[Bug 801419] New: ntp does not start properly if Network manager is used
https://bugzilla.novell.com/show_bug.cgi?id=801419 https://bugzilla.novell.com/show_bug.cgi?id=801419#c0 Summary: ntp does not start properly if Network manager is used Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: axel.braun@gmx.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 After boot and login to KDE, I have to enter the password for kwallet before a network connection is up. ntp uses this time to die without further notice: T520:/home/docb # rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: inactive (dead) since Tue, 15 Jan 2013 15:34:09 +0100; 1 day and 1h ago Process: 1498 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 804 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service Jan 15 15:31:40 T520.axxite.internal ntpd[887]: proto: precision = 0.132 usec Jan 15 15:31:40 T520.axxite.internal ntpd[887]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 15 15:31:40 T520.axxite.internal ntpd[887]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Jan 15 15:31:40 T520.axxite.internal ntp[804]: Starting network time protocol daemon (NTPD)..done Jan 15 15:31:40 T520.axxite.internal ntpd[887]: Listen and drop on 1 v6wildcard :: UDP 123 Jan 15 15:31:41 T520.axxite.internal ntpd[887]: Listen normally on 2 lo 127.0.0.1 UDP 123 Jan 15 15:31:41 T520.axxite.internal ntpd[887]: Listen normally on 3 lo ::1 UDP 123 Jan 15 15:31:41 T520.axxite.internal ntpd[887]: peers refreshed Jan 15 15:31:41 T520.axxite.internal ntpd[887]: Listening on routing socket on fd #20 for interface updates Jan 15 15:34:09 T520.axxite.internal ntp[1498]: Shutting down network time protocol daemon (NTPD)..done After a restart, ntp works as expected (note that this is one day later!): T520:/home/docb # rcntp restart redirecting to systemctl T520:/home/docb # rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: active (running) since Wed, 16 Jan 2013 18:20:26 +0100; 4s ago Process: 1498 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 8118 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service └ 8150 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf Jan 16 18:20:26 T520.axxite.internal ntp[8118]: Starting network time protocol daemon (NTPD)..done Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen and drop on 1 v6wildcard :: UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 2 lo 127.0.0.1 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 3 wlan0 192.168.1.16 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 4 wlan0 fe80::120b:a9ff:feef:6c4c UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listen normally on 5 lo ::1 UDP 123 Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: peers refreshed Jan 16 18:20:26 T520.axxite.internal ntpd[8150]: Listening on routing socket on fd #22 for interface updates I dont feel that this is a configuration issue, but correct me if I'm wrong. IMHO ntp should restart after each network connection (i.e. after resume from suspend) Reproducible: Always Steps to Reproduce: 1. reboot PC 2. 3. Actual Results: system time is wrong, ntp has to be restarted after every boot Expected Results: ntp restarts after network connection is settled Please see bug 774502 from comment 18 onwards. Marius recommended to open a new bug for this -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=801419 https://bugzilla.novell.com/show_bug.cgi?id=801419#c Du Weihua <whdu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |varkoly@suse.com |ovo.novell.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=801419 https://bugzilla.novell.com/show_bug.cgi?id=801419#c1 --- Comment #1 from Axel Braun <axel.braun@gmx.de> 2013-05-07 12:51:18 UTC --- working in 12.3 with KDE 4.10.2 -> closing? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=801419 https://bugzilla.novell.com/show_bug.cgi?id=801419#c2 Peter Varkoly <varkoly@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #2 from Peter Varkoly <varkoly@suse.com> 2014-06-11 13:34:43 UTC --- Works in 13.1 too -- 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