Results 1 to 5 of 5
  1. #1

    Apache reload kills apache

    Since last week, every time I reload apache with /etc/init.d/apache reload the server dies:

    [notice] SIGUSR1 received. Doing graceful restart accept_mutex_on: Identifier removed
    [notice] Apache/1.3.33 (Debian GNU/Linux) mod_ssl/2.8.22 OpenSSL/0.9.7d mod_gzip/ PHP/4.3.10-12 configured -- resuming normal operations
    [notice] Accept mutex: sysvsem (Default: sysvsem)
    [alert] Child 20340 returned a Fatal error... \nApache is exiting!

    To start it again I must do a "killall -9 apache" and "/etc/init.d/apache start". Any ideas of what is going on?


  2. #2
    Join Date
    Nov 2004
    What control panel you are using?
    AssistanZ - Beyond Boundaries...
    Cloudstack Consultancy / 24x7 Web Hosting Support / 24x7 Server Management / Infrastructure Management Services
    Web & Mobile Apps Development / Web Designing Services / Php, Grails, Java Development

  3. #3
    Join Date
    Oct 2003
    Long Island, New York
    What does it say in your apache error log about it? - Business Web Hosting Solutions & Server Management Since 2003

  4. #4
    Join Date
    Mar 2005
    u could try calling the apachectl or httpd directly to see whats the error its showing .
    /usr/sbin/apachectl stop/start or call /usr/sbin/httpd
    That'll give you a more detailed error message

  5. #5
    I'm using Debian Sarge without control panel, and the error log is in my first post:

    [alert] Child 20340 returned a Fatal error... \nApache is exiting!

    That's all.

    I've changed the init script to send a HUP signal instead of USR1, and it seems to work now. But I don't know if this is the correct way to do it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts