[Openais] Corosync 2.0 Feature Request: Notification of the status change for each rings via SNMP

would be considering it. Regards, Keisuke MORI 2011/7/22 Steven Dake : > The Corosync flatiron 1.y series had many more features added then I > would have liked, but the development team feels the 1.y series > addresses any major gaps users of the software have had.  As a result,

Re: [Openais] FAILED TO RECEIVE followed by cluster failure

traffic When we encountered to this issue, we had assigned a multicast address to a bridge interface on top of a bonding interface. Changing to assign the IP address onto a bonding interface did solve it. Increasing fail_recv_const did not actually solve it; it just "delayed" to occur.

Re: [Openais] init script runlevel at 20/20 instead of 20/80 debate

orted. As for the starting order, I would be grad if you could also consider the attached patch. It will adjust the dependency with syslog correctly so that can prevent a problem when you use rsyslog as I reported before: https://lists.linux-foundation.org/pipermail/openais/2010-July/014946.

Re: [Openais] Corosync 1.2.5 still hangs on startup

2010/7/2 Keisuke MORI : > 2010/7/2 Steven Dake : >> 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 p

Re: [Openais] Corosync 1.2.5 still hangs on startup

2010/7/2 Steven Dake : > 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,

Re: [Openais] Corosync 1.2.5 still hangs on startup

2010/7/2 Andrew Beekhof : > On Thu, Jul 1, 2010 at 3:09 PM, Keisuke MORI > wrote: >> Here is the stack trace and the corosync.conf when I reproduce it with >>  corosync-1.2.6. >> According to the core, fileno=10 looks broken, while filno=0,1,2,3 seems >> sane. &g

Re: [Openais] Corosync 1.2.5 still hangs on startup

- I'm using rsyslog and the invocation order in init.d is corosync first (S20corosync) and rsyslog later (S26rsyslog) with other 8 services between them. Hope it helps. -- Keisuke MORI ___ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais

Re: [Openais] Corosync 1.2.5 still hangs on startup

Bad news... 2010/6/30 Andrew Beekhof : > On Wed, Jun 30, 2010 at 12:06 PM, Keisuke MORI > wrote: >> 2010/6/29 Andrew Beekhof : >>> On Mon, Jun 28, 2010 at 2:20 PM, Keisuke MORI >>> wrote: >>>> I've upgrade to pacemaker-1.0.9.1 / corosync-1.2.5 fr

Re: [Openais] Corosync 1.2.5 still hangs on startup

2010/6/29 Andrew Beekhof : > On Mon, Jun 28, 2010 at 2:20 PM, Keisuke MORI > wrote: >> I've upgrade to pacemaker-1.0.9.1 / corosync-1.2.5 from clusterlabs on >> CentOS 5.5 using yum but it still hangs on its startup somtimes. >> >> The symptom is exactly sa

[Openais] Corosync 1.2.5 still hangs on startup

r/lib64/heartbeat/stonithd 2597 /usr/lib64/heartbeat/lrmd 2599 /usr/lib64/heartbeat/pengine 3473 /usr/lib64/heartbeat/crmd 8<8<8<8<----8<8<8< Regards, -- Keisuke MORI ___ Open

Re: [Openais] SNMP for corosync

t in case... Regards, Keisuke MORI 2010/3/12 Steven Dake : > Sato-san, > > Really nice initial work.  I have few comments on the patch which are > nitpicky but which once resolved, can be merged. > > first the high level issues: > > configure --with-snmp should be --

Re: [Openais] call for roadmap features for future releases

27;s implemented as a daemon. You can just add "respawn" configuration with the path to the daemon to enable it. I'm glad to help you to implement any of those items if there's anything I can do. Sincerely, -- Keisuke MORI ___ Ope