Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Processes failing

Discussion in 'General Discussion' started by sirbrent, Aug 12, 2009.

  1. sirbrent

    sirbrent Well-Known Member

    Sep 30, 2008
    Likes Received:
    Trophy Points:
    Over the last week i have received emailed alerts from one of my server informing me that services have failed. I have reviewed the logs but find nothing to help me understand why.

    An example would be when i was alerted httpd failed:

    httpd failed @ Fri Aug  7 16:50:23 2009. A restart was attempted automagically.
    Service Check Method:  [tcp connect]
    Failure Reason: Unable to connect to port 80
    and the apache error log only had this to say:
    [Fri Aug 07 16:50:38 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Fri Aug 07 16:50:38 2009] [notice] ModSecurity for Apache/2.5.5 ( configured.
    [Fri Aug 07 16:50:39 2009] [notice] mod_python: Creating 8 session mutexes based on 256 max processes and 0 max threads.
    [Fri Aug 07 16:50:39 2009] [notice] mod_python: using mutex_directory /tmp 
    [Fri Aug 07 16:50:39 2009] [notice] Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.7a DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/ SVN/1.5.1 mod_python/3.3.1 Python/2.4.3 configured -- resuming normal operations
    The second example is that mysqld failed, the message:

    mysql failed @ Wed Aug 12 07:42:35 2009. A restart was attempted automagically.
    Service Check Method:  [check command]
    Cmd Service Check Raw Output: mysql has failed
    i checked my mysql error log and it had this to say, which doesnt indicate anything to me:

    090812  7:39:41 [Note] /usr/sbin/mysqld: Normal shutdown
    090812  7:39:43  InnoDB: Starting shutdown...
    090812  7:39:45  InnoDB: Shutdown completed; log sequence number 0 77439216
    090812  7:39:45 [Note] /usr/sbin/mysqld: Shutdown complete
    090812 07:39:45  mysqld ended
    090812 07:42:37  mysqld started
    090812  7:42:37  InnoDB: Started; log sequence number 0 77439216
    090812  7:42:37 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.0.51a-community'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition (GPL)
    What can I do to understand these process failures?
  2. netlook

    netlook Well-Known Member

    Mar 25, 2004
    Likes Received:
    Trophy Points:
    Have you sorted this out? We are seeing such random failures on some of our servers, without any reason also.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice