Not sure these symptoms would be the same on the later versions but on
Lucid I also encountered the following due to this bug:

service corosync stop - never completes.  Hangs waiting for crmd to shutdown 
(over 6 hours without a change)
crm ra info ocf:xx:xx - hangs the crm shell
crm configure primitive p_test ocf: - hung when trying to use tab completion of 
ocf:<tab>

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in Ubuntu.
https://bugs.launchpad.net/bugs/821732

Title:
  Drop raexecupstart.patch and fix_lrmd_leak.patch to not cause socket
  leak in lrmd.

Status in “cluster-glue” package in Ubuntu:
  Fix Released
Status in “cluster-glue” source package in Oneiric:
  Confirmed
Status in “cluster-glue” source package in Precise:
  Fix Released

Bug description:
  ii  cluster-glue               1.0.7-3ubuntu2             The reusable
  cluster components for Linux HA

  The comamnds `crm ra classes` and `cr ra list` cause a socket leak in
  the lrmd daemon.

  When approx. 1024 sockets are allocated, the lrmd becomes unresponsive and 
must be killed.
  The syslog then shows repeated entries:

    Aug  3 10:25:08 server lrmd: [1941]: ERROR:
  socket_accept_connection: accept(sock=6): Too many open files

  While I only use these commands during development, it is still a
  nuisance.

  The leak does not appear for other commands, e.g. `crm resource
  list`, but I have not tested exhaustively.

  I originally reported this bug to http://developerbugs.linux-
  foundation.org/show_bug.cgi?id=2626.

  There I was informed that the behavior most likely stems from an
  unsupported patch (raexecupstart.patch) in the Ubuntu package.
  When I remove that patch, the socket leaks does indeed go away.

  Although I did not have any "deadlock" situations with the original
  code, I replaced it with the attached patch which should prevent any
  possible recursive calls of the `on_remove_client' function.

  *******************************
  After further investigation it was determined that the problem was in glib 
itself and the patch was not needed in the latest's releases of Ubuntu, but 
rather, this patches were creating the socket leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/821732/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to