Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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. 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