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.

all sites down

Discussion in 'General Discussion' started by Secret Agent, Jun 17, 2005.

Thread Status:
Not open for further replies.
  1. Secret Agent

    Secret Agent Guest

    Server stats shows everything ok
    apache restarts ok
    mysql restarts ok
    rebooted server, sites still down
    IP's all pingable

    able to login to whm of course
    updated cpanel
    updated apache

    sites all still down

    removed/readded dns for nameservers
    restarted bind, same issue

    /scripts/fixndc (2x)
    /scripts/fixetchosts
    /scripts/fixnamed
    /scripts/fixbuggynamed
    /scripts/fixcommonproblems
     
  2. fwwebs

    fwwebs Well-Known Member

    Joined:
    Feb 16, 2004
    Messages:
    329
    Likes Received:
    0
    Trophy Points:
    16
    Post a domain and and IP.
     
  3. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    Is this on the server that you yum upgraded to centos 4?
     
  4. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    Try /scripts/rebuildhttpdconf and restart apache
     
  5. Secret Agent

    Secret Agent Guest

    That didn't work unfortunately.

    This has nothing to do with Centos 4 upgrade, another server

    As a matter of fact, I noticed on a few servers Centos upgraded by itself from 3.4 to 3.5

    Could this be it or just another cpanel bug?

    Maybe a bad upgrade?
     
  6. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    What do you see when you try to go to a site? The cPanel page or no page? Does it timeout? Error?
     
  7. Secret Agent

    Secret Agent Guest

    Page not found

    I got 3 reports from 3 dedicated server clients same issue, yet all pinging.

    Anyone replicating this?
     
  8. webignition

    webignition Well-Known Member

    Joined:
    Jan 22, 2005
    Messages:
    1,880
    Likes Received:
    0
    Trophy Points:
    36
    This is a tad vague, and could happen for a number of reasons.

    First, when you say they all ping, you are pinging the domain names and not IPs?

    Second, is mail for these domains working? Are you certain it is not DNS issue?

    Thirdly, try to telnet on port 80 to one of the affected domains and try and make a simple GET request and see what happens - timeout? error?
     
  9. Secret Agent

    Secret Agent Guest

    I am pinging the IP addresses not domain. I had datacenter look at it and they confirmed it is not network but local, coincidently 3 servers in one day.

    I have telnet disabled for security reasons
     
  10. Secret Agent

    Secret Agent Guest

    BIND is up and running.

    I can't imagine BIND breaking on 4 servers in one day coincidently unless its a new cpanel bug.
     
  11. webignition

    webignition Well-Known Member

    Joined:
    Jan 22, 2005
    Messages:
    1,880
    Likes Received:
    0
    Trophy Points:
    36
    Try to ping the affected domains. If this fails, try a to run a traceroute to one of the affected domains and see where it dies.

    You didn't answer the question about mail - for the affected domains whose websites aren't working, does mail work?
     
  12. Secret Agent

    Secret Agent Guest

    I don't know about mail, not sure what that would have to do with all sites being down.


    ping 147.202.65.178

    Pinging 147.202.65.178 with 32 bytes of data:

    Reply from 147.202.65.178: bytes=32 time=49ms TTL=50
    Reply from 147.202.65.178: bytes=32 time=48ms TTL=50
    Reply from 147.202.65.178: bytes=32 time=49ms TTL=50
    Reply from 147.202.65.178: bytes=32 time=49ms TTL=50

    Ping statistics for 147.202.65.178:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 49ms, Average = 48ms

    tracert calgarymarketplace.com
    Unable to resolve target system name calgarymarketplace.com.

    ping calgarymarketplace.com
    Ping request could not find host calgarymarketplace.com. Please check the name and try again.
     
  13. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    /scripts/rebuildnamedconf; service named restart

    the cahcing-nameserver package was probobly not on your yum skiplist and got installed which completely recreates your /etc/named.conf. Running the above command will put in the domains again and restart the service. Also, make sure rndc status doesn't give any errors. If it says it can't connect, /scripts/fixndc try again, and if it still can't connect, do it once more. After the second time it should be working.
     
  14. Secret Agent

    Secret Agent Guest

    I ran those many times, still no good

    number of zones: 13
    debug level: 0
    xfers running: 0
    xfers deferred: 0
    soa queries in progress: 0
    query logging is OFF
    server is up and running
     
  15. Secret Agent

    Secret Agent Guest

    /scripts/rebuildnamedconf

    /etc/rc.d/init.d/named restart


    Fixed.
    Another cPanel issue (4 servers all cpanel, same day).

    sigh but thank GOD resolved

    Blue, thanks!
     
  16. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    Ping the nameserver addresses (ns1/2.yourdomain.com) and see if those work. If not, make sure they're setup properly in named still, and then wait 24 hours. That's about all you can do.

    I assume that the caching-nameserver package was installed yesterday or before which caused the DNS to become stale now and now that you see the effects, the domains need some time to propogate now that you ran the proper script to fix it.
     
  17. cPanelNick

    cPanelNick Administrator
    Staff Member

    Joined:
    Mar 9, 2015
    Messages:
    3,426
    Likes Received:
    2
    Trophy Points:
    38
    cPanel Access Level:
    DataCenter Provider
    What build are you running?
     
  18. cPanelNick

    cPanelNick Administrator
    Staff Member

    Joined:
    Mar 9, 2015
    Messages:
    3,426
    Likes Received:
    2
    Trophy Points:
    38
    cPanel Access Level:
    DataCenter Provider
    Actually... it seems the problem may be OS related. Are you perhaps using CentOS 3.4 and updated to CentOS 3.5 last night ?
     
  19. nickn

    nickn Well-Known Member
    PartnerNOC

    Joined:
    Jun 15, 2003
    Messages:
    619
    Likes Received:
    1
    Trophy Points:
    18
    It's been verified as an RPM issue. Basically the mtime was changed in caching-nameserver RPM and that caused the RPM to save the /etc/named.conf as /etc/named.conf.rpmsave. Here's what happened:

    Code:
    # rpm -Uvh caching-nameserver-7.2-7.noarch.rpm  --nodeps
    warning: caching-nameserver-7.2-7.noarch.rpm: V3 DSA signature: NOKEY,
    key ID 025e513b
    Preparing...                
    
    ###########################################
    [100%]
       1:caching-nameserver     warning: user named does not exist - using
    root
    ########################################### [100%]
    [root@localhost RR]#
    [root@localhost RR]#
    [root@localhost RR]# pico /etc/named.conf
    
    
    # rpm -Uvh --nodeps caching-nameserver-7.3-3_EL3.noarch.rpm
    warning: caching-nameserver-7.3-3_EL3.noarch.rpm: V3 DSA signature:
    NOKEY, key ID 025e513b
    Preparing...                
    ###########################################
    [100%]
       1:caching-nameserver     warning: /etc/named.conf saved
    as /etc/named.conf.rpmsave
    ########################################### [100%]
    
    In short, to fix this you should simply be able to copy the /etc/named.conf.rpmsave file to /etc/named.conf.

    This wasn't due to cPanel but was due to the yum upgrade to 3.5 and a bad RPM build.
     
  20. Secret Agent

    Secret Agent Guest

    Thank you for clarify Nick.

    Also, I did not update Centos on 3 servres, it did it automaticlaly by itself
     
Loading...
Thread Status:
Not open for further replies.

Share This Page