New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

whonix clock issues after recent updates #3930

Closed
qubesissues opened this Issue May 26, 2018 · 7 comments

Comments

Projects
None yet
6 participants
@qubesissues

Qubes OS version:

4.0 Release Candidate updated (all Qubes and dom0) on 24 May 2018

Affected component(s):

sys-whonix and other NetVMs based on whonix-gw


Steps to reproduce the behavior:

  • Update all VMs and dom0 as of 24 May 2018
  • Create and use a VM that depends on sys-whonix

Expected behavior:

The netVM (ex - sys-whonix) will start up without error and provide TOR networking.

Actual behavior:

Two things happen:

First you will get a popup from the netVM (ex sys-whonix) that has this error:

ERROR: Systemd Clock Check Result:
Unexpected results by timedatectl.
timedatectl_output_pretty:
Local time: Sat 2018-05-26 05:21:12 UTC
Universal time: Sat 2018-05-26 05:21:12 UTC
RTC time: n/a
Time zone: Etc/UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: n/a
It is generally recommended to keep the default as per Whonix Design. [1] If you did not change timezone related settings, please report this Whonix bug. If you know what you are doing and changed this on purpose, feel free to disable this check. [2]

[1] https://www.whonix.org/wiki/Dev/Design-Shared#timezone
[2] Create a file /etc/whonix.d/50_whonixcheck_user and add:
whonixcheck_skip_functions+=" check_systemd_clock "

Second you will lose networking through this netVM (ex sys-whonix) after about 10 minutes.

General notes:

My dom0 time is set to UTC. It has been set to UTC always and I only have this error after upgrading on 24 May 2018.


Related issues:

@esote

This comment has been minimized.

Show comment
Hide comment
@esote

esote May 26, 2018

I am getting this exact same error. The error also prevents the rest of the WhonixCheck, however I have (so far) not experienced it losing network after about 10 minutes.

esote commented May 26, 2018

I am getting this exact same error. The error also prevents the rest of the WhonixCheck, however I have (so far) not experienced it losing network after about 10 minutes.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 26, 2018

Member

Duplicate of #3469

Member

marmarek commented May 26, 2018

Duplicate of #3469

@marmarek marmarek marked this as a duplicate of #3469 May 26, 2018

@marmarek marmarek closed this May 26, 2018

@qubesissues

This comment has been minimized.

Show comment
Hide comment
@qubesissues

qubesissues May 26, 2018

@marmarek @andrewdavidwong Is this a duplicate? On my system this issue began only on a very recent update. The other issue was reported in January.

@marmarek @andrewdavidwong Is this a duplicate? On my system this issue began only on a very recent update. The other issue was reported in January.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 27, 2018

Member

@adrelanos, can you confirm whether this is a duplicate of #3469?

Member

andrewdavidwong commented May 27, 2018

@adrelanos, can you confirm whether this is a duplicate of #3469?

@marcialvieira

This comment has been minimized.

Show comment
Hide comment
@marcialvieira

marcialvieira Jun 1, 2018

This is happening to me too, this is what was updated in my whonix-gw when it occurred.

Start-Date: 2018-05-29  05:34:19
Commandline: /usr/bin/apt-get.anondist-orig -V dist-upgrade
Install: dconf-cli:amd64 (0.22.0-1, automatic)
Upgrade: procps:amd64 (3.3.9-9, 3.3.9-9+deb8u1), libxen-4.8:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), libxen-lowlevel1.0:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), qubes-core-agent:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), libxenstore3.0:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), libprocps3:amd64 (3.3.9-9, 3.3.9-9+deb8u1), xenstore-utils:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), xdg-utils:amd64 (1.1.0~rc1+git20111210-7.4, 1.1.0~rc1+git20111210-7.4+deb8u1), qubes-core-agent-networking:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), xen-utils-common:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), qubes-core-agent-dom0-updates:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), qubes-core-agent-passwordless-root:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), qubes-core-agent-qrexec:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1)
End-Date: 2018-05-29  05:34:59

marcialvieira commented Jun 1, 2018

This is happening to me too, this is what was updated in my whonix-gw when it occurred.

Start-Date: 2018-05-29  05:34:19
Commandline: /usr/bin/apt-get.anondist-orig -V dist-upgrade
Install: dconf-cli:amd64 (0.22.0-1, automatic)
Upgrade: procps:amd64 (3.3.9-9, 3.3.9-9+deb8u1), libxen-4.8:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), libxen-lowlevel1.0:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), qubes-core-agent:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), libxenstore3.0:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), libprocps3:amd64 (3.3.9-9, 3.3.9-9+deb8u1), xenstore-utils:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), xdg-utils:amd64 (1.1.0~rc1+git20111210-7.4, 1.1.0~rc1+git20111210-7.4+deb8u1), qubes-core-agent-networking:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), xen-utils-common:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), qubes-core-agent-dom0-updates:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), qubes-core-agent-passwordless-root:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), qubes-core-agent-qrexec:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1)
End-Date: 2018-05-29  05:34:59
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@marcialvieira

This comment has been minimized.

Show comment
Hide comment
@marcialvieira

marcialvieira Jun 23, 2018

Thank you @adrelanos, using Whonix 14 I get no alerts.

Thank you @adrelanos, using Whonix 14 I get no alerts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment