Control: retitle -1 drbd-utils: initscript may wait forever (wfc-timeout unset)
Hi,
On 10:45 Thu 12 May , Ferenc Wágner wrote:
> Christoph Berg writes:
>
> > Is that something we can or should fix on the corosync side?
>
> Without further information I can't see anything to fix in corosync
Christoph Berg writes:
> Is that something we can or should fix on the corosync side?
Without further information I can't see anything to fix in corosync.
> Or reassign to drbd-utils to change the default for wfc-timeout?
Sounds like a good idea, the original report shows S03drbd S04corosync.
Control: tags -1 moreinfo
Re: Ferenc Wagner 2015-10-22 <87lhavxbi3@lant.ki.iif.hu>
> Hi,
>
> Does syslog contain anything corosync-related after bootup, but before
> you start it manually? Isn't it the DRBD timeout mentioned in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752512#10 ?
Hi,
Does syslog contain anything corosync-related after bootup, but before
you start it manually? Isn't it the DRBD timeout mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752512#10 ?
--
Thanks,
Feri.
I observed this very same issue on a two-nodes cluster with one of the nodes
powered off.
The culprit in my case was DRBD waiting forever for a connection from the other
node. DRBD’s LSB header says that corosync should be started after itself and
given the unlimited WFC timeout, this never happ
Package: corosync
Version: 1.4.2-3
Severity: normal
Dear Maintainers,
I ran into problem with corosync on one of our servers. Our corosync daemon
doesn't
start at boot, but after the host is back online again 'service corosync start'
fixes
the issue just fine until next reboot.
Unfortunately I
6 matches
Mail list logo
