My apologies for not being more reponsive; I've been very busy at NASA
these past six months. I'm getting ready to use nsopenssl for the sites
we're building here so I'll be fixing any problems you're seeing in the
next few weeks. I suspect I'm not seeing many of the errors when my
tests are being run on the same machine as the web server, so I've
purchased two low-end intel boxes to set up a test network and run load
tests across ethernet; just waiting for two 200GB drives to arrive so I
can install OSs. I did get the SSL error pointed out in this thread and
had an image or two not load when I tested last night on my powerbook;
under a much heavier load I should be able to track down the problem.
thanks,
/s.
On Aug 10, 2004, at 2:59 PM, Janine Sisk wrote:
That's really interesting... all I can think of is a permissions
problem, but then it wouldn't work at all.
FWIW, I've had this running since about 1 pm on Friday, so four days
now. In that time we've had 8 unexplained crashes, or an average of 2
per day. Although four of them were yesterday so you might expect it
to be load related, but there have been none so far today.
During that same time there have been 67 SSL_ERRORs reported. Although
it's obviously too many, it's not the level of spewing I was getting
with the beta17 version nor what Nate is experiencing.
Anyone have any ideas? I guess Scott isn't working on the module
anymore? I'm not really qualified to try to fix this, unfortunately,
or I would have tried already.
janine
On Aug 10, 2004, at 11:56 AM, Nathaniel Haggard wrote:
Binding to port 8443 using the same setup that I mentioned in my first
email fixes the problems I was having with too many log entries of
this nature:
07/Aug/2004:12:56:00][27466.7176][-conn:server1::2] Debug:
SSLOp(27-0): SSL_ERROR_SSL: bytes = 16000; total = 0; rc = -1
Why would port number matter?
Nate
On Mon, 9 Aug 2004 16:56:06 -0600, Nathaniel Haggard
<[EMAIL PROTECTED]> wrote:
nsopenssl is using openssl 0.9.6b, is that a problem?
openssl3.0beta21 with aolserver4.0.7 gives similar results. The
server actually crashed even more frequently but that might be due to
traffic.
Nate
On Mon, 9 Aug 2004 10:21:01 -0600, Nathaniel Haggard
<[EMAIL PROTECTED]> wrote:
aolserver is binding to the ssl port. It is prebinding to port 443
(-b 0.0.0.0:80,0.0.0.0:443)
[07/Aug/2004:13:28:37][28040.1024][-main-] Notice: nsopenssl
(server1): 'users' certificate and key loaded successfully
[07/Aug/2004:13:28:37][28040.1024][-main-] Notice: nsopenssl
(server1): 'users' failed
to load CA certificate file
'/sm/aolserver/servers/server1/modules/nsopenssl/ca-client/ca-
client.crt'
[07/Aug/2004:13:28:37][28040.1024][-main-] Error: nsopenssl
(server1):
'users' CA certificate file is not readable or does not exist
The server crashed (and restarted because it's running from inittab)
4
times in the 20 minutes I had it running. Like Janine reported
there
was no explanation for the crash in the error.log; it just crasehd.
Nate
On Sat, 7 Aug 2004 21:56:27 -0700, Torben Brosten
<[EMAIL PROTECTED]> wrote:
Nate,
Is aolserver binding to the ssl port?
I get an identical error when something is prebound to the ssl port
and
so aolserver fails to bind to it.
A "failed to listen on.. address already in use" error shows up in
the
logfile just after server reports "listening on" same port, ie.
during
server startup.
Torben
ps. this is my 3rd attempt at posting this message. Hopefully this
time
there are no glitches. Sorry if this is a duplicate message.
Nathaniel Haggard wrote:
AOLserver 4.0.7 with nsopenssl from cvs has problems. The
following
messages are from the server.log while we tested the site. We
didn't
have any problems on the client side and all the pages come up as
usual.
[07/Aug/2004:12:56:00][27466.7176][-conn:server1::2] Debug:
SSLOp(27-0): SSL_ERROR_SSL: bytes = 16000; total = 0; rc = -1
[07/Aug/2004:12:56:00][27466.7176][-conn:server1::2] Error:
nsopenssl
(server1): SSL error on reading data
[07/Aug/2004:12:56:08][27466.7176][-conn:server1::2] Debug:
SSLOp(55-0): SSL_ERROR_SSL: bytes = 16000; total = 0; rc = -1
[07/Aug/2004:12:56:08][27466.7176][-conn:server1::2] Error:
nsopenssl
(server1): SSL error on reading data
[07/Aug/2004:13:00:29][27627.5126][-conn:server1::0] Debug:
SSLOp(19-0): SSL_ERROR_SSL: bytes = 16000; total = 0; rc = -1
[07/Aug/2004:13:00:29][27627.5126][-conn:server1::0] Error:
nsopenssl
(server1): SSL error on reading data
The server crashes every few minutes as well. Most of the entries
in
the server.log, which is growing at a rapid rate, are errors or
warning related to nsopenssl.
This looks like the problem you guys discussed earlier with
nsopenssl3.0beta.
Nate
--
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.
--
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.
--
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.
