On 28/09/2013, at 5:37 AM, Radoslaw Garbacz
radoslaw.garb...@xtremedatainc.com wrote:
The problem was actually of a different nature - nothing to do with
cib_shm. The logs showed later on that the connection to cib was
established, just the corosync configuration file didn't hava a proper
cibadmin -Ql works, problem is persistent after upgrade, and the logs
for crmd reviled the problem:
Sep 27 16:19:22 [5074] ip-10-82-197-219 crmd: info:
crm_ipc_connect: Could not establish cib_shm connection: Connection
refused (111)
Sep 27 16:19:22 [5074] ip-10-82-197-219 crmd:
Hi,
I have a problem starting up a cluster after upgrading corosync from
1.4 to 2.3.2 and pacemaker from 1.8 to 1.9.
All crm_node calls report well, but any CIB manipulation fails, i.e.:
* crm_node -q: 1
* crm_node -l: OK
* crm_node -p: OK
* cibadmin -Q: Call cib_query failed (-62): Timer
On 27/09/2013, at 8:45 AM, Radoslaw Garbacz
radoslaw.garb...@xtremedatainc.com wrote:
Hi,
I have a problem starting up a cluster after upgrading corosync from
1.4 to 2.3.2 and pacemaker from 1.8 to 1.9.
All crm_node calls report well, but any CIB manipulation fails, i.e.:
* crm_node
