On 15 Jan 2014, at 11:13 pm, Ulrich Windl <[email protected]> wrote:
>>>> Andrew Beekhof <[email protected]> schrieb am 15.01.2014 um 10:27 in >>>> Nachricht > <[email protected]>: >> Looks like corosync is dying underneath pacemaker. >> >> On 15 Jan 2014, at 6:49 pm, Ulrich Windl <[email protected]> >> wrote: >> >>> Hi! >>> >>> I feel the current clusterstack for SLES11 SP3 has several problems. I'm >> fighting for a day to get my test cluster up again after having installed >> the >> latest updates. I still cannot find out what's going on, but I suspect there >> are too many bugs in the software (again). For example I just saw these >> messages: >>> >>> Jan 15 08:39:50 o4 attrd[13911]: error: plugin_dispatch: Receiving >> message body failed: (2) Library error: Success (0) >>> Jan 15 08:39:50 o4 attrd[13911]: crit: attrd_cs_destroy: Lost >>> connection >> to Corosync service! >>> Jan 15 08:39:50 o4 cib[13908]: error: plugin_dispatch: Receiving message >> body failed: (2) Library error: Success (0) >>> Jan 15 08:39:50 o4 cib[13908]: error: cib_cs_destroy: Corosync >>> connection >> lost! Exiting. >>> Jan 15 08:39:50 o4 attrd[13911]: notice: main: Exiting... >>> Jan 15 08:39:50 o4 attrd[13911]: notice: main: Disconnecting client >> 0x611eb0, pid=13913... >>> Jan 15 08:39:50 o4 stonith-ng[13909]: error: plugin_dispatch: Receiving >> message body failed: (2) Library error: Success (0) >>> Jan 15 08:39:50 o4 stonith-ng[13909]: error: stonith_peer_cs_destroy: >> Corosync connection terminated >>> Jan 15 08:39:50 o4 attrd[13911]: error: attrd_cib_connection_destroy: >> Connection to the CIB terminated... >>> Jan 15 08:39:50 o4 crmd[13913]: error: plugin_dispatch: Receiving >>> message >> body failed: (2) Library error: Success (0) >>> Jan 15 08:39:50 o4 crmd[13913]: error: crmd_cs_destroy: connection >> terminated >>> >>> I'm afraid nobody except the developer can make any sense from these error >> messages, except that there is an error. >> >> Seriously? "Lost connection to Corosync service!" and "Corosync connection >> lost! Exiting." are too cryptic for you? > > I'm talking about "...error: Success (0)": What type of "error" is that? "(2) Library error" is from corosync, "Success (0)" is the value of errno. Yes the errno part is confusing, but its also valuable information :( > > [...] > > Regards, > Ulrich > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
