[ClusterLabs] Pacemaker fails to start after few starts
Jan Pokorný
jpokorny at redhat.com
Fri Apr 10 07:00:49 UTC 2015
Hello ,
On 30/03/15 10:36 +1100, Andrew Beekhof wrote:
>> On 28 Mar 2015, at 1:10 am, Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com> wrote:
>> If I start/stop Corosync and Pacemaker few times I get the state
>> where Corosync is running, but Pacemaker cannot start.
>> Here is a snippet from /var/log/messages:
[...]
>> Mar 27 14:00:49 daemon.notice<29> pacemakerd[111069]: notice: mcp_read_config: Configured corosync to accept connections from group 107: Library error (2)
>
> Everything else flows from this.
> Perhaps one of the corosync people can comment on the conditions
> under which this call would fail.
CC'd relevant ML.
> Relevant code from pacemaker is:
>
> char key[PATH_MAX];
> snprintf(key, PATH_MAX, "uidgid.gid.%u", gid);
> rc = cmap_set_uint8(local_handle, key, 1);
> crm_notice("Configured corosync to accept connections from group %u: %s (%d)",
> gid, ais_error2text(rc), rc);
Appears to resemble https://bugzilla.redhat.com/show_bug.cgi?id=1114852
--
Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20150410/479503be/attachment-0003.sig>
More information about the Users
mailing list