Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello
In combination of drbd-utils-8.9.3 and drbd-8.4.6, the following
command failed to start drbd resource.
# systemctl stop pacemaker
# rmmod drbd
# systemctl start pacemaker
# crm_mon
Failed actions:
res_drbd_r0_start_0 on sac-tkh-sv002 'unknown error' (1): call=7, status=complete, last-rc-change='Tue Jun 30 09:33:29 2015', queued=0ms, exec=67ms
Jun 30 09:33:29 sac-tkh-sv002 drbd(res_drbd_r0)[26761]: ERROR: r0: Called drbdadm -c /etc/drbd.conf syncer r0
Jun 30 09:33:29 sac-tkh-sv002 drbd(res_drbd_r0)[26761]: ERROR: r0: Exit code 1
Jun 30 09:33:29 sac-tkh-sv002 drbd(res_drbd_r0)[26761]: ERROR: r0: Command output:
Jun 30 09:33:29 sac-tkh-sv002 pacemaker_remoted[26723]: notice: operation_finished: res_drbd_r0_start_0:26761:stderr [ drbdadm: Unknown command 'syncer' ]
Jun 30 09:33:29 sac-tkh-sv002 pacemaker_remoted[26723]: info: log_finished: finished - rsc:res_drbd_r0 action:start call_id:7 pid:26761 exit-code:1 exec-time:67ms queue-time:0ms
Jun 30 09:33:29 sac-tkh-sv002 crmd[26726]: notice: process_lrm_event: Operation res_drbd_r0_start_0: unknown error (node=sac-tkh-sv002, call=7, rc=1, cib-update=12, confirmed=true)
Jun 30 09:33:29 sac-tkh-sv002 crmd[26726]: notice: process_lrm_event: sac-tkh-sv002-res_drbd_r0_start_0:7 [ drbdadm: Unknown command 'syncer'\n ]
The problem does not occur in drbd-utils-8.9.2.
--
Hiroshi Fujishima