At 01:03 PM 7/24/01 -0400, you wrote:
>Rocael,
>
>Are you using nsvhr? I'm pretty sure Jerry is ...
>
>I noticed some funny bugs with nsvhr that cause it to kill
>the nsd process .. I haven't had the time to track down the
>actual problem (it was quicker to just add my AOLserver
>hosts to my system monitoring toolkit, which restarts
>services if they fail).
>
>-- Dossy
Dossy can you be more specific. Which process do you think nsvhr is
killing, the master server or the proxies?
I am using nsvhr, but that's only in one server, and the others are using
nsunix.
The nsvhr master hasn't died yet, and I don't know if that is because nsvhr
is killing the others (destory, m u s t d e s t r o y), or because the
nsvhr server is actually the simplest server: know scheduled procs, no
filters, no pages to serve, no database drivers, nothing but: get
connection, switch connect, lather, rinse, repeat.
Are the nsunix servers dying because of nsunix or for some other reason? I
am inclined to believe the latter, as a) nsunix hasn't changed for months,
and b) many (most?) of these crashes have occurred in the dead of night
when there has been no traffic to those particular servers, but at times
when there have been various scheduled procs running. (I can tell there
has been no traffic since neither the crashing server nor the nsvhr master
reported any traffic.)
But I am always looking for more information....
I'm really annoyed by this. I've been using AOLserver for almost two years
now, and this is the first time I've ever experienced any instability that
would lead me to setting up a keepalive service.
Jerry
=====================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
