[Pacemaker] cib connection error
Andrew Beekhof
andrew at beekhof.net
Tue Sep 24 03:40:25 UTC 2013
On 24/09/2013, at 2:09 AM, Халезов Иван <i.khalezov at rts.ru> wrote:
> Hi all,
>
> I use pacemaker 1.1.9 with corosync 2.3 both built from source.
> My OS is CentOS 6.4 x86_64
>
> I have about 30 resources of one type managed by my own resource agent. It is nesessary for the resource agent to know utilization parameter of the configured resource. I query for this parameter by crm_resource utility in the start function of the RA. After I had implemented this feature, I got a lot of error's in my logs:
>
> Sep 23 19:19:47 iblade5 lrmd[7492]: notice: operation_finished: RESOURCE_start_0:8445:stderr [ Could not establish cib_rw connection: Resource temporarily unavailable (11) ]
> Sep 23 19:19:47 iblade5 lrmd[7492]: notice: operation_finished: RESOURCE_start_0:8445:stderr [ Error signing on to the CIB service: Transport endpoint is not connected ]
>
> So, only few resources (about 4 or 5), every time different, start correctly (crm_resource correctly returns the needed value during start action). And all other resources fail to start.
>
> I think there is a problem when many (20-30) resources start at the same time, and there are 20-30 queries to CIB from the resource agents
>
> How can I correct this ?
I recall talking to NTT about this recently but I forget what they did to make progress.
Perhaps you could look for $?=11 and try again. I _think_ there might have been a patch for libqb that resolved it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130924/3a8e3861/attachment-0004.sig>
More information about the Pacemaker
mailing list