ISPConfig not writing vhost changes to disk

Discussion in 'General' started by 99miles, Feb 17, 2012.

  1. falko

    falko Super Moderator ISPConfig Developer

    Sorry, I gave the wrong command. The correct command is

    Code:
    . /etc/apache2/envvars && apache2 -t
    (there's a space between the dot and /etc...)
     
  2. baskin

    baskin New Member

    It is very strange. Before i try anything i copy the .err file as .vhost file and i remove the working one

    Trying the above command with the .err file:

    Code:
    # . /etc/apache2/envvars && apache2 -t
    [Wed Jul 04 19:41:07 2012] [warn] NameVirtualHost 2a00:7b80:3019:12::d7f3:23b9:80 has no VirtualHosts
    [Wed Jul 04 19:41:07 2012] [warn] NameVirtualHost 2a00:7b80:3019:12::d7f3:23b9:443 has no VirtualHosts
    Syntax OK
    but when i try to start apache

    Code:
     /etc/init.d/apache2 restart
    Restarting web server: apache2[Wed Jul 04 19:40:46 2012] [warn] NameVirtualHost 2a00:7b80:3019:12::d7f3:23b9:80 has no VirtualHosts
    [Wed Jul 04 19:40:46 2012] [warn] NameVirtualHost 2a00:7b80:3019:12::d7f3:23b9:443 has no VirtualHosts
     ... waiting [Wed Jul 04 19:40:47 2012] [warn] NameVirtualHost 2a00:7b80:3019:12::d7f3:23b9:80 has no VirtualHosts
    [Wed Jul 04 19:40:47 2012] [warn] NameVirtualHost 2a00:7b80:3019:12::d7f3:23b9:443 has no VirtualHosts
    Action 'start' failed.
    The Apache error log may have more information.
     failed!
    Replacing the ".err" file with the "working" copy make apache to start successfully. Error log doesn't contain anything useful

    I'm on dead end...
     
    Last edited: Jul 4, 2012
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Thats a good result, as it helps us to find the reason for the problem. ISPConfig has created the .err file because it does not work and used the last working version and saved the .err file to allow debugging like you do it currently. Compare the content of the .err file with the working file and post the difference.

    A likely reason is that you enabled ssl and the sl cert on your server is invalid, as this causes apache to fail without logging any errors.
     

Share This Page