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.

Service Status hangs

Discussion in 'General Discussion' started by paulkoan, Jul 14, 2010.

  1. paulkoan

    paulkoan Well-Known Member

    Joined:
    Nov 24, 2006
    Messages:
    80
    Likes Received:
    0
    Trophy Points:
    6
    Hello,

    On one of our servers, the /scripts/servup page (Service Status) hangs. The banner appears, but that is all. In FF it stays in "Transferring Data" indefinitely, and in IE it immediately stops loading.

    In the access_log for whm, I can see:

    Code:
    x.x.x.x - root [07/14/2010:23:55:46 -0000] "GET /cPanel_magic_revision_1261096955/combined_optimized.css HTTP/1.1" 304 0 "https://server.com:2087/scripts/servup" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729; .NET4.0C)"
    x.x.x.x - root [07/14/2010:23:55:46 -0000] "GET /cPanel_magic_revision_1261096946/themes/x/style_optimized.css HTTP/1.1" 304 0 "https://server.com:2087/scripts/servup" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729; .NET4.0C)"
    x.x.x.x - root [07/14/2010:23:55:53 -0000] "GET /json-api/loadavg HTTP/1.1" 200 0 "https://server.com:2087/scripts/command" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)"
    x.x.x.x - root [07/14/2010:23:56:14 -0000] "GET /json-api/loadavg HTTP/1.1" 200 0 "https://server.com:2087/scripts/command" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)"
    x.x.x.x - root [07/14/2010:23:56:36 -0000] "GET /json-api/loadavg HTTP/1.1" 200 0 "https://server.com:2087/scripts/command" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)"
    
    This suggests that the loadavg script isn't working, however I get an immediate reply if I load that script "server.com:2087/json-api/loadavg" :

    Code:
    {"one":"1.33","five":"0.95","fifteen":"0.79"}
    
    So I guess it is whatever happens next. Any ideas how I can troubleshoot this? I have tried restarting the cpanel service.

    Thanks,

    Paul
     
  2. Miraenda

    Miraenda Well-Known Member

    Joined:
    Jul 28, 2004
    Messages:
    242
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Coralville, Iowa USA
    Although it's going to provide a lot of output that might be difficult to review to determine what's going on, the best option will be strace in this instance. In root SSH, run the following command to get an strace on the cpsrvd process:

    Code:
    strace -fvv -s 4096 -o ~/cpsrvd.strace -p `cat /var/run/cpsrvd.pid`
    Please log out of WHM first, then start the strace, then log back into WHM and go to Service Status area. After it hangs for a few moments, then stop the strace process with ctrl+c in shell. You may need to restart cPanel after you have done so:

    Code:
    /etc/init.d/cpanel restart
    Please note the strace will only work on Linux systems. If your system is FreeBSD, you'd need to use ktrace or truss with different flags.

    After you have the strace completed, you can then review it at ~/cpsrvd.strace file. There will be a lot of content. Normally, I open the file in vi at the end and go up line by line to see what it shows:

    Code:
    vi + ~/cpsrvd.strace
    Other people usually grep the file for write and errors instead. There's a tutorial on using strace at this location, which was a presentation at the cPanel 2009 Conference.

    If you aren't able to track down the cause, I'd suggest opening a ticket with cPanel at that point in WHM > Support Center > Contact cPanel area.

    Edit: Actually, I just realized you also hadn't indicated any error log checking. Before you do the strace, check the error_log also at /usr/local/cpanel/logs/error_log when visiting that page in WHM:

    Code:
    tail -f /usr/local/cpanel/logs/error_log
    By tailing it when you visit the page in WHM, you'll see any errors being produced. If there aren't any errors showing up there, then strace will be the best option. If there are errors, please let us know what errors here (even if you are able to figure it out from the errors on how to fix it).
     
    #2 Miraenda, Jul 15, 2010
    Last edited: Jul 15, 2010
Loading...

Share This Page