I've been staring at this problem for a while now and can't seem to place my
finger on it.
I've compiled nsopenssl 3.x (CVS HEAD) against OpenSSL 0.9.7d, loading
nsopenssl in AOLserver 4.0 r3 appears to go flawless. Except for a OpenSSL
memory callback warning. The port nsopenssl listens to (443)
I had a very very similar problem.
ns_param maxthreads 5
ns_param minthreads 5
with minthreads 0, (and sometimes 1 or 2) it exhibited the same
behavior.
On Mon, 2004-05-03 at 02:02, Bart Teeuwisse wrote:
Notice: prebind: bound: 192.168.1.2:80
Notice: prebind: bound:
Torben,
excellent information -- duplicating the problem is 90% of the battle
and the info you've given here may be enough for me to do so.
thanks,
/s.
On May 2, 2004, at 12:50 AM, Torben Brosten wrote:
Scott,
Not sure if you solved this. I came across similar error conditions,
apparently
the
Hmm, I've changed the max/minthreads in ns/servers/server1 to no avail.
Scott, do you have any suggestions?
/Bart
On Mon, 3 May 2004 02:49:47 -0400, Chris Davies [EMAIL PROTECTED] wrote:
I had a very very similar problem.
ns_param maxthreads 5
ns_param minthreads 5
with
It's not a threading issue. AOLserver 4.x opens the listen sockets for
all comm modules including nsopenssl, and the error message is coming
from the DriverThread function in nsd/driver.c when it attempts to
start listening on the port. The reason it says nsopenssl is, well,
because that's the
We've upgraded from AOLserver v3.4 to v4.01 and have been having problems with the
server hanging intermittently without leaving any clues in the error log. The
AOLservers are running under SuSE 8.1 with Linux 2.4.19-64GB-SMP kernel.
Below are some 'ps' outputs of the AOLserver process in its
On 2004.05.03, Fen Tamanaha [EMAIL PROTECTED] wrote:
Sadly, there's nothing interesting in the logs. Here's the end of the
error and access logs from the latest hung server:
[03/May/2004:17:53:33][31889.9225][-sched:idle1-] Notice: starting
[03/May/2004:17:54:28][31889.5124][-conn:dawn::0]
Sadly, there's nothing interesting in the logs. Here's the end of the error and
access logs from the latest hung server:
[03/May/2004:17:53:33][31889.9225][-sched:idle1-] Notice: starting
[03/May/2004:17:54:28][31889.5124][-conn:dawn::0] Notice: dbdrv: opening database
'ora8:'
On 2004.05.03, Fen Tamanaha [EMAIL PROTECTED] wrote:
% ps -ef | grep 17072
UIDPID PPID C STIME TTY TIME CMD
nsadmin 17072 900 0 11:54 ?00:00:02 /apps/aolserver-4.01/bin/nsd -i -t
/web/aol-configs/web7-demo-8607.tcl -u nsuser -g nsgroup
nsadmin 17098 17072 0
On Mon, 2004-05-03 at 15:32, Scott Goodwin wrote:
It's not a threading issue. AOLserver 4.x opens the listen sockets for
all comm modules including nsopenssl, and the error message is coming
from the DriverThread function in nsd/driver.c when it attempts to
start listening on the port. The
On Mon, 3 May 2004 15:32:24 -0400, Scott Goodwin [EMAIL PROTECTED] wrote:
It's not a threading issue. AOLserver 4.x opens the listen sockets for
all comm modules including nsopenssl, and the error message is coming
from the DriverThread function in nsd/driver.c when it attempts to
start listening
11 matches
Mail list logo
