[SLE] Apache doesn;t restart

From: John (isofroni_at_cc.uoi.gr)
Date: 02/27/05

  • Next message: Adalberto Castelo: "[SLE] Realtek ALC850 - jack sensing problems" 
    To: "Suse" <suse-linux-e@suse.com>
Date: Sun, 27 Feb 2005 16:19:00 +0200

    Hello all

    I have recently installed apache 2.0.50 and its patches. (on Suse 9.2 Pro)

    The problem is that i cannot restart apache.

    If i make a configuration in a file (say /etc/apache2/vhosts.d/secure.conf)
    then it cannot "see" the changes i made to that file. However, if i make
    i "type" a mistake then apache warns me that the syntax is not ok.
    After that i run rcapache2 restart and the new configurations cannot be seen by apache.

    Do you know why this happening?

  • Next message: Adalberto Castelo: "[SLE] Realtek ALC850 - jack sensing problems"

    Relevant Pages

    • Re: the google keywords for debug...
      ... After I added the pint or warn message, I didn't restart Apache. ... I can not find this message in the project private logs. ... I receive a project in perl. ...
      (perl.beginners)
    • Re: Portupgrade breaks Apache13-modssl
      ... On Saturday 21 May 2005 10:39 am, Eric Sheesley wrote: ... I can get apache started with no ssl but not with it. ... Then restart apache. ... If there is no "obvious" conflict like the recode conflict, ...
      (freebsd-questions)
    • Re: rotatelogs is rotating too quickly...
      ... I had to change a bunch of apache config files to switch from normal log files to piping logs through rotatelogs. ... So the list above reflects how fast it took me to update a config file and restart apache, not anything that rotate logs was doing. ...
      (freebsd-questions)
    • Re: problems with installing wordpress 2.0
      ... > I have no idea why phpmyadmin would show differently than phpinfo. ... > In phpinfo output, take note of the php.ini path (should be at the top ... > if it's not already there, then restart apache. ...
      (Ubuntu)
    • FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to a
      ... This may be an Apache issue and if so I'll take my questions elsewhere ... restart apache I get this error: ... upgrading. ... errors in the .conf file. ...
      (linux.redhat)