I've got a 9.0RC2 box, as well as a couple other boxes (8.2, and a 7.1 updated) that, 
suddenly this morning, generated an error email, and apache stopped.  Here's some
example emails:

> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [  OK  ]
> Reloading httpd-perl: [  OK  ]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> Reloading httpd-perl: [FAILED]
> Reloading httpd: [FAILED]
> 

In looking through the syslog, I see:

Oct  1 04:01:00 gw CROND[22433]: (root) CMD (nice -n 19 run-parts /etc/cron.hour
ly)
Oct  1 04:02:01 gw CROND[22444]: (root) CMD (nice -n 19 run-parts /etc/cron.dail
y)
Oct  1 04:02:42 gw AESctl: httpd -USR1 succeeded
Oct  1 04:02:42 gw AESctl: httpd -USR1 succeeded  
Oct  1 04:02:43 gw AESctl: httpd shutdown failed
Oct  1 04:02:55 gw last message repeated 29 times
Oct  1 04:03:21 gw :
Oct  1 04:03:21 gw : Security Warning: World Writable files found :
Oct  1 04:03:21 gw : - /lib/dev-state/log
Oct  1 04:03:21 gw : - /tmp/.font-unix
Oct  1 04:03:21 gw : - /tmp/.font-unix/fs-1
Oct  1 04:03:21 gw : - /var/apache-mm
Oct  1 04:03:21 gw : - /var/spool/postfix/private/bounce
Oct  1 04:03:21 gw : - /var/spool/postfix/private/bsmtp
Oct  1 04:03:21 gw : - /var/spool/postfix/private/cyrus
Oct  1 04:03:21 gw : - /var/spool/postfix/private/defer
Oct  1 04:03:21 gw : - /var/spool/postfix/private/error
Oct  1 04:03:21 gw : - /var/spool/postfix/private/ifmail
Oct  1 04:03:21 gw : - /var/spool/postfix/private/lmtp
Oct  1 04:03:21 gw : - /var/spool/postfix/private/local
Oct  1 04:03:21 gw : - /var/spool/postfix/private/rewrite
Oct  1 04:03:21 gw : - /var/spool/postfix/private/smtp
Oct  1 04:03:21 gw : - /var/spool/postfix/private/uucp
Oct  1 04:03:21 gw : - /var/spool/postfix/private/virtual
Oct  1 04:03:21 gw : - /var/spool/postfix/public/cleanup
Oct  1 04:03:21 gw : - /var/spool/postfix/public/flush     
Oct  1 04:03:21 gw : - /var/spool/postfix/public/qmgr
Oct  1 04:03:21 gw : - /var/spool/postfix/public/showq

...followed by the log of it sending me the email.  The only thing I found in the
 pache error logs was this in the ssl-error_log:

[Tue Oct  1 04:02:43 2002] [error] mod_ssl: Init: (test.nlenet.net:443) Ops, no R
SA or DSA server certificate found?!
[Tue Oct  1 04:02:43 2002] [error] mod_ssl: Init: (test.nlenet.net:443) You have
to perform a *full* server restart when you added or removed a certificate and/o
r key file                    

I was able to restart the server with no problems using apachectl stop, then apachectl 
start.

What gives?  I don't have a registered ssl cert for this machine, but one was 
generated upon installation and running of apache.  This particular machine doesn't 
need it,
so I've commented out the ssl stuff now, but is this ssl thing what took the webserver 
down during the cron job?

Another machine that went down this morning had this in the error_log of apache:

[Tue Oct  1 05:12:29 2002] [notice] Apache-AdvancedExtranetServer/1.3.22 (Linux-
Mandrake/1.4mdk) mod_mp3/0.35 mod_ssl/2.8.5 OpenSSL/0.9.5a PHP/4.0.6 configured
-- resuming normal operations
[Tue Oct  1 05:12:29 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Oct  1 05:12:29 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Tue Oct  1 05:12:29 2002] [warn] long lost child came home! (pid 19026)
[Tue Oct  1 05:12:30 2002] [notice] SIGUSR1 received.  Doing graceful restart
[Tue Oct  1 05:12:31 2002] [notice] Apache-AdvancedExtranetServer/1.3.22 (Linux-
Mandrake/1.4mdk) mod_mp3/0.35 mod_ssl/2.8.5 OpenSSL/0.9.5a PHP/4.0.6 configured
-- resuming normal operations
[Tue Oct  1 05:12:31 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Oct  1 05:12:31 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Tue Oct  1 05:12:31 2002] [notice] SIGUSR1 received.  Doing graceful restart
[Tue Oct  1 05:12:31 2002] [notice] Apache-AdvancedExtranetServer/1.3.22 (Linux-
Mandrake/1.4mdk) mod_mp3/0.35 mod_ssl/2.8.5 OpenSSL/0.9.5a PHP/4.0.6 configured
-- resuming normal operations
[Tue Oct  1 05:12:31 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Oct  1 05:12:31 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Tue Oct  1 05:12:31 2002] [warn] long lost child came home! (pid 19190)
[Tue Oct  1 05:12:31 2002] [warn] long lost child came home! (pid 19056)
[Tue Oct  1 05:12:32 2002] [notice] SIGUSR1 received.  Doing graceful restart

This was repeated several times.  (Yes, I know, this version needs to be updated... 
working on it!)

Bob

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to