time sync dysfunctional

10 views
Skip to first unread message

haaber

unread,
Feb 6, 2024, 5:49:03 AM2/6/24
to qubes-users
Hi,

I am still on Q4.1 (no time to do a full install now). Since a few days,
my time ran large out of sync, despite the swdate displaying normal
functioning. I rebooted, I restarted swdate. Its log says:

      [INFO] date output: 10:44:44

(which is London time, but otherwise correct), my set-to-Berlin-time
clock displays  10:42 which is 1h and 3min wrong. If it was 1h exactly,
I'd guess a user-malconfig, but 3min ??

do you have some hints on that?

Thank you, Bernhard


haaber

unread,
Feb 6, 2024, 7:11:42 AM2/6/24
to qubes...@googlegroups.com
addendum: if I run "date" in a client VM it will give the right
timezone, but still has 3min of delay..

unman

unread,
Feb 6, 2024, 10:22:35 AM2/6/24
to haaber, qubes...@googlegroups.com
Hi Bernhard
My first thought was that this is a Whonix issue, but the fact that
`date` has the same 3 min offset speaks against that.
Let me get to a 4.1 box and I will see if I can help.
Do you have locales set differently in qube from in dom0?
What timezone is set in dom0?
What in the qube?
What in your Whonix gateway?

--
I never presume to speak for the Qubes team.
When I comment in the mailing lists I speak for myself.

haaber

unread,
Feb 7, 2024, 2:41:52 AM2/7/24
to unman, qubes...@googlegroups.com

Hi Unman

I reply inline below.

On 2/6/24 11:45, 'haaber' via qubes-users wrote:
Hi,

I am still on Q4.1 (no time to do a full install now). Since a few days,
my time ran large out of sync, despite the swdate displaying normal
functioning. I rebooted, I restarted swdate. Its log says:

      [INFO] date output: 10:44:44

(which is London time, but otherwise correct), my set-to-Berlin-time
clock displays  10:42 which is 1h and 3min wrong. If it was 1h exactly,
I'd guess a user-malconfig, but 3min ??

do you have some hints on that?

Thank you, Bernhard

Hi Bernhard
My first thought was that this  is a Whonix issue, but the fact that
`date` has the same 3 min offset speaks against that.
Let me get to a 4.1 box and I will see if I can help.
Do you have locales set differently in qube from in dom0?
What timezone is set in dom0?
CET (UTC +1:00) according to timedatectl
What in the qube?
same, CET (UTC + 1:00)

What in your Whonix gateway?

the whonix netvm- is sys-whonix who connects to sys-firewall and finally sys-net (classic setup). Was that your question? Whonix is still whonix-16 (I know ..)


thank you, Bernhard

haaber

unread,
Feb 14, 2024, 5:44:51 AM2/14/24
to unman, qubes...@googlegroups.com

Dear unman & qubes -community,

I am still on Q4.1 (no time to do a full install now). Since a few days,
my time ran large out of sync, despite the swdate displaying normal
functioning. I rebooted, I restarted swdate. Its log says:

      [INFO] date output: 10:44:44

(which is London time, but otherwise correct), my set-to-Berlin-time
clock displays  10:42 which is 1h and 3min wrong. If it was 1h exactly,
I'd guess a user-malconfig, but 3min ??

do you have some hints on that?

Thank you, Bernhard

Hi Bernhard
My first thought was that this  is a Whonix issue, but the fact that
`date` has the same 3 min offset speaks against that.
Let me get to a 4.1 box and I will see if I can help.
Do you have locales set differently in qube from in dom0?
What timezone is set in dom0?
What in the qube?
What in your Whonix gateway?

things are even more funny (or not) since sys-whonix itself displays the correct time! The widget & other app-VM's are off by 3-4 minutes constantly.

that is very confusing ...  best, Bernhard

Reply all
Reply to author
Forward
0 new messages