You are correct. Sorry I should have considered version information. On my RHEL4.4 cluster behaves as described. cman_tool leave + options works for me .. And so should service cman stop remove Good luck.. Damjan Stulic -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Alain Moulle Sent: Wednesday, December 12, 2007 01:43 To: linux-cluster@xxxxxxxxxx Subject: RE: CS5 can't stop service cman This problem is related to the cman kernel module. The module has services connected to it, and therefore will not unload from memory. You can stop cman manually by: cman_tool leave force Or cman_tool leave force remove There is also a force flag on the cman start stop script. However this does not solve the problem of the cman kernel module! Hi Thanks Damjan, but I don't think so : what you write is true with CS U4 but no more with CS5 because cman seems to no more be a kernel module but in user space now. So ... ? Thanks Regards Alain Moullé Thanks, Damjan Stulic IS Security Identity Management Edward Jones If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments. If you no longer wish to receive e-mail from Edward Jones, please send this request to messages@xxxxxxxxxxxxxxxx You must include the e-mail address that you wish not to receive e-mail communications. For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Alain Moulle Sent: Monday, December 10, 2007 10:06 To: linux-cluster@xxxxxxxxxx Subject: CS5 can't stop service cman Hi I've got quite systematically this problem when stopping cman service : # service cman stop Stopping cluster: Stopping fencing... done Stopping cman... failed /usr/sbin/cman_tool: Error leaving cluster: Device or resource busy [FAILED] but no more details in syslog ... Is this a known issue ? and if so, is there a issue number with a patch ? Thanks Regards Alain Moullé -- ######################################## Bull recrute : http://www.bull.fr/emploi ######################################## mailto:Alain.Moulle@xxxxxxxx +------------------------------+--------------------------------+ | Alain Moullé | from France : 04 76 29 75 99 | | | FAX number : 04 76 29 72 49 | | Bull SA | | | 1, Rue de Provence | Adr : FREC B1-063 | | B.P. 208 | | | 38432 Echirolles - CEDEX | Email: Alain.Moulle@xxxxxxxx | | France | BCOM : 229 7599 | +-------------------------------+-------------------------------+ -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
