[Pacemaker] [Problem]The problem of the combination of Pacemaker and corosync1.2.7.

Vladislav Bogdanov bubble at hoster-ok.com
Mon Aug 2 03:57:48 EDT 2010


02.08.2010 04:17, renayama19661014 at ybb.ne.jp wrote:

...

> Problem 3) There is a case to fail in the start of a cib process and the attrd process.
> 
> Jul 30 14:25:46 x3650g attrd: [26258]: ERROR: ais_dispatch: Receiving message body failed: (2) Library
> error: Resource temporarily unavailable (11)
> Jul 30 14:25:46 x3650g attrd: [26258]: ERROR: ais_dispatch: AIS connection failed
> Jul 30 14:25:46 x3650g cib: [26256]: ERROR: ais_dispatch: Receiving message body failed: (2) Library
> error: Resource temporarily unavailable (11)
> Jul 30 14:25:46 x3650g cib: [26256]: ERROR: ais_dispatch: AIS connection failed
> Jul 30 14:25:46 x3650g attrd: [26258]: CRIT: attrd_ais_destroy: Lost connection to OpenAIS service!
> Jul 30 14:25:46 x3650g cib: [26256]: ERROR: cib_ais_destroy: AIS connection terminated
> Jul 30 14:25:46 x3650g attrd: [26258]: info: main: Exiting...
> Jul 30 14:25:46 x3650g attrd: [26258]: ERROR: attrd_cib_connection_destroy: Connection to the CIB
> terminated...
> Jul 30 14:25:46 x3650g stonithd: [26255]: ERROR: ais_dispatch: Receiving message body failed: (2)
> Library error: Success (0)
> Jul 30 14:25:46 x3650g stonithd: [26255]: ERROR: ais_dispatch
> 
> Can this problem be settled in Pacemaker1.0 and corosync1.2.7?
> 
> I know that a revision to replace communication with CPG in structure of new Pacemaker begins.
> When we combine corosync and use it, should we wait for a revision of CPG to be over?
> (Should we wait for Pacemaker1.1 system?)
> 
> Because log is big, I contact it again after registering this problem with bugzilla.
>


This is probably connected to
http://marc.info/?l=openais&m=127977785007234&w=2

Steven promised to look at that issue after his vacation.


Best,
Vladislav




More information about the Pacemaker mailing list