[opensuse-factory] stop job delays shutdown (ntpd)
Is there anything below that explains why my TW host big31 is always delayed to reboot or shutdown by "a stop job is running for NTP Server Daemon"? # systemctl status ndpd ● ntpd.service - NTP Server Daemon Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Drop-In: /run/systemd/generator/ntpd.service.d └─50-insserv.conf-$time.conf Active: active (running) since Mon 2017-03-13 19:51:22 EDT; 1min 28s ago Docs: man:ntpd(1) Process: 1018 ExecStart=/usr/sbin/start-ntpd start (code=exited, status=0/SUCCESS) Main PID: 1038 (ntpd) Tasks: 2 (limit: 4915) CGroup: /system.slice/ntpd.service ├─1038 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf └─1043 ntpd: asynchronous dns resolver Mar 13 19:51:21 big31 systemd[1]: Starting NTP Server Daemon... Mar 13 19:51:22 big31 ntpd[1030]: ntpd 4.2.8p9@1.3265-o Sat Mar 11 14:51:28 UTC 2017 (1): Starting Mar 13 19:51:22 big31 ntpd[1030]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf Mar 13 19:51:22 big31 ntpd[1038]: proto: precision = 0.120 usec (-23) Mar 13 19:51:22 big31 ntpd[1038]: restrict: ignoring line 57, mask '::' unusable. Mar 13 19:51:22 big31 ntpd[1038]: switching logging to file /var/log/ntp Mar 13 19:51:22 big31 start-ntpd[1018]: Starting network time protocol daemon (NTPD) Mar 13 19:51:22 big31 systemd[1]: Started NTP Server Daemon. If not, what can I do to find out why? Installation has no persistent journal. Can systemd-analyze somehow be used for shutdown analysis (if there's something in it's man page, it's non-obvious)? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-14 01:06, Felix Miata wrote:
Is there anything below that explains why my TW host big31 is always delayed to reboot or shutdown by "a stop job is running for NTP Server Daemon"?
No, that's the starting log.
If not, what can I do to find out why? Installation has no persistent journal. Can systemd-analyze somehow be used for shutdown analysis (if there's something in it's man page, it's non-obvious)?
Maybe with persistent journal. Otherwise, log to another computer. Don't ask me how, with systemd I don't know. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljHN+8ACgkQja8UbcUWM1x3zgD/RVt6ri+gIwgG0hnvANJKavtO Ttcb3/t7T8P2FlyhV4oBAIJ13KyphfSi1dlmFwZIrq+FmcUXwfNJSximfkmUhTDH =c60c -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. composed on 2017-03-14 01:23 (UTC+0100):
On 2017-03-14 01:06, Felix Miata wrote:
Is there anything below that explains why my TW host big31 is always delayed to reboot or shutdown by "a stop job is running for NTP Server Daemon"?
No, that's the starting log.
If not, what can I do to find out why? Installation has no persistent journal. Can systemd-analyze somehow be used for shutdown analysis (if there's something in it's man page, it's non-obvious)?
Maybe with persistent journal. Otherwise, log to another computer. Don't ask me how, with systemd I don't know.
Remote login is terminated quite before the stop job message appears. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-14 08:00, Felix Miata wrote:
Carlos E. R. composed on 2017-03-14 01:23 (UTC+0100):
Maybe with persistent journal. Otherwise, log to another computer. Don't ask me how, with systemd I don't know.
Remote login is terminated quite before the stop job message appears.
No, it is not with remote login. It is direct kernel message dump to IP:port. I think the name is "netconsole". But it is the kernel log, I don't know about the "journal". - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljH9IcACgkQja8UbcUWM1zAbQEAnF7hsg29WEuNQXR3JAO8U2VM BksaFUXogli9sjIqA8UBAIXpowau1kKkwZIaaRIgl4l5DZkWMrfOVbggu5+TyE52 =Z/Fp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Felix Miata wrote:
If not, what can I do to find out why? Installation has no persistent journal. Can systemd-analyze somehow be used for shutdown analysis (if there's something in it's man page, it's non-obvious)?
Not sure. Mine has logfile /var/log/ntp set in /etc/ntp.conf. There you can see the shutdown messages. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Carlos E. R.
-
Felix Miata
-
Peter Suetterlin