Hi all!
Just done an online update.
For some unknown reason, after doing an online update, the Apache2 update overwrites my /etc/sysconfig/apache2 configuration file.
Apache2 then refuses to start with the following error message:
Starting httpd2 (prefork) Syntax error on line 24 of /etc/apache2/sysconfig.d/global.conf: CustomLog takes two or three arguments, a file name, a custom log format string or format name, and an optional "env=" clause (see docs)
The command line was: /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf failed Failed services in runlevel 3: apache2
To correct the problem, I have to overwrite the apache2 config file the update has kindly installed for me, with a backup copy, and then start Apache manually.
This is odd behaviour. Should a security update be allowed to overwite config files that have been manually altered by the sys admin?
Has anyone else noticed this behaviour?
This is what I have defined for Apache2 logs:
APACHE_ACCESS_LOG="/var/log/apache2/access_log common, /var/log/apache2/browser_log agent, /var/log/apache2/referer_log referer, /var/log/apache2/combined_access_log combined, /var/log/apache2/ROBOT_LOG agent"
Kind Regards - Keith Roberts
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2005-09-13 at 22:52 +0100, suse@karsites.net wrote:
This is odd behaviour. Should a security update be allowed to overwite config files that have been manually altered by the sys admin?
Has anyone else noticed this behaviour?
I can tell you that the last update did indeed overwrite or change the configuration file, by looking at the modification date. I can not find any /etc/sysconfig/apache2.rpmsave, as I understand it should if it replaces a configuration file.
The culprit seems to be the POSTIN or ALL scripts in apache2-2.0.53-9.5.i586.patch.rpm:
if test -s etc/sysconfig/apache2 && grep -q "^LOADMODULES" etc/sysconfig/apache2; then sed "s/LOADMODULES/APACHE_MODULES/" etc/sysconfig/apache2 >| $tmpfile \ && cp $tmpfile etc/sysconfig/apache2 fi
- -- Cheers, Carlos Robinson
On Tue, Sep 13, 2005 at 10:52:01PM +0100, suse@karsites.net wrote:
The command line was: /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf failed Failed services in runlevel 3: apache2
To correct the problem, I have to overwrite the apache2 config file the update has kindly installed for me, with a backup copy, and then start Apache manually.
This is odd behaviour. Should a security update be allowed to overwite config files that have been manually altered by the sys admin?
Has anyone else noticed this behaviour?
This is what I have defined for Apache2 logs:
APACHE_ACCESS_LOG="/var/log/apache2/access_log common, /var/log/apache2/browser_log agent, /var/log/apache2/referer_log referer, /var/log/apache2/combined_access_log combined, /var/log/apache2/ROBOT_LOG agent"
That is invalid syntax for a file which is sourced by a shell script (which is what happens).
Put everything in one line, or use backslashes to escape the newlines characters.
(Assuming that the pasted snippet is verbatim)
Regards, Peter
On Fri, Oct 21, 2005 at 01:06:24PM +0200, Peter Poeml wrote:
On Tue, Sep 13, 2005 at 10:52:01PM +0100, suse@karsites.net wrote:
APACHE_ACCESS_LOG="/var/log/apache2/access_log common, /var/log/apache2/browser_log agent, /var/log/apache2/referer_log referer, /var/log/apache2/combined_access_log combined, /var/log/apache2/ROBOT_LOG agent"
That is invalid syntax for a file which is sourced by a shell script
No, this is correct for bash. It might be invalid for other tools but for bash this is legal.
Robert
On Fri, Oct 21, 2005 at 01:38:06PM +0200, Robert Schiele wrote:
On Fri, Oct 21, 2005 at 01:06:24PM +0200, Peter Poeml wrote:
On Tue, Sep 13, 2005 at 10:52:01PM +0100, suse@karsites.net wrote:
APACHE_ACCESS_LOG="/var/log/apache2/access_log common, /var/log/apache2/browser_log agent, /var/log/apache2/referer_log referer, /var/log/apache2/combined_access_log combined, /var/log/apache2/ROBOT_LOG agent"
That is invalid syntax for a file which is sourced by a shell script
No, this is correct for bash. It might be invalid for other tools but for bash this is legal.
Hm, true. Then maybe the fillup tool doesn't like it.
Peter
-
Carlos E. R. -
Dr. Peter Poeml -
Robert Schiele -
suse＠karsites.net