Re: LVS Total Lockup x 2 Systems

Brian/BMAN,

 Direct replies to your questions follow:

(resending w/o attachment)
>> = you
> = me

> --- "Brian Gray (BMan)" <[email protected]> wrote:
> > What errata have you applied besides apache?
> > (2.4.9.31 kernel is not the
> > latest by the way.)  What pirnaha version are you
> > running?
> 
> I've applied errata using "up2date --update"
> which updates everything except kernels which I 
> usually do manually.  In short, ALL ERRATA that
> Red Hat put out (except kernel) were applied. 
> I did NOT update to 2.4.9-34 because I saw a report
> form someone up the list whose Piranha/LVS BROKE as
> a
> result apparently something different or ip_vs not 
> compiled in or whatever that cause the breakage.
> 
> I'm running the following versions of piranha and
> other requirements - also reminding you that this
> ran
> w/o a problem for 90 days !!!
> 
> piranha-0.6.0-19.i386.rpm
> scsi-reserve-0.7-6.i386.rpm
> scsi-reserve-devel-0.7-6.i386.rpm
> ipvsadm-1.18-8.i386.rpm
> 
> I did not stray from using these piranha versions
> because they worked SO WELL for 90 days straight.
> Again, I did not upgr to k2.4.9-34 because someone
> on the list complained that version broke their 
> piranha/lvs. 
> 
> 
> > 
> > "rpm -qa --last" will show recently installed
> rpms. 
> > You can also look
> > at the source to see what libraries piranha uses.
> > 
> 
> I attached the text output of rpm -qa --last 
> for your inspection should you take on this 
> mission ;-) it's not that big.....
> 
> > So the question I'm getting to here is, what
> besides
> > apache has
> > changed?  Once you find out everything that has
> > changed, start to
> > question what effects, if any, these have on
> 
> ERRATA only have changed, not Piranha versions nor
> piranha configs.  There have been NO changes to
> apache
> configuration files, only the versions of apache and
> other errata running on my real servers and errata
> on
> the piranha boxes.
> 
> > piranha.  Pertaining to
> > Apache, did it change a conf, redirect, proxy or
> > module like php???  Did
> > you restart apache after the upgrade?  Can you get
> > the pirnha-gui via
> > browser or telnet into the servers port 80?
> 
> 
> Again, NO changes to piranha configs, no changes to
> apache configs, only the version of apache and other
> errata, however piranha versions remain the same.
> Yes
> apache was restarted as I updated the Apache errata
> from Red Hat which fixes the recent security issue.
> I
> no longer run Piranha_GUI all the time, but when I
> do
> have it started, YES I can get to
> http://piranha:3636
> and yes apache is serving up 80 and 443 correctly
> (ie.
> Piranha is routing normally to the real servers.)
> 
> > 
> > God Luck.
> > 
> 
> I suppose this is some kind of extra-special case of
> good luck wish ;-) though it sort of feels like one
> that leaves me left out in the blue with lots of
> clouds. ;-) (Kidding of course.)
> 
> Thanks
> Peter
> 
> PS: My next step was to write my very own
> heartbeat+failover handler perl script which you can
> find at http://peterbaitz.com/lvs.html
> since the Piranha still functions fine - but needed
> the
> backup of the failover strategy since the lockups
> started randomly (usually seperated by days and
> sometimes many hours). Recently its gone 5 days
> w/o a hitch but can't bet on it anymore....
> 


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com