Jan: not sure if you're on the pacemaker list On 29 Oct 2013, at 6:43 pm, Bauer, Stefan (IZLBW Extern) <stefan.ba...@iz.bwl.de> wrote:
> Dear Developers/Users, > > we’re using Pacemaker 1.1.7 and Corosync Cluster Engine 1.4.2 with Debian 6 > and a recent vanilla Kernel (3.10). > > On quite a lot of our clusters we can not check the ring status anymore: > > corosync-cfgtool –s returns: > > Could not initialize corosync configuration API error 2 > > A reboot is fixing the problem. > > Even though the status is not returned, i see traffic on the ring interfaces > and the cluster is operational. > > We’re using rrp_mode: active with 2 ring interfaces with multicast. > > Is this a known problem? Not that I know of. CC'ing Jan (corosync maintainer) > Does a workaround exist to not force us to reboot the machines regularly ? > > Any help is greatly appreciated. > > Regards > > Stefan Bauer > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
