From jimmy.nimo at pranical.com Mon Nov 5 17:51:15 2007 From: jimmy.nimo at pranical.com (jimmy.nimo at pranical.com) Date: Mon, 5 Nov 2007 13:51:15 -0400 Subject: piranha problem server not working Message-ID: <20071105135115.5mnnv4bwcbqoskw4@webmail.pranical.com> Hello, thanks for reading my email, I have a problem and perphaps someone in the list can work it out I have 3 working redhat 4 update 5 trying to work with piranha+lvs+nanny, 2 Real Server and 1 LVS Router, the router have 2 NIC, 1 with IP 172.16.247.130(eht0), and the other with 10.11.12.9(eth1), the real server are 10.11.12.11 and 10.11.12.12, I want to put the virtual server to run in the ip 172.16.247.150 (eth0:1) and the gateway in the real servers are 10.11.12.10 (eth1:1 in the router server), I create the lvs.cf with piranha and start pulse, but, NOTHING happens, piranha create the 10.11.12.10 and the 172.16.247.150 virtual interfaces (I can conect to the gui of piranha in http://172.16.247.150:3636) but can't do in the port 80. here are my lvs.cf serial_no = 137 primary = 172.16.247.130 primary_private = 10.11.12.9 service = lvs backup_active = 0 backup = 172.16.247.131 backup_private = 10.11.12.11 heartbeat = 1 heartbeat_port = 539 keepalive = 3 deadtime = 10 network = nat nat_router = 10.11.12.10 eth1:1 nat_nmask = 255.255.255.0 debug_level = NONE monitor_links = 0 virtual http { active = 1 address = 172.16.247.150 eth0:1 vip_nmask = 255.255.255.0 port = 80 use_regex = 0 load_monitor = ruptime scheduler = rr protocol = tcp timeout = 5 reentry = 5 quiesce_server = 0 server uno { address = 10.11.12.11 active = 1 weight = 1 } server dos { address = 10.11.12.12 active = 1 weight = 1 } } and I don't know why, but the ipsvadmin don't show the entrys of the real servers: [root at node1 ~]# ipvsadm -Ln IP Virtual Server version 1.2.0 (size=4096) Prot LocalAddress:Port Scheduler Flags -> RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 172.16.247.150:80 rr can anyone help me? (sorry for my bad english) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-keys Size: 1340 bytes Desc: Clave PGP p?blica URL: From Michael.Geraghty at cognotec.com Wed Nov 14 14:32:07 2007 From: Michael.Geraghty at cognotec.com (Michael Geraghty) Date: Wed, 14 Nov 2007 14:32:07 -0000 Subject: Pulse Reload configuration problem Message-ID: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com> Hi I am running "ipvsadm-1.24-6" on Redhat 4/4 ES. I have the system configured using piranha and works very well apart from one thing .. The problem I am having is when I change the configuration when adding a new site/VIP - I have to restart all nanny procs. The command 'service pulse restart' will not work for me. I get the following in my messages file: rereading configuration file pulse: pulse -HUP succeeded But the new nanny processes do not start up. I also tried "kill -1 pid" - but no joy. The only thing that will work is a "service pulse restart" - which is not good as there are several web servers live. Any ideas or suggestions would be great Thanks Mick *********************************************************************************************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. *********************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhurst at bidmc.harvard.edu Wed Nov 14 14:55:45 2007 From: rhurst at bidmc.harvard.edu (rhurst at bidmc.harvard.edu) Date: Wed, 14 Nov 2007 09:55:45 -0500 Subject: Pulse Reload configuration problem In-Reply-To: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com> References: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com> Message-ID: <1195052145.23963.52.camel@xw9300.bidmc.harvard.edu> Just wondering, if you are only servicing web servers, why would restarting it be an issue? I have restarted pulse with other protocols, and it is quick enough to resume the session, i.e. the keepalive on ssh, telnet, and other IP connections. Once in a while (usually from a misconfiguration), you might lose client connection because of the timing. On Wed, 2007-11-14 at 14:32 +0000, Michael Geraghty wrote: > Hi > > > > I am running ?ipvsadm-1.24-6? on Redhat 4/4 ES. I have the system > configured using piranha and works very well apart from one thing .. > > > > The problem I am having is when I change the configuration when adding > a new site/VIP ? I have to restart all nanny procs. The command > ?service pulse restart? will not work for me. I get the following in > my messages file: > > > > rereading configuration file > > pulse: pulse -HUP succeeded > > > > But the new nanny processes do not start up. I also tried ?kill -1 > pid? ? but no joy. The only thing that will work is a ?service pulse > restart? ? which is not good as there are several web servers live. > > > > Any ideas or suggestions would be great > > > > Thanks > > > > Mick > > > > > > > > > *********************************************************************************************** > This email, its contents and any files attached are a confidential > communication and are > intended only for the named addressees indicated in the message. > > If you are not the named addressee or if you have received this email > in error, you may not, > without the consent of Cognotec, copy, use or rely on any information > or attachments in any way. > Please notify the sender by return email and delete it from your email > system. > > Unless separately agreed, Cognotec does not accept any responsibility > for the accuracy or > completeness of the contents of this email or its attachments. Please > note that any views, > opinion or advice contained in this communication are those of the > sending individual > and not those of Cognotec and Cognotec shall have no liability > whatsoever in relation to > this communication (or its content) unless separately agreed. > *********************************************************************************************** > > > _______________________________________________ > Piranha-list mailing list > Piranha-list at redhat.com > https://www.redhat.com/mailman/listinfo/piranha-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2178 bytes Desc: not available URL: From Michael.Geraghty at cognotec.com Wed Nov 14 14:59:13 2007 From: Michael.Geraghty at cognotec.com (Michael Geraghty) Date: Wed, 14 Nov 2007 14:59:13 -0000 Subject: Pulse Reload configuration problem In-Reply-To: <1195052145.23963.52.camel@xw9300.bidmc.harvard.edu> References: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com > <1195052145.23963.52.camel@xw9300.bidmc.harvard.edu> Message-ID: <53E3BF543C3DBA4592A60FA1E062F63305B6EA6B@dubex2003.cognotec.com> I am just servicing web services - but just paranoid because these are production servers and am afraid that the others won't come back online. Also, the documentation says the 'service pulse restart' reloads the configuration - so would prefer to use what it says on the tin ________________________________ From: piranha-list-bounces at redhat.com [mailto:piranha-list-bounces at redhat.com] On Behalf Of rhurst at bidmc.harvard.edu Sent: 14 November 2007 14:56 To: piranha-list at redhat.com Subject: Re: Pulse Reload configuration problem Just wondering, if you are only servicing web servers, why would restarting it be an issue? I have restarted pulse with other protocols, and it is quick enough to resume the session, i.e. the keepalive on ssh, telnet, and other IP connections. Once in a while (usually from a misconfiguration), you might lose client connection because of the timing. On Wed, 2007-11-14 at 14:32 +0000, Michael Geraghty wrote: Hi I am running "ipvsadm-1.24-6" on Redhat 4/4 ES. I have the system configured using piranha and works very well apart from one thing .. The problem I am having is when I change the configuration when adding a new site/VIP - I have to restart all nanny procs. The command 'service pulse restart' will not work for me. I get the following in my messages file: rereading configuration file pulse: pulse -HUP succeeded But the new nanny processes do not start up. I also tried "kill -1 pid" - but no joy. The only thing that will work is a "service pulse restart" - which is not good as there are several web servers live. Any ideas or suggestions would be great Thanks Mick ************************************************************************ *********************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. ************************************************************************ *********************** _______________________________________________ Piranha-list mailing list Piranha-list at redhat.com https://www.redhat.com/mailman/listinfo/piranha-list *********************************************************************************************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. *********************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michael.Geraghty at cognotec.com Wed Nov 14 15:08:17 2007 From: Michael.Geraghty at cognotec.com (Michael Geraghty) Date: Wed, 14 Nov 2007 15:08:17 -0000 Subject: Pulse Reload configuration problem In-Reply-To: <53E3BF543C3DBA4592A60FA1E062F63305B6EA6B@dubex2003.cognotec.co m> References: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com > <1195052145.23963.52.camel@xw9300.bidmc.harvard.edu> <53E3BF543C3DBA4592A60FA1E062F63305B6EA6B@dubex2003.cognotec.com> Message-ID: <53E3BF543C3DBA4592A60FA1E062F63305B6EA76@dubex2003.cognotec.com> Sorry - I meant 'service pulse reload' - this seems to work and re reads the lvs.cfg file as the messages file reads ... Nov 14 14:45:45 lvsrt1 lvs[1243]: rereading configuration file Nov 14 14:45:45 lvsrt1 pulse: pulse -HUP succeeded But, the new configuration / nanny procs do not get started Only 'service pulse restart' works ________________________________ From: piranha-list-bounces at redhat.com [mailto:piranha-list-bounces at redhat.com] On Behalf Of Michael Geraghty Sent: 14 November 2007 14:59 To: Piranha clustering/HA technology Subject: RE: Pulse Reload configuration problem I am just servicing web services - but just paranoid because these are production servers and am afraid that the others won't come back online. Also, the documentation says the 'service pulse restart' reloads the configuration - so would prefer to use what it says on the tin ________________________________ From: piranha-list-bounces at redhat.com [mailto:piranha-list-bounces at redhat.com] On Behalf Of rhurst at bidmc.harvard.edu Sent: 14 November 2007 14:56 To: piranha-list at redhat.com Subject: Re: Pulse Reload configuration problem Just wondering, if you are only servicing web servers, why would restarting it be an issue? I have restarted pulse with other protocols, and it is quick enough to resume the session, i.e. the keepalive on ssh, telnet, and other IP connections. Once in a while (usually from a misconfiguration), you might lose client connection because of the timing. On Wed, 2007-11-14 at 14:32 +0000, Michael Geraghty wrote: Hi I am running "ipvsadm-1.24-6" on Redhat 4/4 ES. I have the system configured using piranha and works very well apart from one thing .. The problem I am having is when I change the configuration when adding a new site/VIP - I have to restart all nanny procs. The command 'service pulse restart' will not work for me. I get the following in my messages file: rereading configuration file pulse: pulse -HUP succeeded But the new nanny processes do not start up. I also tried "kill -1 pid" - but no joy. The only thing that will work is a "service pulse restart" - which is not good as there are several web servers live. Any ideas or suggestions would be great Thanks Mick ************************************************************************ *********************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. ************************************************************************ *********************** _______________________________________________ Piranha-list mailing list Piranha-list at redhat.com https://www.redhat.com/mailman/listinfo/piranha-list ************************************************************************ *********************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. ************************************************************************ *********************** *********************************************************************************************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. *********************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhurst at bidmc.harvard.edu Wed Nov 14 17:43:13 2007 From: rhurst at bidmc.harvard.edu (rhurst at bidmc.harvard.edu) Date: Wed, 14 Nov 2007 12:43:13 -0500 Subject: Pulse Reload configuration problem In-Reply-To: <53E3BF543C3DBA4592A60FA1E062F63305B6EA76@dubex2003.cognotec.com> References: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com > <1195052145.23963.52.camel@xw9300.bidmc.harvard.edu> <53E3BF543C3DBA4592A60FA1E062F63305B6EA6B@dubex2003.cognotec.com> <53E3BF543C3DBA4592A60FA1E062F63305B6EA76@dubex2003.cognotec.com> Message-ID: <1195062193.24894.16.camel@xw9300.bidmc.harvard.edu> Yes, we see that same behavior too. But, the Linux ipvs table does not get flushed on a pulse restart. So as long as your pulse configuration is correct, you can safely restart it, and all client connections will resume. Also make certain your backup pulse service is downed BEFORE restarting the primary pulse, so it won't failover -- it's an active-passive config, so you would LOSE the ipvs table by going over to the other server. Now if RHEL only included keepalived as part of piranha . . . I do wish that the nanny processes could be manually spawned, and at the very least, have some kind of command-line identifier so I know which is serving which, instead relying upon syslog messages. On Wed, 2007-11-14 at 15:08 +0000, Michael Geraghty wrote: > Sorry ? I meant ?service pulse reload? - this seems to work and re > reads the lvs.cfg file as the messages file reads ? > > > > Nov 14 14:45:45 lvsrt1 lvs[1243]: rereading configuration file > > Nov 14 14:45:45 lvsrt1 pulse: pulse -HUP succeeded > > > > But, the new configuration / nanny procs do not get started > > > > Only ?service pulse restart? works > > > > > > ______________________________________________________________________ > > From:piranha-list-bounces at redhat.com > [mailto:piranha-list-bounces at redhat.com] On Behalf Of Michael Geraghty > Sent: 14 November 2007 14:59 > To: Piranha clustering/HA technology > Subject: RE: Pulse Reload configuration problem > > > > > > I am just servicing web services ? but just paranoid because these are > production servers and am afraid that the others won?t come back > online. Also, the documentation says the ?service pulse restart? > reloads the configuration ? so would prefer to use what it says on the > tin > > > > > > ______________________________________________________________________ > > From:piranha-list-bounces at redhat.com > [mailto:piranha-list-bounces at redhat.com] On Behalf Of > rhurst at bidmc.harvard.edu > Sent: 14 November 2007 14:56 > To: piranha-list at redhat.com > Subject: Re: Pulse Reload configuration problem > > > > > > Just wondering, if you are only servicing web servers, why would > restarting it be an issue? I have restarted pulse with other > protocols, and it is quick enough to resume the session, i.e. the > keepalive on ssh, telnet, and other IP connections. Once in a while > (usually from a misconfiguration), you might lose client connection > because of the timing. > > > On Wed, 2007-11-14 at 14:32 +0000, Michael Geraghty wrote: > > Hi > > > > I am running ?ipvsadm-1.24-6? on Redhat 4/4 ES. I have the system > configured using piranha and works very well apart from one thing .. > > > > The problem I am having is when I change the configuration when adding > a new site/VIP ? I have to restart all nanny procs. The command > ?service pulse restart? will not work for me. I get the following in > my messages file: > > > > rereading configuration file > > pulse: pulse -HUP succeeded > > > > But the new nanny processes do not start up. I also tried ?kill -1 > pid? ? but no joy. The only thing that will work is a ?service pulse > restart? ? which is not good as there are several web servers live. > > > > Any ideas or suggestions would be great > > > > Thanks > > > > Mick > > > > > > > > > > *********************************************************************************************** > > This email, its contents and any files attached are a confidential > > communication and are > > intended only for the named addressees indicated in the message. > > > > If you are not the named addressee or if you have received this > > email in error, you may not, > > without the consent of Cognotec, copy, use or rely on any > > information or attachments in any way. > > Please notify the sender by return email and delete it from your > > email system. > > > > Unless separately agreed, Cognotec does not accept any > > responsibility for the accuracy or > > completeness of the contents of this email or its attachments. > > Please note that any views, > > opinion or advice contained in this communication are those of the > > sending individual > > and not those of Cognotec and Cognotec shall have no liability > > whatsoever in relation to > > this communication (or its content) unless separately agreed. > > *********************************************************************************************** > > > > > > > > > > _______________________________________________ > > Piranha-list mailing list > > Piranha-list at redhat.com > > https://www.redhat.com/mailman/listinfo/piranha-list > > > *********************************************************************************************** > This email, its contents and any files attached are a confidential > communication and are > intended only for the named addressees indicated in the message. > > If you are not the named addressee or if you have received this email > in error, you may not, > without the consent of Cognotec, copy, use or rely on any information > or attachments in any way. > Please notify the sender by return email and delete it from your email > system. > > Unless separately agreed, Cognotec does not accept any responsibility > for the accuracy or > completeness of the contents of this email or its attachments. Please > note that any views, > opinion or advice contained in this communication are those of the > sending individual > and not those of Cognotec and Cognotec shall have no liability > whatsoever in relation to > this communication (or its content) unless separately agreed. > *********************************************************************************************** > > > *********************************************************************************************** > This email, its contents and any files attached are a confidential > communication and are > intended only for the named addressees indicated in the message. > > If you are not the named addressee or if you have received this email > in error, you may not, > without the consent of Cognotec, copy, use or rely on any information > or attachments in any way. > Please notify the sender by return email and delete it from your email > system. > > Unless separately agreed, Cognotec does not accept any responsibility > for the accuracy or > completeness of the contents of this email or its attachments. Please > note that any views, > opinion or advice contained in this communication are those of the > sending individual > and not those of Cognotec and Cognotec shall have no liability > whatsoever in relation to > this communication (or its content) unless separately agreed. > *********************************************************************************************** > > > _______________________________________________ > Piranha-list mailing list > Piranha-list at redhat.com > https://www.redhat.com/mailman/listinfo/piranha-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2178 bytes Desc: not available URL: From Michael.Geraghty at cognotec.com Fri Nov 16 08:03:01 2007 From: Michael.Geraghty at cognotec.com (Michael Geraghty) Date: Fri, 16 Nov 2007 08:03:01 -0000 Subject: Pulse Reload configuration problem In-Reply-To: <1195062193.24894.16.camel@xw9300.bidmc.harvard.edu> References: <53E3BF543C3DBA4592A60FA1E062F63305B6EA59@dubex2003.cognotec.com > <1195052145.23963.52.camel@xw9300.bidmc.harvard.edu><53E3BF543C3DBA4592A60F A1E062F63305B6EA6B@dubex2003.cognotec.com><53E3BF543C3DBA4592A60FA1E062F633 05B6EA76@dubex2003.cognotec.com> <1195062193.24894.16.camel@xw9300.bidmc.harvard.edu> Message-ID: <53E3BF543C3DBA4592A60FA1E062F63305B6EDFC@dubex2003.cognotec.com> I agree - a restart will not disconnect any current connections. But, as the nanny processes are restarting you cannot get access to any of the sites. I know this is only 20-30 seconds, but in a production world this is not acceptable and would be deemed to risky. There must be a fix out there for reloading this configuration? ________________________________ From: piranha-list-bounces at redhat.com [mailto:piranha-list-bounces at redhat.com] On Behalf Of rhurst at bidmc.harvard.edu Sent: 14 November 2007 17:43 To: piranha-list at redhat.com Subject: RE: Pulse Reload configuration problem Yes, we see that same behavior too. But, the Linux ipvs table does not get flushed on a pulse restart. So as long as your pulse configuration is correct, you can safely restart it, and all client connections will resume. Also make certain your backup pulse service is downed BEFORE restarting the primary pulse, so it won't failover -- it's an active-passive config, so you would LOSE the ipvs table by going over to the other server. Now if RHEL only included keepalived as part of piranha . . . I do wish that the nanny processes could be manually spawned, and at the very least, have some kind of command-line identifier so I know which is serving which, instead relying upon syslog messages. On Wed, 2007-11-14 at 15:08 +0000, Michael Geraghty wrote: Sorry - I meant 'service pulse reload' - this seems to work and re reads the lvs.cfg file as the messages file reads ... Nov 14 14:45:45 lvsrt1 lvs[1243]: rereading configuration file Nov 14 14:45:45 lvsrt1 pulse: pulse -HUP succeeded But, the new configuration / nanny procs do not get started Only 'service pulse restart' works ________________________________ From:piranha-list-bounces at redhat.com [mailto:piranha-list-bounces at redhat.com] On Behalf Of Michael Geraghty Sent: 14 November 2007 14:59 To: Piranha clustering/HA technology Subject: RE: Pulse Reload configuration problem I am just servicing web services - but just paranoid because these are production servers and am afraid that the others won't come back online. Also, the documentation says the 'service pulse restart' reloads the configuration - so would prefer to use what it says on the tin ________________________________ From:piranha-list-bounces at redhat.com [mailto:piranha-list-bounces at redhat.com] On Behalf Of rhurst at bidmc.harvard.edu Sent: 14 November 2007 14:56 To: piranha-list at redhat.com Subject: Re: Pulse Reload configuration problem Just wondering, if you are only servicing web servers, why would restarting it be an issue? I have restarted pulse with other protocols, and it is quick enough to resume the session, i.e. the keepalive on ssh, telnet, and other IP connections. Once in a while (usually from a misconfiguration), you might lose client connection because of the timing. On Wed, 2007-11-14 at 14:32 +0000, Michael Geraghty wrote: Hi I am running "ipvsadm-1.24-6" on Redhat 4/4 ES. I have the system configured using piranha and works very well apart from one thing .. The problem I am having is when I change the configuration when adding a new site/VIP - I have to restart all nanny procs. The command 'service pulse restart' will not work for me. I get the following in my messages file: rereading configuration file pulse: pulse -HUP succeeded But the new nanny processes do not start up. I also tried "kill -1 pid" - but no joy. The only thing that will work is a "service pulse restart" - which is not good as there are several web servers live. Any ideas or suggestions would be great Thanks Mick ************************************************************************ *********************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. ************************************************************************ *********************** _______________________________________________ Piranha-list mailing list Piranha-list at redhat.com https://www.redhat.com/mailman/listinfo/piranha-list ************************************************************************ *********************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. ************************************************************************ *********************** ************************************************************************ *********************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. ************************************************************************ *********************** _______________________________________________ Piranha-list mailing list Piranha-list at redhat.com https://www.redhat.com/mailman/listinfo/piranha-list *********************************************************************************************** This email, its contents and any files attached are a confidential communication and are intended only for the named addressees indicated in the message. If you are not the named addressee or if you have received this email in error, you may not, without the consent of Cognotec, copy, use or rely on any information or attachments in any way. Please notify the sender by return email and delete it from your email system. Unless separately agreed, Cognotec does not accept any responsibility for the accuracy or completeness of the contents of this email or its attachments. Please note that any views, opinion or advice contained in this communication are those of the sending individual and not those of Cognotec and Cognotec shall have no liability whatsoever in relation to this communication (or its content) unless separately agreed. *********************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at vfive.com Fri Nov 30 19:19:28 2007 From: brian at vfive.com (Brian Ghidinelli) Date: Fri, 30 Nov 2007 11:19:28 -0800 Subject: Can piranha failover all ethernet interfaces? Message-ID: <47506240.3060202@vfive.com> I'm using Piranha via CentOS-5 on 2 firewall/gateway boxes that sit in front of 3 segmented networks. My network looks like so: 192.168.2.100 (public VIP) 192.168.2.101 (fw 1) 192.168.2.102 (fw 2) 10.64.1.1 (internal VIP, nat_router) 10.64.1.2 (fw 1) 10.64.1.3 (fw 2) 10.64.1.20 (http real server 1) 10.64.1.21 (http real server 2) This part is working great. However, I also have: 10.64.2.10 (http box, not part of lvs) 10.64.3.10 (database server, not part of lvs) What I want is: 10.64.2.1 (floating VIP) 10.64.2.2 (fw 1) 10.64.2.3 (fw 2) 10.64.3.1 (floating VIP) 10.64.3.2 (fw 1) 10.64.3.3 (fw 2) And these interfaces should failover whenever the primary nat_router is failed over so that the boxes in 10.64.2 and .3, which depend on the firewall/gateway for routing, will continue to have network access. Can piranha do this? Thanks! Brian