[Linux-cluster] Linux-cluster Digest, Vol 80, Issue 23

umesh susvirkar susvirkar.3616 at gmail.com
Mon Dec 27 09:02:45 UTC 2010


Hi

Your server hostname & name you specify in cluster.conf file for cluster
node name should be same.is this 2 value are different.
if values are different make it similar and check.




Regards
Umesh Susvirkar


On Mon, Dec 27, 2010 at 12:38 PM, sandeeep <sandy.rhce at gmail.com> wrote:

> Hi,
>  I am using RHEL5.4  and trying to make cluster using conga, i did
> every  thing,  like in main server i installed luci* cluster* related
> package using :"yum groupinstall luci* cluster*,
> and same time installed cman*
> and in other two nodes i have installed ricci* packege using yum.
> now every thing is done, but in server when i am running "service cman
> restart" its giving an error like " local  node name is not found in
> main conficuration file and /usr/sbin/cman_tool: aisex daemon not
> started ."   please have a look into my querry, as i am facing this
> problem since many days.
>
>
> THanks
> Sandeep
>
> On 12/24/10, linux-cluster-request at redhat.com
> <linux-cluster-request at redhat.com> wrote:
> > Send Linux-cluster mailing list submissions to
> >       linux-cluster at redhat.com
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >       https://www.redhat.com/mailman/listinfo/linux-cluster
> > or, via email, send a message with subject or body 'help' to
> >       linux-cluster-request at redhat.com
> >
> > You can reach the person managing the list at
> >       linux-cluster-owner at redhat.com
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Linux-cluster digest..."
> >
> >
> > Today's Topics:
> >
> >    1. IP Resource behavior with Red Hat Cluster (Parvez Shaikh)
> >    2. Re: IP Resource behavior with Red Hat Cluster
> >       (Rajagopal Swaminathan)
> >    3. Re: IP Resource behavior with Red Hat Cluster (Parvez Shaikh)
> >    4. Re: IP Resource behavior with Red Hat Cluster (Jakov Sosic)
> >    5. Re: IP Resource behavior with Red Hat Cluster (Parvez Shaikh)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Fri, 24 Dec 2010 11:03:12 +0530
> > From: Parvez Shaikh <parvez.h.shaikh at gmail.com>
> > To: linux-cluster at redhat.com
> > Subject: [Linux-cluster] IP Resource behavior with Red Hat Cluster
> > Message-ID:
> >       <AANLkTin5PGXoHiLq_5wTfaA-HRcUxcF1hGzGd-1WQP3t at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Hi all,
> >
> > I am using Red Hat cluster 6.2.0 (version shown with cman_tool
> > version) on Red Hat 5.5
> >
> > I am on host that has multiple network interfaces and all(or some) of
> > which may be active while I tried to bring up my IP resource up.
> >
> > My cluster is of simple configuration -
> > It has only 2 nodes, and service basically consist of only IP
> > resource, I had to chose random private IP address for test/debugging
> > purpose (192.168....)
> >
> > When I tried to start service it failed with message -
> >
> > clurgmgrd: [31853]: <debug> 192.168.25.135 is not configured
> >
> > I manually made this virtual IP available on host and then started
> > service it worked -
> >
> > clurgmgrd: [31853]: <debug> 192.168.25.135 already configured
> >
> >
> > My question is - Is it prerequisite for IP resource to be manually
> > added before it can be protected via cluster?
> >
> > Thanks
> > Parvez
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Fri, 24 Dec 2010 06:00:01 +0000
> > From: Rajagopal Swaminathan <raju.rajsand at gmail.com>
> > To: linux clustering <linux-cluster at redhat.com>
> > Subject: Re: [Linux-cluster] IP Resource behavior with Red Hat Cluster
> > Message-ID:
> >       <AANLkTik08h5urUqPYZ6azUWW2YGnsPdBbnOa+Jk-0JBu at mail.gmail.com<AANLkTik08h5urUqPYZ6azUWW2YGnsPdBbnOa%2BJk-0JBu at mail.gmail.com>
> >
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Greetings,
> >
> > On Fri, Dec 24, 2010 at 5:33 AM, Parvez Shaikh
> > <parvez.h.shaikh at gmail.com> wrote:
> >> Hi all,
> >>
> >> I manually made this virtual IP available on host and then started
> >> service it worked -
> >>
> >
> > Can you please elaborate? did you try to assign IP to the ethx devices
> > and then ping?
> >
> >> clurgmgrd: [31853]: <debug> 192.168.25.135 already configured
> >>
> >>
> >> My question is - Is it prerequisite for IP resource to be manually
> >> added before it can be protected via cluster?
> >>
> >
> > Every resource/service has to be added to the cluster.
> >
> > And they cannot be used by anything else.
> >
> > Regards,
> >
> > Rajagopal
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Fri, 24 Dec 2010 14:11:53 +0530
> > From: Parvez Shaikh <parvez.h.shaikh at gmail.com>
> > To: linux clustering <linux-cluster at redhat.com>
> > Subject: Re: [Linux-cluster] IP Resource behavior with Red Hat Cluster
> > Message-ID:
> >       <AANLkTimTfMFE7MvrQRLMOhpfKBRS+EDSF4OGwBgJu9-W at mail.gmail.com<AANLkTimTfMFE7MvrQRLMOhpfKBRS%2BEDSF4OGwBgJu9-W at mail.gmail.com>
> >
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Hi Rajagopal,
> >
> > Thank you for your response
> >
> > I have created a cluster configuration by adding IP resource with
> > value 192.168.25.153 (some value) and created a service which just has
> > IP resource part of it. I have set all requisite configuration such
> > two node, node names, failover,fencing etc.
> >
> > Upon trying to start then service(enable service),it failed -
> >
> > clurgmgrd: [31853]: <debug> 192.168.25.135 is not configured
> >
> > Then manually added this IP to host
> >
> > ifconfig eth0:1 192.168.25.135
> >
> > Then service could start but it gave message -
> >
> > clurgmgrd: [31853]: <debug> 192.168.25.135 already configured
> >
> > So do I have to add virtual interface manually (as above or any other
> > method?) before I could start service with IP resource under it?
> >
> > Thanks
> > Parvez
> >
> > On Fri, Dec 24, 2010 at 11:30 AM, Rajagopal Swaminathan
> > <raju.rajsand at gmail.com> wrote:
> >> Greetings,
> >>
> >> On Fri, Dec 24, 2010 at 5:33 AM, Parvez Shaikh
> >> <parvez.h.shaikh at gmail.com> wrote:
> >>> Hi all,
> >>>
> >>> I manually made this virtual IP available on host and then started
> >>> service it worked -
> >>>
> >>
> >> Can you please elaborate? did you try to assign IP to the ethx devices
> >> and then ping?
> >>
> >>> clurgmgrd: [31853]: <debug> 192.168.25.135 already configured
> >>>
> >>>
> >>> My question is - Is it prerequisite for IP resource to be manually
> >>> added before it can be protected via cluster?
> >>>
> >>
> >> Every resource/service has to be added to the cluster.
> >>
> >> And they cannot be used by anything else.
> >>
> >> Regards,
> >>
> >> Rajagopal
> >>
> >> --
> >> Linux-cluster mailing list
> >> Linux-cluster at redhat.com
> >> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Fri, 24 Dec 2010 13:46:05 +0100
> > From: Jakov Sosic <jakov.sosic at srce.hr>
> > To: linux clustering <linux-cluster at redhat.com>
> > Subject: Re: [Linux-cluster] IP Resource behavior with Red Hat Cluster
> > Message-ID: <4D14960D.50706 at srce.hr>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > On 12/24/2010 09:41 AM, Parvez Shaikh wrote:
> >> Hi Rajagopal,
> >>
> >> Thank you for your response
> >>
> >> I have created a cluster configuration by adding IP resource with
> >> value 192.168.25.153 (some value) and created a service which just has
> >> IP resource part of it. I have set all requisite configuration such
> >> two node, node names, failover,fencing etc.
> >>
> >> Upon trying to start then service(enable service),it failed -
> >>
> >> clurgmgrd: [31853]: <debug> 192.168.25.135 is not configured
> >>
> >> Then manually added this IP to host
> >>
> >> ifconfig eth0:1 192.168.25.135
> >>
> >> Then service could start but it gave message -
> >>
> >> clurgmgrd: [31853]: <debug> 192.168.25.135 already configured
> >>
> >> So do I have to add virtual interface manually (as above or any other
> >> method?) before I could start service with IP resource under it?
> >
> > How is your network configured? For an IP address to work in a cluster,
> > you have to have interfaces on both machines set up, which are in the
> > same subnet. For example:
> >
> > node1 # ifconfig eth0 192.168.25.11 netmask 255.255.255.0
> > node2 # ifconfig eth0 192.168.25.12 netmask 255.255.255.0
> >
> > Then and only then will cluster be able to bring up virtual ip address
> > and bind it as secondary on this interface. You can then see it with:
> >
> > # ip addr show
> >
> >
> > I guess you're trying to bring up IP address from network subnet that is
> > not in any way set up on your host. And that is a prerequisite with
> > classic IP resource.
> >
> >
> >
> >
> > --
> > Jakov Sosic
> > www.srce.hr
> >
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Fri, 24 Dec 2010 22:16:39 +0530
> > From: Parvez Shaikh <parvez.h.shaikh at gmail.com>
> > To: linux clustering <linux-cluster at redhat.com>
> > Subject: Re: [Linux-cluster] IP Resource behavior with Red Hat Cluster
> > Message-ID:
> >       <AANLkTinp=BFk0ssVkDieOvXVaQqeRfMDQgPbbessA-Qc at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Hi Jakov
> >
> > Thank you for your response. My two hosts have multiple network
> > interfaces or ethernet cards. I understood from your email, that the
> > IP corresponding to "cluster node name" for both hosts, should be in
> > the same subnet before a cluster could bring virtual IP up. I will
> > reconfirm if these are in same subnets.
> >
> > Gratefully yours,
> > Parvez
> >
> > On Fri, Dec 24, 2010 at 6:16 PM, Jakov Sosic <jakov.sosic at srce.hr>
> wrote:
> >> On 12/24/2010 09:41 AM, Parvez Shaikh wrote:
> >>> Hi Rajagopal,
> >>>
> >>> Thank you for your response
> >>>
> >>> I have created a cluster configuration by adding IP resource with
> >>> value 192.168.25.153 (some value) and created a service which just has
> >>> IP resource part of it. I have set all requisite configuration such
> >>> two node, node names, failover,fencing etc.
> >>>
> >>> Upon trying to start then service(enable service),it failed -
> >>>
> >>> clurgmgrd: [31853]: <debug> 192.168.25.135 is not configured
> >>>
> >>> Then manually added this IP to host
> >>>
> >>> ifconfig eth0:1 192.168.25.135
> >>>
> >>> Then service could start but it gave message -
> >>>
> >>> clurgmgrd: [31853]: <debug> 192.168.25.135 already configured
> >>>
> >>> So do I have to add virtual interface manually (as above or any other
> >>> method?) before I could start service with IP resource under it?
> >>
> >> How is your network configured? For an IP address to work in a cluster,
> >> you have to have interfaces on both machines set up, which are in the
> >> same subnet. For example:
> >>
> >> node1 # ifconfig eth0 192.168.25.11 netmask 255.255.255.0
> >> node2 # ifconfig eth0 192.168.25.12 netmask 255.255.255.0
> >>
> >> Then and only then will cluster be able to bring up virtual ip address
> >> and bind it as secondary on this interface. You can then see it with:
> >>
> >> # ip addr show
> >>
> >>
> >> I guess you're trying to bring up IP address from network subnet that is
> >> not in any way set up on your host. And that is a prerequisite with
> >> classic IP resource.
> >>
> >>
> >>
> >>
> >> --
> >> Jakov Sosic
> >> www.srce.hr
> >>
> >> --
> >> Linux-cluster mailing list
> >> Linux-cluster at redhat.com
> >> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>
> >
> >
> >
> > ------------------------------
> >
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-cluster
> >
> > End of Linux-cluster Digest, Vol 80, Issue 23
> > *********************************************
> >
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20101227/4c6e3ee9/attachment.htm>


More information about the Linux-cluster mailing list