Results 1 to 15 of 15
  1. #1
    Join Date
    Feb 2004
    Location
    Ashdod, Israel
    Posts
    49

    httpd has failed, please contact the sysadmin.

    The apache is not working
    I get the error
    "httpd has failed, please contact the sysadmin. "
    Restart is not helping
    i resrated the apche service and the all server, but it didn't fix that

    please help me to fix that as soon as posible

    Thank you,
    Misha

  2. #2
    Join Date
    Apr 2003
    Location
    London, UK
    Posts
    4,721
    run:
    tail -f /usr/local/apache/logs/error_log (i think i'm right here)

    and restart apache, you might get some idea what the error is
    Hyperconfused (™)

  3. #3

    Wink

    Hi Misha

    Check the config test for httpd.conf by service httpd configtest and see what are the results. Also check and Disable Suexec and try to restart. I am sure this works for you.

    Thanks
    Arnold Mathews
    Senior Linux Engineer
    SupportSupply.com Outsourcing
    http://www.SupportSupply.com

  4. #4
    Join Date
    Feb 2004
    Location
    Ashdod, Israel
    Posts
    49
    Warning: DocumentRoot [/home/user1/public_html/user1] does not exist
    Warning: DocumentRoot [/home/user1/public_html/user2] does not exist
    Warning: DocumentRoot [/home/user1/public_html/user3] does not exist
    Warning: DocumentRoot [/home/user2/public_html/user4] does not exist
    Warning: DocumentRoot [/home/user3/public_html/user5] does not exist
    Warning: DocumentRoot [/home/user4/public_html/user6] does not exist
    Warning: DocumentRoot [/home/user1/public_html/mail] does not exist
    Warning: DocumentRoot [/dev/null] does not exist
    Warning: DocumentRoot [/home/user1/public_html/user7] does not exist
    Warning: DocumentRoot [/home/user1/public_html/user8] does not exist
    [Sun Apr 4 22:05:46 2004] [warn] NameVirtualHost 1.1.1.1:80 has no Virtua
    lHosts
    Syntax OK

  5. #5
    Hi Misha


    Ok you need to disable suexec from WHM and restart apache , I hope that works.

    Thanks
    Arnold Mathews
    Senior Linux Engineer
    SupportSupply.com Outsourcing
    http://www.SupportSupply.com

  6. #6
    Join Date
    Feb 2004
    Location
    Ashdod, Israel
    Posts
    49
    Originally posted by supportsup
    Hi Misha

    Check the config test for httpd.conf by service httpd configtest and see what are the results. Also check and Disable Suexec and try to restart. I am sure this works for you.

    Thanks
    I just go to WHM to disable the suexec, and then everiting is stoped to working
    i didn't toch anything,
    and still don't disable suexec

    i cank acsess the server from https://ip:2087
    and can't acsess by SSH

    Please help

  7. #7
    Hi Misha


    Well if you are not able to access the server with shell , You mau have to reboot the server.

    Thanks
    Arnold Mathews
    Senior Linux Engineer
    SupportSupply.com Outsourcing
    http://www.SupportSupply.com

  8. #8
    Join Date
    Feb 2004
    Location
    Ashdod, Israel
    Posts
    49
    Originally posted by supportsup
    Hi Misha


    Well if you are not able to access the server with shell , You mau have to reboot the server.

    Thanks
    Thank you very much,
    I will contact my host for more support.
    Misha B.
    Benis Computers and Communication
    Israel

  9. #9
    Join Date
    Feb 2004
    Location
    Ashdod, Israel
    Posts
    49
    Now i have this problem again.

    disabling susexc and retarting apache is not helping
    Misha B.
    Benis Computers and Communication
    Israel

  10. #10
    Join Date
    Aug 2004
    Posts
    142
    i u care pls contact me on AIM mayeb we can work it out

  11. #11
    Join Date
    Mar 2003
    Location
    California USA
    Posts
    13,681
    Did you recently recompile apache using easyapache? If so are you using mmcache? If so remove it and restart apache.
    Steven Ciaburri | Industry's Best Server Management - Rack911.com
    Software Auditing - 400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com
    Fully Managed Dedicated Servers (Las Vegas, New York City, & Amsterdam) (AS62710)
    FreeBSD & Linux Server Management, Security Auditing, Server Optimization, PCI Compliance

  12. #12
    Join Date
    Feb 2004
    Location
    Ashdod, Israel
    Posts
    49
    Originally posted by thelinuxguy
    Did you recently recompile apache using easyapache? If so are you using mmcache? If so remove it and restart apache.
    no.
    don't know what is " mmcache" and didn't find that in the apache upgrade option ( from WHM )
    Misha B.
    Benis Computers and Communication
    Israel

  13. #13
    Join Date
    Apr 2004
    Location
    Australia
    Posts
    419
    Correct me if im wrong guys

    NameVirtualHost 1.1.1.1:80 has no VirtualHosts
    Why would there be an ip like that in your httpd.conf? (unless you blanked it out)

    Have you deleted any accounts from the /home/ dir? if not, look in your httpd.conf and search it for user1, user2, user3, user4. Have a check that everything is correct including the documentroot.

    Just having a bit of a guess

  14. #14
    Join Date
    Apr 2003
    Posts
    959
    Originally posted by Matt -Seeksadmin
    Correct me if im wrong guys



    Why would there be an ip like that in your httpd.conf? (unless you blanked it out)

    Have you deleted any accounts from the /home/ dir? if not, look in your httpd.conf and search it for user1, user2, user3, user4. Have a check that everything is correct including the documentroot.

    Just having a bit of a guess
    I agree with you, I seen those problems before and what I did is try it out!

    1) make a copy of the httpd.conf
    2) delete those lines~
    3) try restart...
    4) if works then go to those directory and see if they exists
    5) if they don't you are happy chappy

    done

  15. #15
    Join Date
    Mar 2004
    Posts
    1,016
    Looks like you've removed the httpd from /usr/local/apache/bin , I suggest you to recompile apache in WHM.

    Had this problem sometime back, recompiling in WHM worked for me.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •