Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177385 > unrolled thread

can not set time

Back to article view | Back to linux.debian.user

Contents

  can not set time Matthias Bodenbinder <matthias@bodenbinder.de> - 2017-02-04 14:10 +0100
    Re: can not set time Jude DaShiell <jdashiel@panix.com> - 2017-02-04 14:40 +0100
      Re: can not set time Matthias Bodenbinder <matthias@bodenbinder.de> - 2017-02-04 15:10 +0100
        Re: can not set time Jude DaShiell <jdashiel@panix.com> - 2017-02-04 17:50 +0100
          Re: can not set time Matthias Bodenbinder <matthias@bodenbinder.de> - 2017-02-04 18:10 +0100
    Re: can not set time Matthias Bodenbinder <matthias@bodenbinder.de> - 2017-02-04 15:50 +0100
      Re: can not set time Matthias Bodenbinder <matthias@bodenbinder.de> - 2017-02-04 17:50 +0100

#177385 — can not set time

Hi,

I have a weird issue with one of my debian boxes (LMDE): I can not set the time. The time is off by ca. 14 min and whatever I try to fix it is failing. I tried ntp, ntpdate, date and rdate. Nothing helps.

ntpdate shows the offset but is not fixing it.

91# ntpdate 0.debian.pool.ntp.org
 4 Feb 14:03:55 ntpdate[8159]: step time server 85.114.132.52 offset -855.296824 sec


rdate is showing some interesting behaviour. If I run a command like "date && rdate -v  ptbtime1.ptb.de && date" to see the time before and after rdate, the output suggests that rdate was successful:

81# date && rdate -v  ptbtime1.ptb.de && date
Sat Feb  4 14:16:04 CET 2017
Sat Feb  4 14:01:49 CET 2017
rdate: adjust local clock by -855 seconds
Sat Feb  4 14:01:49 CET 2017

But in fact 1 second later the time is back to old values again:

82# date
Sat Feb  4 14:16:06 CET 2017


timedatectl is showing wrong time as well:

93# timedatectl
      Local time: Sat 2017-02-04 14:20:39 CET
  Universal time: Sat 2017-02-04 13:20:39 UTC
        RTC time: Sat 2017-02-04 13:20:39
       Time zone: Europe/Berlin (CET, +0100)


But is should be:
      Local time: Sa 2017-02-04 14:06:25 CET
  Universal time: Sa 2017-02-04 13:06:25 UTC
        RTC time: Sa 2017-02-04 13:06:25
       Time zone: Europe/Berlin (CET, +0100)


I am lost.

Matthias

[toc] | [next] | [standalone]

#177387

please check that other box and see if it has systemd-timesyncd.service 
on it.
You can probably start that service up and solve that problem.
Then try timedatectl set-ntp true.
That should make timesync happen on boot.
On Sat, 4 
Feb 2017, Matthias Bodenbinder wrote:

> Date: Sat, 4 Feb 2017 08:07:16
> From: Matthias Bodenbinder <matthias@bodenbinder.de>
> To: debian-user@lists.debian.org
> Subject: can not set time
> Resent-Date: Sat,  4 Feb 2017 13:07:40 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> Hi,
>
> I have a weird issue with one of my debian boxes (LMDE): I can not set the time. The time is off by ca. 14 min and whatever I try to fix it is failing. I tried ntp, ntpdate, date and rdate. Nothing helps.
>
> ntpdate shows the offset but is not fixing it.
>
> 91# ntpdate 0.debian.pool.ntp.org
> 4 Feb 14:03:55 ntpdate[8159]: step time server 85.114.132.52 offset -855.296824 sec
>
>
> rdate is showing some interesting behaviour. If I run a command like "date && rdate -v  ptbtime1.ptb.de && date" to see the time before and after rdate, the output suggests that rdate was successful:
>
> 81# date && rdate -v  ptbtime1.ptb.de && date
> Sat Feb  4 14:16:04 CET 2017
> Sat Feb  4 14:01:49 CET 2017
> rdate: adjust local clock by -855 seconds
> Sat Feb  4 14:01:49 CET 2017
>
> But in fact 1 second later the time is back to old values again:
>
> 82# date
> Sat Feb  4 14:16:06 CET 2017
>
>
> timedatectl is showing wrong time as well:
>
> 93# timedatectl
>      Local time: Sat 2017-02-04 14:20:39 CET
>  Universal time: Sat 2017-02-04 13:20:39 UTC
>        RTC time: Sat 2017-02-04 13:20:39
>       Time zone: Europe/Berlin (CET, +0100)
>
>
> But is should be:
>      Local time: Sa 2017-02-04 14:06:25 CET
>  Universal time: Sa 2017-02-04 13:06:25 UTC
>        RTC time: Sa 2017-02-04 13:06:25
>       Time zone: Europe/Berlin (CET, +0100)
>
>
> I am lost.
>
> Matthias
>
>
>
>
>
>
>

-- 

[toc] | [prev] | [next] | [standalone]

#177389

Am 04.02.2017 um 14:36 schrieb Jude DaShiell:
> please check that other box and see if it has systemd-timesyncd.service on it.
> You can probably start that service up and solve that problem.
> Then try timedatectl set-ntp true.
> That should make timesync happen on boot.
> On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:


timedatectl set-ntp true
did not help. It is not changing the time.

My reference PC has debian testing running with systemd-timesyncd. But the broken PC is MINT LMDE which is still on init.d.

Matthias

[toc] | [prev] | [next] | [standalone]

#177401

On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:

> Date: Sat, 4 Feb 2017 09:07:00
> From: Matthias Bodenbinder <matthias@bodenbinder.de>
> To: debian-user@lists.debian.org
> Subject: Re: can not set time
> Resent-Date: Sat,  4 Feb 2017 14:07:22 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> Am 04.02.2017 um 14:36 schrieb Jude DaShiell:
>> please check that other box and see if it has systemd-timesyncd.service on it.
>> You can probably start that service up and solve that problem.
>> Then try timedatectl set-ntp true.
>> That should make timesync happen on boot.
>> On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:
>
>
> timedatectl set-ntp true
> did not help. It is not changing the time.
>
> My reference PC has debian testing running with systemd-timesyncd. But the broken PC is MINT LMDE which is still on init.d.
>
> Matthias
>
Okay, since you have ntp, ntpd -qg and then hwclock --systohc --utc may 
get this working for you.  We probably don't need to do anything with 
your timezone setting link to /etc/localtime by now.

>

--

[toc] | [prev] | [next] | [standalone]

#177404

Am 04.02.2017 um 17:43 schrieb Jude DaShiell:
> On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:
>
>> Date: Sat, 4 Feb 2017 09:07:00
>> From: Matthias Bodenbinder <matthias@bodenbinder.de>
>> To: debian-user@lists.debian.org
>> Subject: Re: can not set time
>> Resent-Date: Sat,  4 Feb 2017 14:07:22 +0000 (UTC)
>> Resent-From: debian-user@lists.debian.org
>>
>> Am 04.02.2017 um 14:36 schrieb Jude DaShiell:
>>> please check that other box and see if it has
>>> systemd-timesyncd.service on it.
>>> You can probably start that service up and solve that problem.
>>> Then try timedatectl set-ntp true.
>>> That should make timesync happen on boot.
>>> On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:
>>
>>
>> timedatectl set-ntp true
>> did not help. It is not changing the time.
>>
>> My reference PC has debian testing running with systemd-timesyncd. But
>> the broken PC is MINT LMDE which is still on init.d.
>>
>> Matthias
>>
> Okay, since you have ntp, ntpd -qg and then hwclock --systohc --utc may
> get this working for you.  We probably don't need to do anything with
> your timezone setting link to /etc/localtime by now.

Hello Jude,

I tried it all. I googled almost every command related to time setting 
and tried it out. But it did not work. I am still not sure why.

But now, after switching to systemd and systemd-timesyncd it works. See 
my other post.

Thank you for help anyways.
Matthias

[toc] | [prev] | [next] | [standalone]

#177391

More info:

I switched to systemd and systemd-timesyncd. During boot the time is synced back and forth multiple times and in the end it stays wrong. 

Look at this. See the timestamps for each line. Going back and forth.

Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 78.46.253.198:123 (2.debian.pool.ntp.org).
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.874s/0.016s/560.321s/+0pp
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.864s/0.015s/457.500s/+0pp
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.854s/0.015s/323.501s/+0pp
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.844s/0.015s/0.036s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.834s/0.015s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.824s/0.016s/0.029s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.814s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.804s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.794s/0.015s/0.029s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.784s/0.015s/0.036s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.774s/0.016s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.764s/0.016s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.754s/0.015s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.744s/0.015s/0.037s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.733s/0.016s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.723s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.713s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.702s/0.017s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.693s/0.015s/0.037s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.683s/0.015s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.673s/0.016s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.663s/0.015s/0.037s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.653s/0.015s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.643s/0.016s/0.029s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.633s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.622s/0.017s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.613s/0.015s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.602s/0.016s/0.037s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.593s/0.016s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.582s/0.015s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.572s/0.015s/0.037s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.566s/0.016s/0.044s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.556s/0.016s/0.029s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.


Any idea?

Matthias

[toc] | [prev] | [next] | [standalone]

#177400

Am 04.02.2017 um 15:49 schrieb Matthias Bodenbinder:
> More info:
>
> I switched to systemd and systemd-timesyncd. During boot the time is synced back and forth multiple times and in the end it stays wrong.
>
> Look at this. See the timestamps for each line. Going back and forth.
>
> Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 78.46.253.198:123 (2.debian.pool.ntp.org).
> Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm
> Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
> Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp
> Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
> Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp
> Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
> Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp
> Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
> Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp
> Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.

The switch to systemd and systemd-timesyncd did the trick. But it takes 
very long. Its obvious from the journal messages but I did not get it at 
first: timesyncd changes the time in small increments of only 0.01 seconds.

I just had to wait and now the time is correct.

Matthias

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web