> Rachel wrote: > > Hi, I having problem where my APACHE no longer run after the > everynight 12:01am.... > I have no idea what's the error message below.... can someone > teach/explain to me? > > [Thu Oct 11 00:00:01 2001] [notice] SIGHUP received. Attempting to > restart > What is SIGHUP received ? where can i configure it?
SIGHUP is a "hangup signal". For a running process like apache it has the effect of making the process reload its configuration file without breaking any existing connections. You often do this if you make a minor change to httpd.conf and want to implement the change immediately but you don't want to stop and start the server. You send a SIGHUP with the "kill" command. First, find out apache's parent process-id. This is stored in the file defined by the "PidFile" directive. If you don't have a "PidFile" directive, it will be in httpd.pid in the logs directory. So you can do: # cd <apache logs directory> # cat httpd.pid 27443 # kill -HUP 27443 and you will get the message above in the error_log and apache will reload httpd.conf. Alternatively, the "apachectl" program does this when invoked with the "graceful" argument. NB: Some changes are too extreme to be reloaded by a SIGHUP and need a full stop and start (e.g. changing CertificateFile directives). > What is the bottom error message that say "dynamic module limit was > reached"? how can i increase it? > > [Thu Oct 11 00:00:01 2001] [notice] SIGHUP received. Attempting to > restart > [Thu Oct 11 00:00:01 2001] [error] Cannot remove module mod_ssl.c: not > found in module list > .... > httpd: module "mod_proxy.c" could not be loaded, because the dynamic > module limit was reached. Please increase DYNAMIC_MODULE_LIMIT and > recompile. This is a funny one. The DYNAMIC_MODULE_LIMIT is defined in your apache distribution. Go to the directory in which unpacked apache and look in: src/include/httpd.h and you will find the lines: /* Max. number of dynamically loaded modules */ #ifndef DYNAMIC_MODULE_LIMIT #define DYNAMIC_MODULE_LIMIT 64 #endif So its default is 64 which ought to be enough for anyone. Check yours is not unusually small... However, I rather suspect that the problem is something else. Why is your apache restarting at 00.01 every night? The only way this will happen is if you have a cron job doing it. So do: (login as root) # crontab -l and look for something like "apachectl graceful". Did someone else set up or maintain your apache installation? In any case, even if it does restart each night, it shouldn't cause any problems. I don't use mod_so personally (all my modules are compiled in) so I don't know if a SIGHUP will reload modules or not. It could be that the original set of modules stays in and it trys to load a new set on top which increases the DYNAMIC_MODULE_LIMIT count. Usually, if you have problems with a SIGHUP, it is best to do a full stop and start (e.g. "apachectl restart"). Rgds, Owen Boyle. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
