Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Jake: That was it! Thanks. I vaguely remember seeing something like that go by on the reflector, but I couldn't dig it out. I may need a memory upgrade<g>. Even with the link you sent, I had to dig waaaaaay down to find the magic. Add the following line # X-Interactive: true after the following line in /etc/init.d/drbd file. # X-Stop-After: heartbeat corosync 2. Run the following command in order to apply the above change. insserv -v drbd Now, maybe it will be more searchable for the next fellow that gets caught (I can hope, can't I?) Dan -----Original Message----- From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Jake Smith Sent: Tuesday, May 29, 2012 3:58 PM To: drbd List Subject: Re: [DRBD-user] startup hang after "yes" ----- Original Message ----- > From: "Dan Barker" <dbarker at visioncomm.net> > To: "drbd List" <drbd-user at lists.linbit.com> > Sent: Tuesday, May 29, 2012 8:22:23 AM > Subject: Re: [DRBD-user] startup hang after "yes" > > Machines are now in semi-production (manual start/stop for obvious > reasons). > > The issue still occurs. If I remove the replication cable and boot the > secondary machine (with 4, up to date resources), the boot process > hangs after I reply "yes" to the prompt. Reinserting the cable does > allow the startup scripts to continue, with the error message > "waitpid: > Interrupted > system call", but simply replying "yes" is supposed to do so, with no > error. > > I don't recall seeing this problem before, and I've been through about > 4 drbd release levels. > Long shot but... might be something related to this bug cropping back up? (defining as interactive in the init script): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613654 Jake > Dan (the top poster) > > -----Original Message----- > From: drbd-user-bounces at lists.linbit.com > [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Dan Barker > Sent: Saturday, May 26, 2012 1:23 PM > To: drbd List > Subject: [DRBD-user] startup hang after "yes" > > I'm building a new drbd machine. I put 8.4.0 on a Debian 603 and all > looks > fine except ... > > Since I'm testing, I don't have another node. I did create-md and > then > primary --force. At boot time, there is no peer, so I get the > count-up to > yes. When I enter yes, nothing happens. > > If I ssh in and stop/start drbd, all is normal and my initialization > scripts > finally run (the ones after drbd). > > What can I do to stop the hang? > > Other possibly mitigating factors: > There is no Ethernet cable connected to the NIC for DRBD > synchronization. > There is only one drbd resource defined, drbd3 (no 0, 1 or 2). > > I chose 8.4.0 to match the peer in the environment. I thought about > 8.4.1 or > 8.3.13, but I'll just update everybody to 9 soon. > > Dan > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > > _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user