On 2003.06.05, Jim Wilcoxson <[EMAIL PROTECTED]> wrote: > We still have instances where AOLServer (3.2) "goes deaf" for some > reason. The nsd processes are there, but they aren't handling any > requests. So while I think this suggestion is a good idea, it > probably won't take the place of watchdog monitoring, at least not > for real production sites. "Are you running?" and "Are you answering > requests?" are not the same question...
Right. Since I use my shell script that automatically restarts nsd if the pidfile is still there, I have another script that runs out of cron every 5 minutes that does an HTTP GET to each running nsd and retrieves a page. If the request doesn't return 200 OK and some specific content, the script issuing the HTTP GET then goes and kills the nsd process. The watchdog shell script then goes and starts another nsd, since the nsd died but the pidfile still exists. (Hint: the page that is requested has some ns_db in there to make sure connections to the database server can be made ... which is the "specific content" I was referring to ... if the connection can't be made or a handle can't be gotten from all the pools, it triggers a restart.) -- 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: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
