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.

WHM/Cpanel stopped loading

Discussion in 'General Discussion' started by NDP, Jun 30, 2006.

  1. NDP

    NDP Member

    Joined:
    Aug 4, 2004
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Hey

    I had a named problem. After searching the web i found it might be better to do a CPanel update through SSH. I tried this and i think after this my CPanel and WHM stopped loading. Whenever i access any of the ports 2082 or 2086 or through https it brings a page like this:

    I have tried to stop and restart CPanel and even tried another CPanel update through SSH. I have tried a reboot.

    Does anyone have any idea why this could have happened?

    Thanks in Advance!
     
  2. innovative2001

    innovative2001 Active Member

    Joined:
    Jun 5, 2006
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Hello,

    Please try to restart httpd and named service and then try again to open cpanel and whm.

    If the problem still persists then please provide me the exact URL which you are using.
     
  3. NDP

    NDP Member

    Joined:
    Aug 4, 2004
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    This did not work.

    The URL is http://66.90.103.31:2086

    Summary of what happens:

    Restarting Named


    Restarting httpd

     
  4. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Make sure you kill off any named processes completely:

    killall -9 named

    Then do:

    service named start

    Then check /var/log/messages for any named errors.
     
  5. NDP

    NDP Member

    Joined:
    Aug 4, 2004
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Result of Killing all named processes:

    Result of restarting named:

    What is the easiest way to read my logs?
     
  6. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Open two SSH windows.

    In the first one do this:

    tail -f /var/log/messages

    In the second window:

    service named restart

    You should see a slew of messages in the first window.

    Most commonly, the following script will cure many problems with bind:

    /scripts/fixndc

    If there're still problems, post the errors.
     
  7. NDP

    NDP Member

    Joined:
    Aug 4, 2004
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    :eek: Still no progress.

    Results of tail -f /var/log/messages

    Results of /scripts/fixndc

    Please advise
     
  8. Manuel_accu

    Manuel_accu Well-Known Member

    Joined:
    Jun 19, 2005
    Messages:
    191
    Likes Received:
    0
    Trophy Points:
    16
    Hi,

    This indicates that either named is already running or some other application are running in ths same port. Or your host's networ interface is unable to listen named.

    get the result of:

    # nmap -p 53 localhost

    if this port is open then cehck who is listing on this port:

    # netstat -plan | grep ":53"

    check for the named process

    # ps -ax | grep named

    get the process ID and check,

    lsof -p <PID>


    kill related process and kill named

    now check the status of rndc

    #rndc status

    run the script

    #/scripts/fixnamed

    Have a try...
     
Loading...

Share This Page