Description of problem: ntpd fails to stop cleanly. Version-Release number of selected component (if applicable): ntp-4.2.0.a.20040617-4 How reproducible: every time Steps to Reproduce: 1. /sbin/service ntpd stop (or shut system down) 2. 3. Actual results: Shutting down ntpd: [FAILED] Expected results: Shutdown should succeed Additional info:
Is ntpd running? And if not, what kernel you have? /sbin/service ntpd status uname -r
Oddly, this isn't reproducible every time. For example, check the following session below. "ntpd dead but subsys locked" must be a big clue. Have seen these issues with kernels 2.6.11-1.27_FC3smp and 2.6.11-1.14_FC3smp. [root@pasiphae jgu]# /sbin/service ntpd status ntpd (pid 3773) is running... [root@pasiphae jgu]# /sbin/service ntpd stop Shutting down ntpd: [ OK ] [root@pasiphae jgu]# /sbin/service ntpd start ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] [root@pasiphae jgu]# /sbin/service ntpd stop Shutting down ntpd: [FAILED] [root@pasiphae jgu]# uname -r 2.6.11-1.27_FC3smp [root@pasiphae jgu]# /sbin/service ntpd start ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] [root@pasiphae jgu]# /sbin/service ntpd stop Shutting down ntpd: [ OK ] [root@pasiphae jgu]# /sbin/service ntpd start ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] [root@pasiphae jgu]# /sbin/service ntpd stop Shutting down ntpd: [FAILED] [root@pasiphae jgu]# /sbin/service ntpd stop Shutting down ntpd: [FAILED] [root@pasiphae jgu]# /sbin/service ntpd status ntpd dead but subsys locked
It should be duplicate of #154759. You can try this workaround: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145258#c13 For now I mark this as duplicate. If you disagree with duplicity please reopen it again. *** This bug has been marked as a duplicate of 154759 ***