sdwdate - WARNING - Clock got changed by something other than sdwdate. sleep_time_seconds: 6040 time_delta: 6043 time_passed: -3

Qubes-Whonix
1

In qubes-whonix journalctl:

+ echo 'May 30 04:36:52 host sdwdate[784]: 2022-05-30 04:36:52 - sdwdate - WARNING - Clock got changed by something other than sdwdate.                 sleep_time_seconds: 6568 time_delta: 6564 time_passed: 4<br />'
+ tee -a /tmp/tmp.Z9hSQqbni1/journalctl_warn.txt_br
+ IFS=
+ read -r line
+ echo 'May 30 06:19:01 host sdwdate[784]: 2022-05-30 06:19:01 - sdwdate - WARNING - Clock got changed by something other than sdwdate.                 sleep_time_seconds: 6040 time_delta: 6043 time_passed: -3<br />'
+ tee -a /tmp/tmp.Z9hSQqbni1/journalctl_warn.txt_br

Wonder what effect timing in Qubes.

1 Like
2

2 posts were merged into an existing topic: sdwdate and sdwdate-gui development thread

4

I don’t know.

And attempting gaining Qubes developer attention also seems futile given the abundance of other unresolved Qubes issues:
https://www.whonix.org/wiki/Dev/Qubes#Issues

Therefore not even suggesting opening a ticket. Maybe related:

First, somehow a test or program would have to be written to reproduce this in a Qubes Debian VM. Then even if reported against Qubes, it might actually be a Xen issue that is difficult to fix and/or hardware dependent.

In short: I doubt we can reach this level of perfection.

1 Like