Look for syslog output (probably in /var/log/messages) from aisexec. It should reveal more information after failing to start. For cluster use, you don't want to start the "openais" service, ever. It should be configured off. (As it uses a different configuration than cman, the two are mutually exclusive.) > -----Original Message----- > From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] > On Behalf Of Paras pradhan > Sent: Wednesday, September 16, 2009 1:52 PM > To: linux clustering > Subject: openais issue > > hi, > > I had to reboot one of my nodes in the cluster. After rebooting i > found cman is not working. > > I get this error: > > Starting cluster: > Enabling workaround for Xend bridged networking... done > Loading modules... done > Mounting configfs... done > Starting ccsd... done > Starting cman... failed > /usr/sbin/cman_tool: aisexec daemon didn't start > [FAILED] > > > my /etc/hosts is fine , the node can reach other nodes using dns, > packages are of 64 bit . > > I can start openais using service openais and i can see the pid for that. > > How do i debug whats going on here. > > > Thanks! > Paras. > > -- > 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
