FWIW, I saw those messages too, when I was using nsopenssl2.1, and I
see similar ones using AOLserver 4 and the latest nsopenssl. The only
difference is that I've never had a user complaint related to them, so
I was assuming that they were victimless crimes. Perhaps that is not
the case, though we usually do hear pretty quickly if something's not
working right from the user's perspective.
janine
On Oct 25, 2004, at 5:05 PM, Dossy Shiobara wrote:
On 2004.10.25, Steve <[EMAIL PROTECTED]> wrote:
They seem to cause a variety of errors in different browsers. I've
been
on the receiving end of one of these and in Mozilla it gave a popup
message:
Are you able to reproduce this error on demand? Or is it completely
random?
Unfortunately the logs are going to quickly for me to determine which
error gave the message. The site is getting to be very busy in the run
up to halloween so I wondered if it was related to the load apart from
these errors the system doesn't seem to have any problems and the
response is good.
What do you mean by "going too quickly"? Aren't you logging to disk?
Can't you just roll the log and then inspect it at your leisure?
I'd be grateful is someone could shed some light on these errors or
point me at a way to diagnose the problem without adversely effecting
the site.
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? 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? Is there a
RDBMS involved, and is it running on its own dedicated host? On the
same network segment? Do you serve static assets from these front-end
hosts, or are you using a dedicated server for them and/or a CDN?
This is just a short list of questions to get a better picture of what
you're running, what your network architecture looks like and some
things I've personally seen before that could possibly be responsible
for the badness you're seeing. Lets eliminate the low-hanging fruit
first ...
-- 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.
--
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.
