[opensuse] NTP, KDE 4.9,and NetworkManager on 12.2
On openSUSE 12.1 with KDE 4.9 (same with 4.8 and earlier) when I start my network via NetworkManager (wired or wireless), NTP seems not quite right. I is runnuig. But it does not set the time right unless I restart it. It has been this way for a while (months). Here is a sample of what I mean: # rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: inactive (dead) since Fri, 31 Aug 2012 21:13:26 +0200; 4h 39min ago Process: 2309 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 1274 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service # date Sat Sep 1 01:52:46 CEST 2012 # rcntp restart redirecting to systemctl # date Fri Aug 31 23:53:46 CEST 2012 The final date after the restart is correct. Have I missed doing something? -- -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/31/12 18:00, Roger Oberholtzer pecked at the keyboard and wrote:
On openSUSE 12.1 with KDE 4.9 (same with 4.8 and earlier) when I start my network via NetworkManager (wired or wireless), NTP seems not quite right. I is runnuig. But it does not set the time right unless I restart it. It has been this way for a while (months). Here is a sample of what I mean:
# rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: inactive (dead) since Fri, 31 Aug 2012 21:13:26 +0200; 4h 39min ago Process: 2309 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 1274 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service
# date Sat Sep 1 01:52:46 CEST 2012
# rcntp restart redirecting to systemctl
# date Fri Aug 31 23:53:46 CEST 2012
The final date after the restart is correct. Have I missed doing something?
No you haven't. The problem is that ntp tries to run during bootup but without a running network it fails. I have this same problem on my laptop even though I have the wireless set to start at boot time, ntp startup is before (network manager) network startup. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2012-09-01 at 09:26 -0400, Ken Schneider - openSUSE wrote:
On 08/31/12 18:00, Roger Oberholtzer pecked at the keyboard and wrote:
On openSUSE 12.1 with KDE 4.9 (same with 4.8 and earlier) when I start my network via NetworkManager (wired or wireless), NTP seems not quite right. I is runnuig. But it does not set the time right unless I restart it. It has been this way for a while (months). Here is a sample of what I mean:
# rcntp status redirecting to systemctl ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Active: inactive (dead) since Fri, 31 Aug 2012 21:13:26 +0200; 4h 39min ago Process: 2309 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS) Process: 1274 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ntp.service
# date Sat Sep 1 01:52:46 CEST 2012
# rcntp restart redirecting to systemctl
# date Fri Aug 31 23:53:46 CEST 2012
The final date after the restart is correct. Have I missed doing something?
No you haven't. The problem is that ntp tries to run during bootup but without a running network it fails. I have this same problem on my laptop even though I have the wireless set to start at boot time, ntp startup is before (network manager) network startup.
My wireless starts when I log in. Being a laptop, the connection does change. I had this issue a year or so ago. Then it was fixed. It reappeared somewhere in 12.1. Since I have not heard screams and threats, I guessed it was my own private issue. So I count two of us with the issue. Anyone else have a non-functional ntp when starting wireless at login via NetworkManager? I do indeed have a dual boot system with Winders 7 as the evil other. I have the hardware clock set to UTC (set in BIOS). I know that Windows mucks about with this. But I am 95% certain I set the BIOS correct after a Windows boot. I will check again. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer [03.09.2012 15:13]:
On Sat, 2012-09-01 at 09:26 -0400, Ken Schneider - openSUSE wrote:
On 08/31/12 18:00, Roger Oberholtzer pecked at the keyboard and wrote:
On openSUSE 12.1 with KDE 4.9 (same with 4.8 and earlier) when I start my network via NetworkManager (wired or wireless), NTP seems not quite right. I is runnuig. But it does not set the time right unless I restart it. It has been this way for a while (months). Here is a sample of what I mean:
My wireless starts when I log in. Being a laptop, the connection does change. I had this issue a year or so ago. Then it was fixed. It reappeared somewhere in 12.1. Since I have not heard screams and threats, I guessed it was my own private issue.
So I count two of us with the issue. Anyone else have a non-functional ntp when starting wireless at login via NetworkManager?
Yep, me. This is, before I check the "system connection" box in KNetworkManager. :-) This is explained in <http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.nm.html#sec.nm.security> in section "21.7.1. User and System Connections" ("Connections that are defined as system connection can be shared by all users and are made available right after NetworkManager is started—before any users log in."). However, you have to convince the ntp daemon to wait until NM has started. I'm sure systemd will manage it befor christmas. 2015. Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 1. September 2012, 09:26:10 schrieb Ken Schneider - openSUSE:
[...] No you haven't. The problem is that ntp tries to run during bootup but without a running network it fails. I have this same problem on my laptop even though I have the wireless set to start at boot time, ntp startup is before (network manager) network startup.
I do not think so: I have the wireless set to start at KDE login time and configured ntp to start at boot time. Thus, ntp will always fail at boot time. Nonetheless, it perfectly synchronizes later. So, try to give it the IP address of your local caching/proxy ntp in your wireless router or the one(s) of your ISP. This works for me. Please note: I am not sure that this still needed but it was a workaround I found some years ago. Nowadays ntp notices when an interface goes up or down. HTH Jan -- A penny saved is ridiculous. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 1. September 2012, 00:00:07 schrieb Roger Oberholtzer:
On openSUSE 12.1 with KDE 4.9 (same with 4.8 and earlier) when I start my network via NetworkManager (wired or wireless), NTP seems not quite right.
Using openSUSE 12.1 with KDE 4.7 and wireless autoconnection on KDE login, it seems to work fine. At least "ntpdc -p" shows an increasing "reach" state and finally marks the ntp server with an "*".
I is runnuig. [...] # rcntp status [...] Active: inactive (dead) since Fri, 31 Aug 2012 21:13:26 [...]
That does not look like it is running! The line should say " Active: active (running)". What does "ntpdc -p" say?
# date Sat Sep 1 01:52:46 CEST 2012
# rcntp restart redirecting to systemctl
# date Fri Aug 31 23:53:46 CEST 2012
The final date after the restart is correct.
Looks your hardware clock is in local time and Linux does not know about it and thinks it is in UTC and, thus, adds 2h! Maybe you have a dual-boot system and Windows changes the time to local time. Check the HWCLOCK option in /etc/sysconfig/clock.
Have I missed doing something?
Try to use the IP address of the ntp server instead its host name. I use the ntp server of my ISP or the built-in one of my WLAN router. Gruß Jan -- The knowledge that a secret exists is half the secret. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Jan Ritzerfeld -
Ken Schneider - openSUSE -
Roger Oberholtzer -
Werner Flamme