Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-11 Thread Nathaniel Haggard
After reordering the ns_sections in nsd.tcl to jive with http://aolserver.com/docs/admin/config-detailed.html as Torben recommends the new order goes like this: ns_section "ns/parameters" ns_section "ns/threads" ns_section "ns/mimetypes" ns_section "ns/encodings" ns_section "ns/servers" ns_section

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Scott Goodwin
I appreciate you and others pointing these issues out so I can track them down and fix them. Hopefully my "low-end" boxes will help in identifying these problems sooner. One box will be running Gentoo Linux, the other might be some form of *BSD. /s. On Aug 10, 2004, at 7:05 PM, Janine Sisk wrote: N

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Scott Goodwin
I guess low-end does sound a bit odd in the same sentence with 200 GB disk drives, but they're going into 500MHz and 800MHz Dell OptiPlexes, which can only fit one drive. I can certainly give you the 5GB and 10GB excess disks I'm pulling out of them if you pay postage :) /s. On Aug 10, 2004, at 5:4

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Janine Sisk
No problem, Scott, glad to hear you're still at it. I hope I didn't sound like I was complaining; I was just wanting to figure out who, if anyone, was maintaining the module. If I can help you sort this out, just let me know. janine On Aug 10, 2004, at 5:28 PM, Scott Goodwin wrote: My apologies f

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Cathy Sarisky
On Tue, 10 Aug 2004, Scott Goodwin wrote: > 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... LOL. I like your definition of low-end. Should you find yourself with an excess of low-end boxen, you can

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Scott Goodwin
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

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Andrew Piskorski
On Tue, Aug 10, 2004 at 04:23:25PM -0400, Janine Sisk wrote: > There haven't been any core files, and, well, I've never learned how to > use gdb so I wouldn't know what to look at anyway Using gdb to show the stack trace of a core file is easy. I generally do it from inside Emacs: In Emacs, d

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Janine Sisk
There haven't been any core files, and, well, I've never learned how to use gdb so I wouldn't know what to look at anyway janine On Aug 10, 2004, at 3:52 PM, Andrew Piskorski wrote: On Tue, Aug 10, 2004 at 02:59:31PM -0400, Janine Sisk wrote: FWIW, I've had this running since about 1 pm on Frid

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Andrew Piskorski
On Tue, Aug 10, 2004 at 02:59:31PM -0400, Janine Sisk wrote: > 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 Did you look at the

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Torben Brosten
I don't know, Nate, but I made these errors go away by changing the order of the ns_section definitions to the order described at: http://aolserver.com/docs/admin/config-detailed.html hth Torben Nathaniel Haggard wrote: Binding to port 8443 using the same setup that I mentioned in my first email fi

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Janine Sisk
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 y

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-10 Thread Nathaniel Haggard
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

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-09 Thread Nathaniel Haggard
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 i

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-09 Thread Nathaniel Haggard
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' fa

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Torben Brosten
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

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Janine Sisk
An update - the site did crash tonight, but there was no sign of it being SSL related in the error logs. It appears to have just *stopped*. No errors whatsoever. Hmph. janine On Aug 7, 2004, at 3:07 PM, Nathaniel Haggard wrote: AOLserver 4.0.7 with nsopenssl from cvs has problems. The following

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Torben Brosten
Nate, Is aolserver binding to the ssl port? I get a similar error when something is prebound to the port and so cannot bind to the port. 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. Torb

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Janine Sisk
Not a huge amount; there have been 28 orders placed in the last 24 hours, with each order going through somewhere in the neighborhood of 4 secure pages, plus all the admin pages but there probably hasn't been much of that going on today. But I was the one who had all the trouble with beta17, so w

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Nathaniel Haggard
How much SSL traffic do you have in a 24 hour period? Nate On Sat, 7 Aug 2004 15:26:27 -0400, Janine Sisk <[EMAIL PROTECTED]> wrote: > As it happens, I switched to using nsd 4.0.7 with the latest nsopenssl > from CVS about 24 hours ago. I am seeing a similar error: > > [07/Aug/2004:14:56:39][305

Re: [AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Janine Sisk
As it happens, I switched to using nsd 4.0.7 with the latest nsopenssl from CVS about 24 hours ago. I am seeing a similar error: [07/Aug/2004:14:56:39][30511.5126][-conn:live-nybooks::2] Warning: nsopenssl (live-nybooks): SSL interrupted, perhaps by client [07/Aug/2004:14:56:39][30511.5126][-conn:

[AOLSERVER] nsopenssl latest from CVS SSL error on reading data

2004-08-07 Thread Nathaniel Haggard
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