[Debian-ha-maintainers] Bug#596694: Bug#596694: Workaround?

Dr. Frank Albrecht schreibmirjetzt at me.com
Wed Sep 15 11:38:29 UTC 2010

Hi all,

due to some research and and a lot of tests I've got some new  
informations about the bug and 2 possible solutions.

Should I post the infos to the closed bug report?



Am 14.09.2010 um 13:27 schrieb Guido Günther:

> On Tue, Sep 14, 2010 at 01:10:34PM +0200, Dr. Frank Albrecht wrote:
>> Cite raoul:
>> "i ended up adding $syslog too and until now, i did not have any
>> problem."
>> I spent a lot of time to fix/workaround the corosync start problem
>> but with no luck. I've found your bug report (the shorewell issue)
>> and tried to manage the order of init.d starter scripts (adding
>> $syslog in .depend.boot resp. changing the order of the
>> rc2.d-symlinks).
>> But I'm not able to get a consistent behaviour for the corosync
>> start. Sometimes it starts correct, sometimes it stucks in a zombie
>> state and the only solution is a "killall -s 9 corosync".
>> The logs are not so helpful. I will link them later here in this
>> bugreport thread.
>> Do you have a workaround? Where did you add $syslog?
> I've just uploaded a new version to unstable that should fix this.
> Cheers,
> -- Guido
> -- 
> To unsubscribe, send mail to 596694-unsubscribe at bugs.debian.org.

More information about the Debian-ha-maintainers mailing list