[Bug 681340] New: chkconfig stops working after installing cluster-glue package
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c0
Summary: chkconfig stops working after installing cluster-glue
package
Classification: openSUSE
Product: openSUSE 11.4
Version: Final
Platform: PC
OS/Version: All
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: comes@naic.edu
QAContact: qa@suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2)
Gecko/20070221 SeaMonkey/1.1.1
After installing cluster-glue package the command chkconfig <service> on
aborts with the following error:
insserv: FATAL: service network is missed in the runlevels 2 4 to use service
ha_logd
insserv: FATAL: service syslog is missed in the runlevels 4 to use service
ha_logd
insserv: exiting now!
/sbin/insserv failed, exit code 1
if I remove cluster-glue or if I disable the logd service (chkconfig logd off)
then chkconfig <service> on works again.
Reproducible: Always
Steps to Reproduce:
1. zypper in cluster-glue
2. chkconfig
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c1
--- Comment #1 from Giacomo Comes
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c2
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c3
Dejan Muhamedagic
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c4
Tim Serong
https://bugzilla.novell.com/show_bug.cgi?id=681340
https://bugzilla.novell.com/show_bug.cgi?id=681340#c5
--- Comment #5 from Tim Serong
But, $network only runs by default in runlevels 3 and 5 (not 2), and runlevel 4 is disabled by default on *SUSE, hence the insserv warning/error. This is all true on SLES as well, it's just that insserv doesn't complain there.
Correction, just for the record: SLES apparently starts network in runlevels 2, 3 and 5, so that's *not* the same. But runlevel 4 being disabled/unused/reserved is true in all cases. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com