Description of problem: NTP service crashed after stopping network service Version-Release number of selected component (if applicable): ntp-4.2.6p5-5.fc18.x86_64 How reproducible: 100% Steps to Reproduce: 1. run ntp service 2. stop network service 3. ntp service will fail Actual results: ntp service will fail Expected results: ntp service shouldn't fail Additional info:
Created attachment 643642 [details] ntpd failure log --- snip from the log ---- Nov 11 16:35:20 dhcp-1-165 ntpd[14399]: 0.0.0.0 c615 05 clock_sync Nov 11 16:37:23 dhcp-1-165 systemd[1]: Stopping LSB: Bring up/down networking... Nov 11 16:37:23 dhcp-1-165 systemd[1]: Stopping Network Time Service... Nov 11 16:37:23 dhcp-1-165 ntpd[14399]: ntpd exiting on signal 15 Nov 11 16:37:23 dhcp-1-165 systemd[1]: Starting Network Time Service... Nov 11 16:37:23 dhcp-1-165 ntpd[15124]: ntpd 4.2.6p5 Wed Oct 24 16:46:54 UTC 2012 (1) Nov 11 16:37:23 dhcp-1-165 ntpd[15125]: proto: precision = 0.069 usec ---- snip from the log ---- In this particular log you can see that NTP raise up again because it explicitly required by vdsmd service.
It seems the ntpd service didn't crash, but was restarted for some reason. It happens without vdsmd service too. Looking at the systemctl dot output I don't see anything suspicious, let's see if systemd maintainers know what is going on.
Both chrony and ntp ship hooks in /etc/dhcp/dhclient.d/ and /etc/NetworkManager/dispatcher.d/. Is it possible that some of the hooks is the cause?
Good point, Michal. That would explain it. Igor, do you see the restart of the ntp service when PEERNTP=no is added to /etc/sysconfig/network? That would be expected behavior and not a bug.
(In reply to comment #4) > Good point, Michal. That would explain it. > > Igor, do you see the restart of the ntp service when PEERNTP=no is added to > /etc/sysconfig/network? That would be expected behavior and not a bug. No, with PEERNTP=no ntpd doesn't restart
Ok, thanks. Let's close this as NOTABUG.