Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
My master stays in WFReportParams forever due to a network
failure on my slave.
Scenario: Master is running and is Primary, Slave is booting
This is the relevant log:
Slave boot: (only kernel drbd messages)
11:49:46 SYSLOG info kernel drbd: initialised. Version: 0.7.4
(api:76/proto:74)
11:49:46 SYSLOG info kernel drbd: SVN Revision: 1537M build by
root at build, 2004-09-21 14:44:03
11:49:46 SYSLOG info kernel drbd: registered as block device major 147
11:49:46 SYSLOG info kernel drbd0: resync bitmap: bits=1540096
words=48128
11:49:46 SYSLOG info kernel drbd0: size = 6016 MB (6160384 KB)
11:49:46 SYSLOG info kernel drbd0: 0 KB marked out-of-sync by on disk
bit-map.
11:49:46 SYSLOG warning kernel drbd0: No usable activity log found.
11:49:46 SYSLOG info kernel drbd0: drbdsetup [775]: cstate Unconfigured
--> StandAlone
11:49:46 SYSLOG info kernel drbd0: drbdsetup [788]: cstate StandAlone
--> Unconnected
11:49:46 SYSLOG info kernel drbd0: drbd0_receiver [789]: cstate
Unconnected --> WFConnection
11:49:46 SYSLOG info kernel drbd0: drbd0_receiver [789]: cstate
WFConnection --> WFReportParams
11:49:48 SYSLOG err kernel drbd0: sock_recvmsg returned -11
11:49:48 SYSLOG info kernel drbd0: drbd0_receiver [789]: cstate
WFReportParams --> BrokenPipe
11:49:48 SYSLOG err kernel drbd0: short read expecting header on sock:
r=-11
11:49:48 SYSLOG warning kernel drbd0: Discarding network configuration.
11:49:48 SYSLOG info kernel drbd0: worker terminated
11:49:48 SYSLOG info kernel drbd0: drbd0_receiver [789]: cstate
BrokenPipe --> Unconnected
11:49:48 SYSLOG info kernel drbd0: Connection lost.
11:49:48 SYSLOG info kernel drbd0: drbd0_receiver [789]: cstate
Unconnected --> StandAlone
11:49:48 SYSLOG info kernel drbd0: receiver terminated
master log:
... non drbd logging
11:49:46 SYSLOG info kernel drbd0: drbd0_receiver [951]: cstate
WFConnection --> WFReportParams
... non drbd logging
and afterwards:
master$ cat /proc/drbd
version: 0.7.4 (api:76/proto:74)
SVN Revision: 1537M build by root at build, 2004-09-21 14:44:03
0: cs:WFReportParams st:Primary/Unknown ld:Consistent
ns:44028 nr:0 dw:409272 dr:65465 al:2 bm:48 lo:0 pe:0 ua:0 ap:0
1: cs:Unconfigured
(this stays forever)
(I do not have a cat /proc/drbd from the slave anymore)
The only way I found to get out of this situation is to reboot
the master.
Shouldn't there be a 'timeout' on this WFReportParams state, since
the docs (wiki) says it's: 'Transitory state, while waiting for first
packet on a new TCP connection.'
I guess the first packet never came....
alex
--
************************************************************
visit us at Infosecurity NL - Stand 08.B121
13-14 october 2004
Jaarbeurs - Utrecht Netherlands
Free Registration, click here: www.axsguard.com
************************************************************
aXs GUARD has completed security and anti-virus checks on this e-mail
(http://www.axsguard.com)