Caught Sigterm

T

Titam

Verified User
Joined
Apr 29, 2005
Messages
168
Hi,

If anybody know... i would like to understand why in the log, i have this :

[Fri May 13 19:51:01 2005] [notice] caught SIGTERM, shutting down
[Fri May 13 19:51:03 2005] [notice] Apache/1.3.33 (Unix) mod_ssl/2.8.22 OpenSSL/0.9.7a PHP/4.3.11 mod_perl/1.29 FrontPage/5.0.2.2510 configured -- resuming normal operations
[Fri May 13 19:51:03 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri May 13 19:51:03 2005] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Fri May 13 19:51:45 2005] [notice] caught SIGTERM, shutting down
[Fri May 13 19:53:42 2005] [notice] Apache/1.3.33 (Unix) mod_ssl/2.8.22 OpenSSL/0.9.7a PHP/4.3.11 mod_perl/1.29 FrontPage/5.0.2.2510 configured -- resuming normal operations
[Fri May 13 19:53:42 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri May 13 19:53:42 2005] [notice] Accept mutex: sysvsem (Default: sysvsem)
Click to expand...

That happens sometimes and i dont know why ...

Thanks
 
How often does it happen? It could be normal operations since apache must be restarted if any configuration changes are made.
 
I will let this 2 or 3 days to analyze logs and I will reply at this post.
 
Today i had a domains, create FTP & co, and i have this message again, it's normal so ?
 
Yes it sounds normal since it's only happening when you make modifications in DirectAdmin that would change the httpd.conf file or the nightly tally when rotating logs which require apache to reload.
 
jmstacey said:
Yes it sounds normal since it's only happening when you make modifications in DirectAdmin that would change the httpd.conf file or the nightly tally when rotating logs which require apache to reload.
Click to expand...

Ok, thanks a lot jmstacey :)
 
Hello,

Just as a followup, a restart is only required when the httpd.conf either has a new virtualhost. This is mainly because ssl certificate changes require a full restart vs just a reload (cert files have to be read in). Reloads are adequtate when making minor changes to a virtualhost or the main settings, but DA is almost always modifying more major things (ssl, new subdomains), thus the restarts are usually called for.

John
 
Thanks John, but i see that all days, at 00:11 am, that restarts (and i didn't changed anything and a priori i don't have cron :\)
 
Hello,

The nightly tally runs at 00:10am. Since it might be suspending accounts (changing virtualhosts) it does a full restart when the tally is done. (regardless if someone was or not). Also, the HUP is given right off the bat after the logs are rotated so that they get re-opened. DA will work on the rotated logs.

John
 
You must log in or register to reply here.
Back
Top