Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well I'm a newbie in clustering and I'm trying to set a 1 node cluster and I can't start cman, i get: cman not started: Can't find local node name in cluster.conf /usr/sbin/cman_tool: aisexec daemon didn't start
Is your cluster node server.gfs resolvable? Best way is to add the id and name to your /etc/hosts. I suppose you should add a line like as follows:
192.168.1.53 server.gfs
Thanks elcody02, I forgot to mencione that server.gfs is resolvable. In /etc/hosts I have:
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.1.53 server.gfs server localhost.localdomain localhost
192.168.1.21 athlon1
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
Ok. So next is to have a look at what syslog tells you when cman is started. Also the ccsd messages are important. Check if ccsd is running and what it tells you about quorum.
I'm not sure, but I remember having troubles with using nodenames with . in the name. Try to not use server.gfs. Instead use servergfs or something the like. But thats only a wild guess. I'm really not sure about that.
Ok. So next is to have a look at what syslog tells you when cman is started. Also the ccsd messages are important. Check if ccsd is running and what it tells you about quorum.
I'm not sure, but I remember having troubles with using nodenames with . in the name. Try to not use server.gfs. Instead use servergfs or something the like. But thats only a wild guess. I'm really not sure about that.
Have fun.
Thanks elcody02
I've tried changing the cluster name from server.gfs to servergfs and I also added "192.168.1.53 servergfs" to /etc/hosts file. But i keep geting the same response.
In /var/log/messages I don't have any line about cman, only lines of ccsd:
Nov 22 13:12:43 server ccsd[14345]: Starting ccsd 2.0.60:
Nov 22 13:12:43 server ccsd[14345]: Built: Mar 14 2007 08:17:44
Nov 22 13:12:43 server ccsd[14345]: Copyright (C) Red Hat, Inc. 2004 All rights reserved.
Nov 22 13:12:43 server ccsd[14345]: cluster.conf (cluster name = kluster, version = 1) found.
Nov 22 13:13:13 server ccsd[14345]: Unable to connect to cluster infrastructure after 30 seconds.
Nov 22 13:13:43 server ccsd[14345]: Unable to connect to cluster infrastructure after 60 seconds.
Nov 22 13:14:13 server ccsd[14345]: Unable to connect to cluster infrastructure after 90 seconds.
And it seems to work much better than the old cluster.conf but I still can't start cman, the last lines of /var/log/messages goes like this: Nov 23 11:56:48 server openais[18649]: [SERV ] Initialising service handler 'openais CMAN membership service 2.01'
Nov 23 11:56:48 server openais[18649]: [CMAN ] CMAN 2.0.60 (built Mar 14 2007 08:17:48) started
Nov 23 11:56:48 server openais[18649]: [SYNC ] Not using a virtual synchrony filter.
Nov 23 11:56:48 server openais[18649]: [IPC ] ERROR: Could not bind AF_UNIX: Address already in use.
Nov 23 11:56:48 server openais[18649]: [MAIN ] AIS Executive exiting (-7).
Nov 23 11:56:48 server ccsd[18638]: Initial status:: Quorate
Nov 23 11:57:14 server ccsd[18638]: Unable to connect to cluster infrastructure after 30 seconds.
I think that the problem is someting to do with the address, but I'm clueless of how to solve it
Hm, everything looks quite ok so far. What you'll need is the expected_votes="1" in cman.
But that didn't work before either. I haven't seen this before.
Hm, did you try to stop everything:
Quote:
service openais stop
check that no clusterservice is running
service openais start
Wild guess:
You could also try to setup a two node cluster by adding a second node to the cluster.conf. Where no second node is available. Perhaps that is a problem. Check for cman being something like this then:
Well, I disabled a few daemons and also the firewall and it work pretty fine, thanks elcody02 for all your help. I don't know what configuration should I add to the iptables config, but that's a topic for a another post.
Last edited by Roboam León López; 11-29-2007 at 12:54 PM.
Well, I disabled a few daemons and also the firewall and it work pretty fine, thanks elcody02 for all your help. I don't know what configuration should I add to the iptables config, but that's a topic for a another post.
Well, I disabled a few daemons and also the firewall and it work pretty fine, thanks elcody02 for all your help. I don't know what configuration should I add to the iptables config, but that's a topic for a another post.
I'm curious: which daemons did you disable, and how did you disable the firewall? Because I'm having the same problem.
Well, I disabled a few daemons and also the firewall and it work pretty fine, thanks elcody02 for all your help. I don't know what configuration should I add to the iptables config, but that's a topic for a another post.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.