On 2004.10.25, Steve <[EMAIL PROTECTED]> wrote: > > How large is the nsd process memory footprint? What modules are you > > loading? Did you upgrade anything at ALL lately? What OS is this on? > > Is it a single front-end host or a farm of them? If it's a farm, is it > > behind a load balancer, if so what make/model? > > OK its OACS 5.1 so apart from nsopenssl its loading tDom, nspostgres, > nssha1 and nscache. We haven't changed anything in over a week. its > Linux 2.4 series kernel on a single host.
Does OACS 5.1 support AOLserver 3.3 still? There's been a series of bugs fixed in nsopenssl 3 and AOLserver 4 that have not been backported to older nsopenssl 2.1a and AOLserver 3 -- you could be getting bitten by one of those. However, those were all server-crashing bugs so if your nsd isn't crashing/restarting, then perhaps <jedi>these are not the bugs you are looking for ... move along</jedi>. > > Is your upstream bandwidth > > provider having routing issues? What kind of uplink exists on the host > > (10mbit, 100mbit, half or full duplex, configured or auto-negotiate)? > > What make/model switch is/are the hosts connected to? Are the switches > > configured or auto-negotiate? Is there any other traffic on your > > network segment or is it just these front-end webservers? > > Its co-lo. I've asked the host company to check the routing but so far > they haven't turned up anything they'd admit too. Check the output of "mii-tool" and see if it's actually negotiated a gig-e connection and if it's full/half duplex, etc. Check output of ifconfig and see if you're seeing any packet loss/etc. Basically, if any of the error counters are non-zero, you have some investigation to do ... (Maybe someone stepped on your ethernet cable in the co-lo recently.) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
