This is the first time in years; and I wonder what might be wrong. I
am running OpenBSD 4.4, nothing specific. I have rotated the logs
daily through these years, with the script as below, and no problem
until today. The machine has an uptime of 50 days.
Still after the cron-ed logrotation this morning it didn't come up
with 'graceful'.
This is what I have gathered until now from the error-log:

[Wed Mar 18 04:21:06 2009] [error] [client 77.37.220.140] File does
not exist: /htdocs/v2/intl/zh-CN/
[Wed Mar 18 04:21:06 2009] [error] [client 77.37.220.140] File does
not exist: /htdocs/v2/error_404.html
[Wed Mar 18 04:21:10 2009] [error] PHP Notice:  Undefined index:
HTTP_HOST in /htdocs/v2/libraries/joomla/environment/uri.php on line
154
[Wed Mar 18 04:21:10 2009] [error] PHP Notice:  Undefined index:
HTTP_USER_AGENT in /htdocs/v2/libraries/joomla/html/html/behavior.php
on line 51
[Wed Mar 18 04:21:10 2009] [error] PHP Notice:  Undefined index:
HTTP_USER_AGENT in /htdocs/v2/templates/ja_purity/ja_templatetools.php
on line 200
[Wed Mar 18 04:21:10 2009] [error] PHP Notice:  Undefined index:
HTTP_USER_AGENT in /htdocs/v2/templates/ja_purity/ja_templatetools.php
on line 249
[Wed Mar 18 04:22:44 2009] [warn] child process 23069 still did not
exit, sending a SIGTERM
[Wed Mar 18 04:22:44 2009] [warn] child process 11890 still did not
exit, sending a SIGTERM
[Wed Mar 18 04:22:44 2009] [warn] child process 9049 still did not
exit, sending a SIGTERM
[Wed Mar 18 04:22:44 2009] [warn] child process 17620 still did not
exit, sending a SIGTERM
[Wed Mar 18 04:22:44 2009] [warn] child process 6571 still did not
exit, sending a SIGTERM
[Wed Mar 18 04:22:52 2009] [notice] caught SIGTERM, shutting down
PHP Warning:  Module 'mysql' already loaded in Unknown on line 0
PHP Warning:  Module 'mysql' already loaded in Unknown on line 0
[Wed Mar 18 18:05:43 2009] [notice] Initializing etag from
/var/www/logs/etag-state

apachectl stop
newsyslog -f /var/www/conf/newhttpdlog.conf
apachectl graceful
are the commands in the crontab.
When I run the command now, it works. It looks like a glitch. Still,
it ought not happen.

Please, inform me if more is required.

Uwe

Reply via email to