Pulse Reload configuration problem

rhurst at bidmc.harvard.edu rhurst at bidmc.harvard.edu
Wed Nov 14 17:43:13 UTC 2007


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: <http://listman.redhat.com/archives/piranha-list/attachments/20071114/8dce40d0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2178 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/piranha-list/attachments/20071114/8dce40d0/attachment.p7s>


More information about the Piranha-list mailing list