I have the following in my newsyslog.conf
/var/log/httpd-*.log 644 9 8 @T01 BG /var/run/httpd.pid 30
and am seeing crashes with apache-2.0.63_2 which I think are associated. I think this tells newsyslog to treat the file as binary and send signal 30 SIGUSR1.
The relevant error log entries appear to be these lines
[Thu Apr 02 01:00:00 2009] [notice] Graceful restart requested, doing restart [Thu Apr 02 01:00:00 2009] [emerg] (2)No such file or directory: Couldn't initialize cross-process lock in child [Thu Apr 02 01:00:00 2009] [emerg] (2)No such file or directory: Couldn't initialize cross-process lock in child [Thu Apr 02 01:00:00 2009] [notice] FastCGI: process manager initialized (pid 93707) [Thu Apr 02 01:00:01 2009] [warn] RSA server certificate CommonName (CN) `*.xxx.org' does NOT match server name!?[Thu Apr 02 01:00:01 2009] [warn] RSA server certificate CommonName (CN) `*.xxx.org' does NOT match server name!?
......
[Thu Apr 02 01:00:01 2009] [warn] RSA server certificate wildcard CommonName (CN) `*.xxx.org' does NOT match server name!? [Thu Apr 02 01:00:01 2009] [notice] Apache/2.0.63 (FreeBSD) mod_fastcgi/2.4.6 mod_ssl/2.0.63 OpenSSL/0.9.8e configured -- resuming normal operations [Thu Apr 02 01:00:01 2009] [alert] Child 93701 returned a Fatal error... Apache is exiting! [Thu Apr 02 01:00:01 2009] [alert] FastCGI: read() from pipe failed (0)[Thu Apr 02 01:00:01 2009] [alert] FastCGI: the PM is shutting down, Apache seems to have disappeared - bye
I have used this rotation scheme with FreeBSD 6.0/6.1/6.2 for some years and it has never failed till the last few days when I'm now running 7.0-RELEASE. Can anyone advise what could be done to ameliorate this.
I see mention of rotatelogs and using apache's pipe log feature, is that a better solution to this problem?
-- Robin Becker --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|