2010/7/2 Keisuke MORI <[email protected]>: > 2010/7/2 Steven Dake <[email protected]>: >> On 07/01/2010 09:26 PM, Keisuke MORI wrote: >> If rsyslog is started first, does this problem persist? Why >> starting logging daemon after corosync? corosync depends on syslog if using >> syslog output. Does this problem persist if to_syslog is set to no? > > OK, I will test them. > > The starting order is all by default. I just installed by rpm > and did no special instructions.
OK, now I've found that the issues is triggered by the starting order of rsyslog. As you suggested, I've tested 1) changing to start corosync after rsyslog, 2) changing to_syslog to no, and I've been not able to reproduce it on either configuration with rebooting the nodes more than five times each (while it occurred almost every time with the default configuration). This problem should be occurred if you just enabled rsyslog since this starting order is the default (at least on RHEL 5/CentOS 5). I would suggest the attached patch to address this issue. The reason why rsyslog is started at S26 (after corosync) by default is that, rsyslog states that it depends on $local_fs/$remote_fs defined in LSB which is provided by netfs started at S25. The traditional syslog and syslog-ng are usually started at S12 and corosync is at S20, so the problem does not occur. Other note: 'to_syslog: no' is probably not usable for Pacemaker cluster because RAs complain as below and can not record logs. Jul 02 21:30:19 pm02 lrmd: [2564]: info: RA output: (pingd:0:monitor:stderr) logger: unknown facility name: none. Regards, -- Keisuke MORI
--- corosync.org 2010-07-01 17:49:52.000000000 +0900 +++ corosync.mod 2010-07-02 21:58:51.000000000 +0900 @@ -12,9 +12,8 @@ # ### BEGIN INIT INFO # Provides: corosync -# Required-Start: $network -# Should-Start: $syslog -# Required-Stop: $network +# Required-Start: $network $syslog +# Required-Stop: $network $syslog # Default-Start: # Default-Stop: # Short-Description: Starts and stops Corosync Cluster Engine.
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
