The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Apache status - Log Processes are not dying

Discussion in 'General Discussion' started by lordadel, Dec 4, 2015.

  1. lordadel

    lordadel Member

    Joined:
    Jul 2, 2014
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hello all,

    Yesterday, I noticed that the I've hit the Max_Clients count on the server, So I restarted the apache and all went fine.

    Today, I was checking again, and I noticed that Log processes are not dying (Under SS column the numbers are like 12442 ..).

    With my very little linux knowledge and some googling. I tried to debug this issue but hit a dead end and I hope that someone can give me a hint or help me with this issue.

    I took one of the Log processes with PID = 35343

    I run
    And the result is:
    I guess that it's waiting for process with PID: 2837

    I also confirmed with running pgrep to find child processes for the main process (35343)
    The result was:
    So I started tracing the process with PID 2837

    And the result was:
    Obviously, it's trying to access a resource or something and it's timing out everytime. I tried to check the file descriptors for the PID 2837
    And the result is:


    And I got stuck here and don't know what to do next. and I hope that someone could give me a help with this issue.
     
  2. lordadel

    lordadel Member

    Joined:
    Jul 2, 2014
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    I have also noticed that "Gracefully finishing" processes have the same symptoms and they are not dying :/
     
  3. lordadel

    lordadel Member

    Joined:
    Jul 2, 2014
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    I have found the cause of the issue in case anyone have the same problem. It was a line in a PHP script that is using curl and failing while trying to resolve domain names.

    I commented out this line and the problem seems to be gone.
    Code:
    curl_setopt($ch, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4 );
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,723
    Likes Received:
    660
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page