Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Lars, you wrote > > drbd-utils-8.9.2 w/ drbd-8.4.6 does not have such a problem. > > I think it is drbd-utils-8.9.3's problem. > > Yes. > Does this "Yes" mean that you confirmed that there is a problem with drbd-utils-8.9.3. I'm asking because my cluster broke badly after installing this utils version. Do you need some further information about the problem? Best regards Andreas > -----Ursprüngliche Nachricht----- > Von: drbd-user-bounces at lists.linbit.com [mailto:drbd-user- > bounces at lists.linbit.com] Im Auftrag von Lars Ellenberg > Gesendet: Dienstag, 30. Juni 2015 11:14 > An: drbd-user at lists.linbit.com > Betreff: Re: [DRBD-user] Pacemaker resource start failure in combination > of drbd-utils-8.9.3 and drbd-8.4.6 > > On Tue, Jun 30, 2015 at 05:57:17PM +0900, Hiroshi Fujishima wrote: > > >>>>> In <20150630082043.GH7381 at soda.linbit> > > >>>>> Lars Ellenberg <lars.ellenberg at linbit.com> wrote: > > > On Tue, Jun 30, 2015 at 10:16:42AM +0200, Lars Ellenberg wrote: > > > > On Tue, Jun 30, 2015 at 09:46:49AM +0900, Hiroshi Fujishima wrote: > > > > > 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 ] > > > > > > > > You happen to have more than one DRBD module available? > > > > > > In any case, > > > modprobe DRBD before starting pacemaker should help. > > > > I mean that after OS is booted, drbd.ko is not loaded. After > > rebooting OS, `systemctl start pacemaker' fail to start drbd > > resource. > > Yes. So you modprobe DRBD first. > Each distribution has its preferred way to auto-load modules. > > > `systemctl enable drbd.service' loads drbd.ko, But the following > > document describes that you should disable the DRBD init script. > > > > https://drbd.linbit.com/users-guide/s-pacemaker-crm-drbd-backed- > service.html > > Yes. > > > drbd-utils-8.9.2 w/ drbd-8.4.6 does not have such a problem. > > I think it is drbd-utils-8.9.3's problem. > > Yes. > > -- > : Lars Ellenberg > : http://www.LINBIT.com | Your Way to High Availability > : DRBD, Linux-HA and Pacemaker support and consulting > > DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. > __ > please don't Cc me, but send to list -- I'm subscribed > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user