[Pacemaker] Pacemaker1.1.8:pacemaker srvc fails to stop gracefully & crm resource cleanup fails

[Andrew Beekhof]

On Mon, Jan 7, 2013 at 5:11 PM, Parshvi <parshvi.17 at gmail.com> wrote:
>
>>
>> crm_mon failed on Node-1 with the following error:
>> establish cib_ro connection: Resource temporarily unavailable (11)
>>
>> crm resource cleanup <rsc> failed on Node-1 with the following error:
>> Could not establish cib_rw connection: Resource temporarily unavailable (11)
>> Error signing on to the CIB service: Transport endpoint is not connected
>
>
> Hi request the owners to please provide some input.

You do realise this is a community site right?
We do what we can, but most of have day jobs. If you need priority
support there are several companies that would be more than happy to
take your money.
Please also run crm_report (check the man page for examples), what
people think is worthy of including in log fragments is often not what
is needed to diagnose the problem.

> Our system at production is down for over 10 hours under this
>  release of pacemaker.
>
> We faced the issue again:
> crm_mon failed on Node-1 with the following error:
> establish cib_ro connection: Resource temporarily
> unavailable (11)
> - lrmd_connection_destroy:         connection destroyed
> - crmd:     info: lrm_connection_destroy:  LRM Connection
> disconnected
> - crmd:     info: do_cib_control:  Disconnecting CIB
> pacemaker srvc couldnt be stopped. had to be killed to restart.
>
> The failed rscs during this period are not recovered
>  by cluster srvc.
> I will upload the hb_report for this issue.
>
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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