corosync+pacemaker

[Bernhard Pöttinger]

I have tried to test an esos cluster; so under vmware I have built 2 esos server and configured corosync. I can start corosync and pacemaker, but when I try to setup an "crm configure show" I get the following message:

[root@esostest1 ~]# crm configure show
ERROR: running cibadmin -Ql: Could not establish cib_rw connection: Operation not permitted (1)
Signon to CIB failed: Transport endpoint is not connected
Init failed, could not perform requested operations

and the log files says (local2.log)

Apr 16 09:44:42 esostest1 corosync[2136]:  [MAIN  ] Corosync Cluster Engine ('2.3.3'): started and ready to provide service.
Apr 16 09:44:42 esostest1 corosync[2136]:  [MAIN  ] Corosync built-in features: rdma xmlconf pie relro bindnow
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] Initializing transport (UDP/IP Multicast).
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] Initializing transmit/receive security (NSS) crypto: none hash: none
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] Initializing transport (UDP/IP Multicast).
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] Initializing transmit/receive security (NSS) crypto: none hash: none
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] The network interface [10.0.1.4] is now up.
Apr 16 09:44:42 esostest1 corosync[2137]:  [SERV  ] Service engine loaded: corosync configuration map access [0]
Apr 16 09:44:42 esostest1 corosync[2137]:  [QB    ] server name: cmap
Apr 16 09:44:42 esostest1 corosync[2137]:  [SERV  ] Service engine loaded: corosync configuration service [1]
Apr 16 09:44:42 esostest1 corosync[2137]:  [QB    ] server name: cfg
Apr 16 09:44:42 esostest1 corosync[2137]:  [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Apr 16 09:44:42 esostest1 corosync[2137]:  [QB    ] server name: cpg
Apr 16 09:44:42 esostest1 corosync[2137]:  [SERV  ] Service engine loaded: corosync profile loading service [4]
Apr 16 09:44:42 esostest1 corosync[2137]:  [QUORUM] Using quorum provider corosync_votequorum
Apr 16 09:44:42 esostest1 corosync[2137]:  [VOTEQ ] Waiting for all cluster members. Current votes: 1 expected_votes: 2
Apr 16 09:44:42 esostest1 corosync[2137]:  [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Apr 16 09:44:42 esostest1 corosync[2137]:  [QB    ] server name: votequorum
Apr 16 09:44:42 esostest1 corosync[2137]:  [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Apr 16 09:44:42 esostest1 corosync[2137]:  [QB    ] server name: quorum
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] The network interface [10.0.2.4] is now up.
Apr 16 09:44:42 esostest1 corosync[2137]:  [TOTEM ] A new membership (10.0.1.4:64) was formed. Members joined: 1
Apr 16 09:44:42 esostest1 corosync[2137]:  [VOTEQ ] Waiting for all cluster members. Current votes: 1 expected_votes: 2
Apr 16 09:44:42 esostest1 last message repeated 2 times
Apr 16 09:44:42 esostest1 corosync[2137]:  [QUORUM] Members[1]: 1
Apr 16 09:44:42 esostest1 corosync[2137]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 16 09:46:17 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:17 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-response-2137-2195-41: No space left on device (28)
Apr 16 09:46:17 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:17 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-41): No space left on device (28)
Apr 16 09:46:18 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:18 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-request-2137-2195-42: No space left on device (28)
Apr 16 09:46:18 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:18 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-42): No space left on device (28)
Apr 16 09:46:20 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:20 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-request-2137-2195-43: No space left on device (28)
Apr 16 09:46:20 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:20 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-43): No space left on device (28)
Apr 16 09:46:23 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:23 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-request-2137-2195-44: No space left on device (28)
Apr 16 09:46:23 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:23 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-44): No space left on device (28)
Apr 16 09:46:27 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:27 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-request-2137-2195-45: No space left on device (28)
Apr 16 09:46:27 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:27 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-45): No space left on device (28)
Apr 16 09:46:32 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:32 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-request-2137-2195-46: No space left on device (28)
Apr 16 09:46:32 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:32 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-46): No space left on device (28)
Apr 16 09:46:33 esostest1 corosync[2137]:  [QB    ] couldn't create file for mmap
Apr 16 09:46:33 esostest1 corosync[2137]:  [QB    ] qb_rb_open:cfg-request-2137-2195-47: No space left on device (28)
Apr 16 09:46:33 esostest1 corosync[2137]:  [QB    ] shm connection FAILED: No space left on device (28)
Apr 16 09:46:33 esostest1 corosync[2137]:  [QB    ] Error in connection setup (2137-2195-47): No space left on device (28)

So I don't understand the "No space left on device".

best regards
bernhard

[Marc Smith]

Hi,

What version are you using? Previously the /dev/shm file system was
64M and then a revision or two ago it was increased to 128M. For a
temporary fix, you can use this:
mount -o remount,size=128M /dev/shm

Let me know.


--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Bernhard Pöttinger]

Hi Marc,

I have fond the solution. "/dev/shm" has permission 755:

ls -ld /dev/shm/
drwxr-xr-x    2 root     root          2080 Apr 27 11:04 /dev/shm/

I have changed them to 777 and everything works fine:

crm configure show
node $id="1" esostest1
property $id="cib-bootstrap-options" \
        dc-version="1.1.8-1f8858c" \
        cluster-infrastructure="corosync"

best regards
Bernhard