Bug#835474: systemd: timesyncd does not sync time after resume from suspend (need to do so manually with timedatectl)

[Michael Biebl]

Control: tags -1 + moreinfo

On Fri, 26 Aug 2016 09:28:14 +0200 Elena ``of Valhalla''
<valhalla-d at trueelena.org> wrote:
> Package: systemd
> Version: 231-4
> Severity: normal
> 
> Dear Maintainer,
> 
> I suspend my laptop using s2disk. When resuming, the clock remains at
> the time when the suspend happened, even if timedatectl claims that it
> is being synced:
> 
>     # timedatectl status
> 	  Local time: Thu 2016-08-25 19:26:17 CEST
>       Universal time: Thu 2016-08-25 17:26:17 UTC
> 	    RTC time: Thu 2016-08-25 17:26:17
> 	   Time zone: Europe/Rome (CEST, +0200)
>      Network time on: yes
>     NTP synchronized: yes
>      RTC in local TZ: no
> 
> I've tried waiting a bit, but this persisted for some 20 minutes (I think), so I forced an update with 
> 
>   # timedatectl set-ntp false
>   # timedatectl set-ntp true
> 
> And afterwards the time was (apparently) correctly synced.
> 
> Please, let me know what further informations are needed to debug the
> issue, and I would be happy to do some other test.
> 

If this problem still happens,

Can you run
journalctl -f -u systemd-timesyncd.service
and see what it reports after a resume


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161222/7d2f1dc1/attachment.sig>