Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install RHEL3, configure httpd for runlevel 3,4,5
2. upgrade to RHEL4
3. httpd is not running after upgrade. chkconfig
chkconfig --list httpd
httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
chkconfig --list httpd
httpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
probably a duplicate of 131919, but I thought I would get something in
bugzilla for RHEL4.
Also, I was left with an httpd.conf.rpmsave and httpd.conf.rpmnew after
upgrade, but no httpd.conf.
> Then something very funky has happened. Was the RHEL3 httpd.conf modified
> from the default?
Yes. I expected an httpd.conf.rpmnew, but didn't expect my file to then be
moved to httpd.conf.rpmsave.
Here is some info from the upgrade.log:
warning: /etc/httpd/conf/httpd.conf saved as /etc/httpd/conf/httpd.conf.rpmsave
warning: /etc/httpd/conf/httpd.conf created as /etc/httpd/conf/httpd.conf.rpmnew
> I tried and failed to reproduce bug 131919, I hoped it was user error.
I'll run a few more tests.
That looks wrong, I don't see how that could happen due to a mere packaging bug.
Jeremy/Jeff, are there any known anaconda/rpm issues which could cause
something like the above?
Probably related. I had a similiar issue with up2date after a RHEL3 to RHEL4
migration. From my upgrade.log file
warning: /etc/sysconfig/rhn/up2date created as /etc/sysconfig/rhn/up2date.rpmnew
warning: /etc/sysconfig/rhn/sources saved as /etc/sysconfig/rhn/sources.rpmsave
Once RHEL4 booted, I had no /etc/sysconfig/rhn/sources file!
Hope I am not too OT for this bug.
What I can hypothesize is happening here with httpd is some weird
behaviour from the upgrade from "httpd" to "httpd + apr + apr-util".
jbj could you have a look at this, am I off-base?
it looks like on the upgrade to the RHEL4 apr package (which replaces
some files previously in the RHEL3 httpd package), httpd is first
being *removed*; the %postun is run removing the chkconfig links, and
a modified httpd.conf is renamed to httpd.conf.rpmsave:
warning: /etc/httpd/conf/httpd.conf saved as
then later on httpd is installed as fresh:
warning: /etc/httpd/conf/httpd.conf created as
warning: /etc/sysconfig/httpd created as /etc/sysconfig/httpd.rpmnew
except RPM still had some memory that httpd.conf did exist, so it
created httpd.conf.rpmsave instead.
I can reproduce this at will...
I'm going to presume this is some RPM bug, though possibly it is
anaconda related. If instead there's some packaging mistake which I
can correct I'm just as happy to hear what it is...
What is the status of this bug? I am still seeing it on RHEL4U1 updates. This
routinely happens to httpd and up2date, where httpd.conf.rpmnew will be created
with no httpd.conf . And /etc/sysconfig/rhn/up2date.rpmnew is created with no
/etc/sysconfig/rhn/up2date (or the sources file will have a similiar fate).
Bug or not, the behavior in rpm has been exactly the same for years. Guessing
that it's an rpm bug and asking how to fix your packaging has the burden of proof
going the wrong way.
I was never able to reproduce this. If anybody is able to reproduce the bug and is still affected by the issue, please reopen.