On Jul 18, 2005, at 5:35 PM, Dossy Shiobara wrote:
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:
Nope, actually not:
[08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: nsmain:
AOLserver/4.0 stopping
[08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: serv: stopping
server: live-gmt
[08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: serv:
connection threads stopped
[08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: driver:
shutdown complete
[08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: sched:
shutdown pending
[08/Jul/2005:20:00:57][30673.3063348144][-sched-] Notice: sched:
shutdown started
[08/Jul/2005:20:00:57][30673.3063348144][-sched-] Notice: sched:
waiting for event threads...
[08/Jul/2005:20:00:57][30673.3045063600][-sched:idle1-] Notice: exiting
[08/Jul/2005:20:00:57][30673.3050306480][-sched:idle2-] Notice: exiting
[08/Jul/2005:20:00:57][30673.3048209328][-sched:idle0-] Notice: exiting
[08/Jul/2005:20:00:59][30673.3063348144][-sched-] Notice: sched:
shutdown complete
[08/Jul/2005:20:00:59][30673.3063348144][-shutdown-] Notice: nslog:
closing '/export/logs/live/live-gmt.log'
[08/Jul/2005:20:00:59][30673.3073912960][-main-] Notice: nsmain:
AOLserver/4.0 exiting
So, now your server really will wait until the shutdown timeout
(default
20 seconds) before giving up and tearing down the server.
It's staying in this state for a lot longer than 20 seconds. I can't
let it go for a long time since it's a production site but I think it
would hang there forever.
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.
Wouldn't it make sense for the scheduler to stop starting up new proc
runs once it knows the server is shutting down? It's not like these
are long running things; they are starting up very frequently because
they only run for a few seconds and then finish. So it wouldn't be a
big issue if the ones that were running when the server was shut down
were allowed to finish; the problem is that the scheduler is keeping
on going, running more of them, seemingly forever.
thanks,
janine
--
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.
