On 2005.07.18, Janine Sisk <[EMAIL PROTECTED]> wrote:
> We've just moved a bunch of sites around and in the process they all 
> got upgraded to 4.0.10.  One of them is exhibiting some odd behavior 
> and I'd like to know if anyone has any idea what the problem might be.
    ...
> etc, etc and so forth.  Is it just so busy that it never has a chance 
> to fully shut down?  If so, this is new behavior since AOLserver 4.0.1, 
> which is what this site was running on before.  And what can I do to 
> fix it?

If you look in your server logs from when it was running 4.0.1, at
shutdown you probably saw an fatal error being logged.  If so, I suspect
you were taking "advantage" of SF Bug #1029918:

    http://aolserver.com/sf/bug/1029918

The note from the ChangeLog:

2004-09-17  Dossy Shiobara <[EMAIL PROTECTED]>

        * nsd/driver.c (1.17.2.9): "stopped" already initalized to 1, which
          means NsWaitDriversShutdown() will never timeout even when it
          should, which means trigPipe always gets closed immediately which
          causes DriverThread to Ns_Fatal() on line 848.  Closes SF Bug
          #1029918.

So, now your server really will wait until the shutdown timeout (default
20 seconds) before giving up and tearing down the server.

I've filed RFE #1029889 that will introduce [ns_info shutdownpending] so
that Tcl scripts, such as scheduled procs and other background threads
can detect that the server is shutting down, and exit/clean up as
appropriate.  Of course, this means that those background threads will
need to be modified to periodically test [ns_info shutdownpending] and
if it returns "true", to exit gracefully.

    http://aolserver.com/sf/rfe/1029889

Hope this helps,

-- Dossy

-- 
Dossy Shiobara                       mail: [EMAIL PROTECTED] 
Panoptic Computer Network             web: http://www.panoptic.com/ 
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)


--
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.

Reply via email to