Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2004-10-12 23:14:32 +0800 \ Seki Lau: > Dear All, > I have posted these error message but I have not received any response. > So, I will provide more information > > Oct 12 23:06:11 Master kernel: drbd2: PingAck did not arrive in time. > Oct 12 23:06:11 Master kernel: drbd2: drbd2_asender [2310]: cstate Connected --> NetworkFailure > Oct 12 23:06:11 Master kernel: drbd2: asender terminated > Oct 12 23:06:11 Master kernel: drbd2: drbd2_receiver [2275]: cstate NetworkFailure --> BrokenPipe > Oct 12 23:06:11 Master kernel: drbd2: short read expecting header on sock: r=-512 > Oct 12 23:06:11 Master kernel: drbd2: worker terminated > Oct 12 23:06:11 Master kernel: drbd2: drbd2_receiver [2275]: cstate BrokenPipe --> Unconnected > Oct 12 23:06:11 Master kernel: drbd2: Connection lost. > Oct 12 23:06:11 Master kernel: drbd2: drbd2_receiver [2275]: cstate Unconnected --> WFConnection > Oct 12 23:06:12 Master login(pam_unix)[2640]: session opened for user root by (uid=0) > Oct 12 23:06:12 Master -- root[2640]: ROOT LOGIN ON tty1 > Oct 12 23:06:13 Master heartbeat[2464]: info: Link slave:eth1 dead. > Oct 12 23:06:15 Master heartbeat[2464]: WARN: node slave: is dead > Oct 12 23:06:15 Master heartbeat[2464]: WARN: No STONITH device configured. > Oct 12 23:06:15 Master heartbeat[2464]: WARN: Shared disks are not protected. > Oct 12 23:06:15 Master heartbeat[2464]: info: Resources being acquired from slave. > Oct 12 23:06:15 Master heartbeat[2464]: info: Link slave:/dev/ttyS0 dead. > Oct 12 23:06:15 Master heartbeat: info: Running /usr/local/etc/ha.d/rc.d/status status > Oct 12 23:06:15 Master heartbeat: info: /usr/local/lib/heartbeat/mach_down: nice_failback: foreign resources acquired > Oct 12 23:06:15 Master heartbeat[2464]: info: mach_down takeover complete. > Oct 12 23:06:15 Master heartbeat: info: mach_down takeover complete for node slave. > Oct 12 23:06:15 Master heartbeat[3261]: info: Local Resource acquisition completed. > Oct 12 23:06:15 Master heartbeat: info: Running /usr/local/etc/ha.d/rc.d/ip-request-resp ip-request-resp > Oct 12 23:06:15 Master heartbeat: received ip-request-resp smbd OK yes > Oct 12 23:06:15 Master heartbeat: info: Acquiring resource group: master smbd drbd if your smb share is on the drbd, that is WRONG. you obviously need to start the dependencies FIRST. and you don't want to start "drbd", you want to start "drbddisk". and you forget about the Filesystem alltogether. use your common sense... > Oct 12 23:06:15 Master heartbeat: info: Running /usr/local/etc/ha.d/resource.d/smbd start > Oct 12 23:06:16 Master smbd: smbd startup succeeded > Oct 12 23:06:16 Master heartbeat[2479]: WARN: TTY write timeout on [/dev/ttyS0] (no connection or bad cable? [see documentation]) > Oct 12 23:06:16 Master smbd: nmbd startup succeeded > Oct 12 23:06:16 Master heartbeat: info: Running /usr/local/etc/ha.d/resource.d/drbd start > Oct 12 23:06:16 Master kernel: drbd0: PingAck did not arrive in time. > Oct 12 23:06:16 Master kernel: drbd0: drbd0_asender [2234]: cstate Connected --> NetworkFailure > Oct 12 23:06:16 Master kernel: drbd0: asender terminated > Oct 12 23:06:16 Master kernel: drbd0: drbd0_receiver [2199]: cstate NetworkFailure --> BrokenPipe > Oct 12 23:06:16 Master kernel: drbd0: short read expecting header on sock: r=-512 > Oct 12 23:06:16 Master kernel: drbd0: worker terminated > Oct 12 23:06:16 Master kernel: drbd0: drbd0_receiver [2199]: cstate BrokenPipe --> Unconnected > Oct 12 23:06:16 Master kernel: drbd0: Connection lost. > Oct 12 23:06:16 Master kernel: drbd0: drbd0_receiver [2199]: cstate Unconnected --> WFConnection > Oct 12 23:06:17 Master kernel: drbd4: PingAck did not arrive in time. > Oct 12 23:06:17 Master kernel: drbd4: drbd4_asender [2420]: cstate Connected --> NetworkFailure > Oct 12 23:06:17 Master kernel: drbd4: asender terminated > Oct 12 23:06:17 Master kernel: drbd4: drbd4_receiver [2381]: cstate NetworkFailure --> BrokenPipe > Oct 12 23:06:17 Master kernel: drbd4: short read expecting header on sock: r=-512 > Oct 12 23:06:17 Master kernel: drbd4: worker terminated > Oct 12 23:06:17 Master kernel: drbd4: drbd4_receiver [2381]: cstate BrokenPipe --> Unconnected > Oct 12 23:06:17 Master kernel: drbd4: Connection lost. > Oct 12 23:06:17 Master kernel: drbd4: drbd4_receiver [2381]: cstate Unconnected --> WFConnection > Oct 12 23:06:18 Master kernel: drbd3: PingAck did not arrive in time. > Oct 12 23:06:18 Master kernel: drbd3: drbd3_asender [2378]: cstate Connected --> NetworkFailure > Oct 12 23:06:18 Master kernel: drbd3: asender terminated > Oct 12 23:06:18 Master kernel: drbd1: PingAck did not arrive in time. > Oct 12 23:06:18 Master kernel: drbd1: drbd1_asender [2272]: cstate Connected --> NetworkFailure > Oct 12 23:06:18 Master kernel: drbd1: asender terminated > Oct 12 23:06:18 Master kernel: drbd3: drbd3_receiver [2343]: cstate NetworkFailure --> BrokenPipe > Oct 12 23:06:18 Master kernel: drbd3: short read expecting header on sock: r=-512 > Oct 12 23:06:18 Master kernel: drbd1: drbd1_receiver [2237]: cstate NetworkFailure --> BrokenPipe > Oct 12 23:06:18 Master kernel: drbd1: short read expecting header on sock: r=-512 > Oct 12 23:06:18 Master kernel: drbd3: worker terminated > Oct 12 23:06:18 Master kernel: drbd1: worker terminated > Oct 12 23:06:18 Master kernel: drbd3: drbd3_receiver [2343]: cstate BrokenPipe --> Unconnected > Oct 12 23:06:18 Master kernel: drbd1: drbd1_receiver [2237]: cstate BrokenPipe --> Unconnected > Oct 12 23:06:18 Master kernel: drbd3: Connection lost. > Oct 12 23:06:18 Master kernel: drbd3: drbd3_receiver [2343]: cstate Unconnected --> WFConnection > Oct 12 23:06:18 Master kernel: drbd1: Connection lost. > Oct 12 23:06:18 Master kernel: drbd1: drbd1_receiver [2237]: cstate Unconnected --> WFConnection > Oct 12 23:06:26 Master kernel: tg3: eth1: Link is down. > Oct 12 23:06:36 Master kernel: drbd0: ASSERT( mdev->state == Primary ) in /home/seki/drbd-0.7.5/drbd/drbd_req.c:186 well, something tries to access the drbd, but it is still Secondary, because you never told it to become Primary. Thus the assertion fails, of course. more user friendly message would be: "IO-Request on drbd in 'Secondary' mode canceled." > Oct 12 23:06:36 Master last message repeated 15 times > Oct 12 23:06:36 Master kernel: drbd1: ASSERT( mdev->state == Primary ) in /home/seki/drbd-0.7.5/drbd/drbd_req.c:186 > Oct 12 23:06:36 Master last message repeated 15 times > Oct 12 23:06:36 Master kernel: drbd2: ASSERT( mdev->state == Primary ) in /home/seki/drbd-0.7.5/drbd/drbd_req.c:186 > Oct 12 23:06:36 Master last message repeated 15 times > Oct 12 23:06:36 Master kernel: drbd3: ASSERT( mdev->state == Primary ) in /home/seki/drbd-0.7.5/drbd/drbd_req.c:186 > Oct 12 23:06:36 Master last message repeated 15 times > Oct 12 23:06:36 Master kernel: drbd4: ASSERT( mdev->state == Primary ) in /home/seki/drbd-0.7.5/drbd/drbd_req.c:186 > Oct 12 23:06:36 Master last message repeated 15 times Lars Ellenberg -- please use the "List-Reply" function of your email client.