You're running a version of pacemaker that was built against a different version of corosync (1.x) than you're running (2.x).
On 2 Apr 2014, at 8:14 pm, Stefan Bauer <stefan.ba...@cubewerk.de> wrote:
> It seems that pacemakerd 1.1 is trying to connect to unix socket
> corosync.ipc but that is not provided by corosync 2.3.3:
>
> connect(4, {sa_family=AF_FILE, path=@"corosync.ipc"}, 110) = -1
> ECONNREFUSED (Connection refused)
>
> With the corosync release from the 1.x branch its available:
>
> root@wrk1:/home/stefan# lsof | grep corosync | grep @
> corosync 4327 root 7u unix 0xffff8800a3f38280
> 0t0 63921 @corosync.ipc
> corosync 4327 root 13u unix 0xffff8800a40f7200
> 0t0 63981 @corosync.ipc
> corosync 4327 root 14u unix 0xffff8800ae8aca40
> 0t0 63982 @corosync.ipc
>
> But not with 2.3:
>
> root@debianbuild:/var/lib/heartbeat/cores/root# lsof | grep corosync |
> grep corosync.ipc
> root@debianbuild:/var/lib/heartbeat/cores/root#
>
> What do i miss?
>
> Stefan
>
>
> _______________________________________________
> 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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
