SIGTERM?

I just installed iTools 6.0.2 (also the SSL) on an OS-X 10.0.4 box with
WebCatalog-4.0.2rc1a. It's a B&W G3-350 w/512MB.

Here's the "error_log" file after just a small amount of "uptime"...

[Tue Jul 17 15:35:44 2001] [notice] FastCGI: process manager initialized
(pid 466)
[Tue Jul 17 15:35:45 2001] [notice] Apache/1.3.19 (iTools/MacOSX)
mod_perl/1.25 mod_fastcgi/2.2.8 configured -- resuming normal operations
[Tue Jul 17 15:37:48 2001] [notice] caught SIGTERM, shutting down
[Tue Jul 17 15:38:00 2001] [notice] Apache/1.3.19 (iTools/MacOSX)
mod_ssl/2.8.1 OpenSSL/0.9.5a mod_perl/1.25 mod_fastcgi/2.2.8 configured --
resumin
g normal operations
[Tue Jul 17 15:38:00 2001] [notice] FastCGI: process manager initialized
(pid 538)
[Tue Jul 17 15:39:52 2001] [notice] caught SIGTERM, shutting down
[Tue Jul 17 15:41:33 2001] [notice] FastCGI: process manager initialized
(pid 261)
[Tue Jul 17 15:41:33 2001] [notice] Apache/1.3.19 (iTools/MacOSX)
mod_ssl/2.8.1 OpenSSL/0.9.5a mod_perl/1.25 mod_fastcgi/2.2.8 configured --
resumin
g normal operations
[Tue Jul 17 15:44:02 2001] [notice] caught SIGTERM, shutting down
[Tue Jul 17 15:44:16 2001] [notice] FastCGI: process manager initialized
(pid 310)
[Tue Jul 17 15:44:16 2001] [warn] FastCGI: server
"/Library/WebServer/CGI-Executables/WebCatalogEngine/WebCatalog" started
(pid 312)
[Tue Jul 17 15:44:16 2001] [notice] Apache/1.3.19 (iTools/MacOSX)
mod_ssl/2.8.1 OpenSSL/0.9.5a mod_perl/1.25 mod_fastcgi/2.2.8 configured --
resumin
g normal operations
[Tue Jul 17 15:44:34 2001] [notice] caught SIGTERM, shutting down

I seem to be catching SIGTERMs quite a bit.

Is there a problem with the SSL, or is it a FastCGI Problem? The machine
gave a "Connection Refused" page after about 25min, and I gave it a
"apachectl-ssl stop & start". That perked it back up. It's been up for about
an hour under moderate traffic now.

Any thoughts???

    -Doug

-- 
Douglas Hardman
doug@xxxxxxxxxxxxxxx
Silver Creek, Ltd.


---
Tenon Intersystems' itools Mailing List
To unsubscribe: send mailto://itools-request@xxxxxxxxxxxxxxx
with the body: unsubscribe