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.

URGENT problem with easyapache script

Discussion in 'EasyApache' started by hariskhan, Oct 8, 2006.

  1. hariskhan

    hariskhan Well-Known Member

    Joined:
    Apr 15, 2004
    Messages:
    146
    Likes Received:
    0
    Trophy Points:
    16
    Hello folks;

    I am receiving an error while running /scripts/easyapache. This didn't happen before.

    It started today when I ran it (/scripts/easyapache) and .. in a hurry pressed Ctrl+C at least 5-6 times to make it stop. I stopped it as soon as it started and gave me the following output;

    # /scripts/easyapache
    Fetching http://layer1.cpanel.net/buildapache.sea
    ......connected......receiving...fetching url http://layer1.cpanel.net/buildapache.sea


    Since then whenever I run /scripts/easyapache I get the following error messages;

    ;=======================================================

    # /scripts/easyapache
    Fetching http://layer1.cpanel.net/buildapache.sea (0)....@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx...@xx.xx.xx.xx......connected......receiving...Error 404 while fetching url http://layer1.cpanel.net/buildapache.sea
    ...failover......skipping xx.xx.xx.xx......Done
    buildapache.sea: Can't open buildapache.sea: No such file or directory
    initfpsuexec: using apache 1.x support
    Waiting for httpd to restart..............finished.

    root 15079 13.8 1.1 18568 11128 ?? Ss 12:26AM 0:01.31 /usr/local/apache/bin/httpd -DSSL

    httpd started ok

    ;=======================================================

    Now the /scripts/easyapache script won't run on production this server. I tried using;

    /scripts/upcp --force
    /scripts/easyapache
    /scripts/fixeverything

    but in vain. All of the above are either broken or don't fix anything.

    This is URGENT. How can I fix it?
     
  2. hariskhan

    hariskhan Well-Known Member

    Joined:
    Apr 15, 2004
    Messages:
    146
    Likes Received:
    0
    Trophy Points:
    16
    Small thing, big affect

    Its working now. Came out to be a dns problem;

    I had disabled recursion, which was causing it not to connect to the IP address to do the update.
     
Loading...

Share This Page