SOLVED! This was the problem. Thanks a lot. The directories and links where there from time when it was running perfect I think. Anyhow, there is always space for improvement. Do you think we should change the error message to make it more clear? May be we can update the FAQ list as well. Thanks a lot, Arne -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Patrick Caulfield Sent: Donnerstag, 26. April 2007 10:27 To: linux clustering Subject: Re: startup problem: "cman not started: Can't bindto local cman socket /usr/sbin/cman_tool: aisexec daemon didn't start " Brieseneck, Arne, VF-Group wrote: > it is high likely that anybody already knows this error and knows how > to fix it: > > ---snip--- > [root@box1 ~]# /etc/init.d/cman start > Starting cluster: > Loading modules... done > Mounting configfs... done > Starting ccsd... done > Starting cman... failed > cman not started: Can't bind to local cman socket /usr/sbin/cman_tool: > aisexec daemon didn't start > [FAILED] > [root@box1 ~]# It means that cman could not create the local socket in /var/run for communication with the cluster clients. cman tries to create /var/run/cman_client & /var/run/cman_admin - things like cman_tool/groupd/ccsd etc talk to cman over this link. If it can't be created then its not much use. Check /var/run is writable and able to hold Unix domain sockets. -- Patrick Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 ITE, UK. Registered in England and Wales under Company Registration No. 3798903 -- 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
