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.

tweak settings changes emptied httpd.conf

Discussion in 'General Discussion' started by pavemen, Jun 26, 2008.

  1. pavemen

    pavemen Active Member

    Joined:
    Oct 8, 2003
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    1
    made a few minor changes to Tweak Settings a bit ago and all of a sudden Apache was dead. I tried to undo the changes (I could not remember all of them) and nothing changed, Apache was still dead.

    Trying to start it, I got the no listening sockets error. I looked at httpd.conf and it was empty except for the virtualhost entry for the hostname.

    I am not running anything custom in the Apache Include files.

    I copied yesterday's backup of the file and httpd restarted fine.

    Running:

    WHM 11.23.2 cPanel 11.23.3-S25959
    REDHAT Enterprise 5.2 i686 on standard - WHM X v3.1.0

    Is there a log of the WHM changes I make that I can go back and review what changed and where the error came from?

    So whatever I changed that rewrote the httpd.conf file(s) didn't work correctly.
     
  2. shopcentar

    shopcentar Well-Known Member
    PartnerNOC

    Joined:
    Jul 10, 2004
    Messages:
    55
    Likes Received:
    1
    Trophy Points:
    8
    Hi,

    same bug on our server.

    httpd.conf are not empty, sintax are ok but apache wont start.

    After restoring backup for httpd.conf file its ok.

    So cPanel Stuff, please chek this error with Tweak Settings because this option are apache KILLER.

    Regards, SC
     
    #2 shopcentar, Jul 2, 2008
    Last edited: Jul 2, 2008
  3. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Seeing as this is not a widespread issue, I recommend submitting a support ticket so our technical analysts can determine why this is happening: http://ticket.cPanel.net/submit
     
Loading...

Share This Page