Check logrotate which is probably doing a 'kill -SIGHUP'. Look in the Apache error log prior to the rotate for a message like this: [Sun Apr 14 03:19:55.472903 2013] [mpm_event:notice] [pid 22674:tid 140605074487040] AH00494: SIGHUP received. Attempting to restart Then the first error log entry after the restart should be similar to: [Sun Apr 14 03:19:55.620047 2013] [mpm_event:notice] [pid 22674:tid 140605074487040] AH00489: Apache/2.4.3 (Unix) OpenSSL/1.0.0-fips mod_fcgid/2.3.7 configured -- resuming normal operations If there is a problem starting, Apache probably encounters it during this process. Regards, John ======================================== On Sunday 14 April 2013 11:35:55 Eric Covener wrote: > On Sun, Apr 14, 2013 at 11:33 AM, Karol Pomaski <karol.pomaski@xxxxxxxxx> wrote: > > Or maybe it reloads the config? > > Something strange is happening maybe this is a bug in Apache package > > from Debian? > > The server isn't reloading itself. Check crontab. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx