NOT SUPPORTED appears in apache config after SSL problems

Discussion in 'Installation/Configuration' started by jmroth, Mar 9, 2006.

  1. jmroth

    jmroth ISPConfig Developer

    Hi there,
    yesterday I wanted to install a new SSL certificate for a site.
    I made a mistake and the private key was not at the right location when I told ISPConfig to "Save". So, Apache did not start up, and ISPConfig marked _all_ optional Apache directives for all sites that I had defined with the tag "NOT SUPPORTED" although it had nothing to do with them.
    Do you have any idea what could have caused this?
    Regards,
    ~jm
     
  2. falko

    falko Super Moderator

    This means that the syntax check
    Code:
    httpd -t
    returned an error, therefore ISPConfig commented out the Apache Directives.
    Anything in the Apache error log?
     
  3. jmroth

    jmroth ISPConfig Developer

    Well, on my box httpd -t always returns the following, however all is working fine and I have not time to troubleshoot it:

    Code:
    [Tue Mar 14 11:48:07 2006] [warn] The ScriptAlias directive in /etc/apache2/vhosts/Vhosts_ispconfig.conf at line 125 will probably never match because it overlaps an earlier AliasMatch.
    [Tue Mar 14 11:48:07 2006] [warn] The Alias directive in /etc/apache2/vhosts/Vhosts_ispconfig.conf at line 153 will probably never match because it overlaps an earlier AliasMatch.
    Syntax OK
    (I understand the error, but as long as all works ok, I will not really touch it)

    Now, what I meant was, how can the missing private key result in all directives being commented out!? (Maybe ISPConfig is confused by the above warnings, although it wouldn't make sense.)
    When the private key was missing, apache just didn't do anything upon a start command via init.d, it didn't even report to the error.log that it couldn't start.

    Regards,
    ~jm
     
  4. falko

    falko Super Moderator

    ISPConfig just reads the return value of
    Code:
    httpd -t
    , and even with your warnings from above this is 0 which is ok (as long as "Syntax OK" appears it is ok).


    When the key was missing,
    Code:
    httpd -t
    must have given back an error which is normal if the Apache configuration file references a file which isn't existing.
     
  5. jmroth

    jmroth ISPConfig Developer

    Actually there were multiple lines in the ispconfig.log that read

    Code:
    08.03.2006 - 22:52:21 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 1814: WARNING: could not httpd -t &> /dev/null
    and then this
    Code:
    08.03.2006 - 22:52:22 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 2333: httpd -t  &> /dev/null
    08.03.2006 - 22:52:22 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 2335: httpd syntax ok
    :-\

    Also, the inverse seems to have happened at some time

    Code:
    08.03.2006 - 22:57:07 => INFO -= /root/ispconfig/scripts/lib/config.lib.php, Line 1814: httpd -t &> /dev/null
    08.03.2006 - 22:57:13 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 2333: WARNING: could not httpd -t  &> /dev/null
    08.03.2006 - 22:57:13 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 2339: httpd syntax seems to contain errors, restarting with old configuration
     

Share This Page