I assume it's too late in the game to upgrade your dev/QA environments to AOLserver 4.0.8 and nsopenssl v3_0beta23, do the necessary smoke tests then attempt a re-deployment of your production env.? If it isn't, I'd suggest doing it to see if it makes the negative user experience go away.
I'd like to move back to 4 and I'll certainly make the suggestion but the problems we experienced with nsopenssl v3 verses the previous reliability of v2.1 will probably mean that other routes are exhausted first.
> Do you think these errors relate to a performance issue somewhere? Do > you think a change of config would help - I'm running with maxthreads > 20, minthreads 20, maxconnections 100 and maxkeepalive 0? No, and no. The bugs I had in mind caused the server to crash, and since that's not happening in your scenario, I'm only assuming that they aren't the cause of your problems.
I asked the config question because I'm concerned that its possibly related to performance as yesterday was the busiest day for the site so far. I was wondering if reducing the number of threads might improve throughput if the cpu is maxed out?
Going back to basics do we know what each of the nsopenssl errors and warnings mean and how significant they each are?
> mii-tool gives an error - I'll check that out tomorrow. ifconfig was my > first port of call and its showing 0 errors, 0 dropped, 0 overruns etc. > No problem there that I can see. At least ifconfig isn't showing errors. That's good news. mii-tool may throw an error if your NIC's driver doesn't support the PHY stuff. Gotta be some way to figure out what speed the NIC is connected at. Maybe this is a dead-end anyway ...
I'll ask the client to ask their ISP but I suspect its only connected on a 100 meg link. If it is a performance issue then having a gig connection would probably help.
> > (Maybe someone stepped on your ethernet cable in the co-lo recently.) > > Only if they climbed in the rack :-) Don't laugh ... I've had a host go off the 'net because the ethernet cable was run up inside the rack and while a new server was being slid into the rack, the cable got severed by one of the rails. "Is the link light on?" was a fun question to ask ...
I know what you mean we had an IBM engineer run over the ethernet cable of an AS/400 with the AS/400's own cabinet - that took some finding.
Steve
-- 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.
