On Wednesday 10 April 2002 01:18, Rob Mayoff wrote:
I don't see a point in modifying the core to also parse Authentication:
Digest headers. I think Ns_SetRequestAuthorizeProc should be ripped
out and replaced with a new filter type, auth. Auth filters should
simply be run after preauth
SASL: http://www.oreillynet.com/pub/a/network/2002/04/09/sasl.html
...if you're feeling ambitious.
This would be manageable in the short term by restarting the server
occasionally if it weren't for the second biggest problem: at least half
the time, if not more, defunct threads are left behind when you kill nsd.
This usually prevents it from starting back up properly. Aack!
Any hints,
Support Requests item #475074, was opened at 2001-10-25 14:40
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=203152aid=475074group_id=3152
Category: Configuration: First-Time Startup
Group: aolserver3_1
Status: Open
Resolution: None
Priority: 5
Submitted By: Gabriel
+-- On Apr 10, Tom Jackson said:
I would try using daemontools to start and restart AOLserver. This tool
should correctly handle killing all children of the main process.
It probably won't. It sends signals only to its direct child.
I have one process I control with daemontools using
On 4/10/02 12:15 PM, Rob Mayoff [EMAIL PROTECTED] wrote:
From Janine's description, it sounds like the defunct threads are not
actually zombies, or else they are not direct children of the nsd
process that she's killing and their actual parent is not dead.
I was doing what I do with later
On Wednesday 10 April 2002 12:38 pm, Janine Sisk wrote:
This is on 7.2, btw, not 6.2 - on 6.2 it works ok. On 7.2 it most
definitely does not. This site ran ok on Solaris, too - it had some
problems there but this was not one of them.
7.2's glibc is so much newer than 6.2's that the linkage
+-- On Apr 10, Lamar Owen said:
7.2's glibc is so much newer than 6.2's that the linkage may be broken.
Binaries linked/compiled under 6.2 usually do _not_ work properly on 7.2.
Even with the compat libraries installed. The reason seems to be kernel 2.4.
To use some JVMs on 2.4, you
Now that's an interesting idea - I did have to set that while installing
Oracle, though it seems to run fine without it, and IIRC I had to set it to
install OpenACS on a 7.2 system, too.
I'll try it and see if it helps.
janine
On 4/10/02 1:00 PM, Rob Mayoff [EMAIL PROTECTED] wrote:
I've got the site programmer working on seeing if we can do a quick 3.3
upgrade, but any suggestions for coping in the meantime will be welcome.
I'm starting to think about doing the restart on a 15 minute interval, which
is getting to be a bit ridiculous!
Maybe the /NS/ can still be done
On 2002.04.10, Janine Sisk [EMAIL PROTECTED] wrote:
This is on 7.2, btw, not 6.2 - on 6.2 it works ok. On 7.2 it most
definitely does not. This site ran ok on Solaris, too - it had some
problems there but this was not one of them.
Could this be a glibc version issue? 2.3.3 is only
Kevin,
I haven't seen a response from you. Did you solve your problem?
-- Dossy
On 2002.04.09, Dossy [EMAIL PROTECTED] wrote:
On 2002.04.09, Kevin Lawver [EMAIL PROTECTED] wrote:
Hi all,
I'm trying to build the MySQL driver for AOLserver and am running into
a problem I can't
You know, I really think Rob is on to something here. Not only is the
number of threads not increasing so fast, I just saw it go *down* by one for
the first time. And the site has not hiccuped since I made this change,
though it is still being restarted every 30 minutes so that's not quite the
The AOLserver weekly chat takes place tomorrow, 2002-04-11, and
every Thursday. Common topics include AOLserver, Tcl, SQL, ACS,
and general web-related questions.
The place: AIM chatroom AOLserver on exchange 4
The time: 20:00 UTC
During the summer, that time is
4 PM US/Eastern
3 PM
Of course, it's not going to be *that* simple...
There seem to be two different symptoms here. One is that the server just
stops responding, even though it does not have a huge number of thread going
and nothing is visibly wrong. That seems to have gone away with Rob's
LD_ASSUME_KERNEL idea.
Does netstat -np still show their tcpip connection as open?
On Wednesday 10 April 2002 01:52 pm, you wrote:
Of course, it's not going to be *that* simple...
There seem to be two different symptoms here. One is that the server just
stops responding, even though it does not have a huge number
It does so far (we're up to 35 threads, and the server was just restarted 7
minutes ago!). I'll run it next time it goes busy and let you know how it
looks then.
janine
On 4/10/02 3:15 PM, David Walker [EMAIL PROTECTED] wrote:
Does netstat -np still show their tcpip connection as open?
On
Not sure but normally on my servers the connections come and go quickly
enough to not have more than a couple showing connected in netstat. (With
the exception of a couple of slow pages)
I'm wondering if the 24 connected is related to the 25 MaxBusy.
On Wednesday 10 April 2002 02:16 pm, you
It seems there are *always* 24 nsd processes connected, no matter how many
are really running.
BTW, a few of these are probably from different processes; there are two
other nsds running on this system. Only this one is running away like this,
though.
janine
On 4/10/02 3:49 PM, David Walker
19 matches
Mail list logo
