Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 181613 - init script removed on every upgrade
init script removed on every upgrade
Product: Fedora
Classification: Fedora
Component: nagios (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McGrath
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2006-02-15 09:11 EST by Martin Ebourne
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-15 15:13:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Ebourne 2006-02-15 09:11:04 EST
Description of problem:
On every upgrade of this nagios package the init script is deregistered from

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Install previous version of nagios
2. Upgrade to the current one
Actual results:
nagios has been unregistered from chkconfig and therefore will no longer
automatically start on boot.

Expected results:
nagios should still be registered in the same runlevels as before

Additional info:
The problem is the preun script:
  /sbin/service nagios stop > /dev/null 2>&1 || :
  /sbin/chkconfig --del nagios || :

This needs a check for upgrading, as in:
  if [ $1 = 0 ]; then
    /sbin/service nagios stop > /dev/null 2>&1 || :
    /sbin/chkconfig --del nagios || :

This is a standard idiom in spec files. This would be forgivable in most
packages but nothing emails me to tell me nagios is not running and I only find
out when something else fails quietly. This package really has to get this right
- doesn't anyone review these packages?

As to fixing this: because the preun script is run from the old package this
will break again (for the last time) on the next upgrade. Suggest you warn
people in the email.
Comment 1 Mike McGrath 2006-02-15 15:13:45 EST
Damn, I noticed this on the last upgrade and completely forgot to fix it.  Its
fixed in the next release.  (Which is already built but not yet in the Extra's Repo)

Note You need to log in before you can comment on or make changes to this bug.