Qubes R4.0 rc4 System Time Errors

[sebuq]

The virgin whonix templates downloaded with official Qubes R4 rc4 release,
did not result in errors via whonixcheck. However, subsequently after updating the
whonix-gw template I get the following system time error:

ERROR: Systemd Clock Check Result:
Unexpected results by timedatectl.
timedatectl_output_pretty:
Local time: Wed 2018-02-14 10:25:33 UTC
Universal time: Wed 2018-02-14 10:25:33 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] Whonix ™ Networking Implementation Documentation
[2] Create a file /etc/whonix.d/50_whonixcheck_user and add:
whonixcheck_skip_functions+=" check_systemd_clock "

In reality, there’s approx 2 minutes dfference between my local clock and the whonix system clock

[Patrick]

duplicate of

sys-whonix launch error

[sebuq]

I’m having difficulty following the thread.
My interpretation is: permanent solution to be Whonix 14. Temporary solution
disable check_systemd_clock
Is this a fair assessment?

[0brand]

Hi sebuq

Yes, temporary solution would be to:

Create a file /etc/whonix.d/50_whonixcheck_user and add:
whonixcheck_skip_functions+=" check_systemd_clock "

[sebuq]

Hi
Tried that but still get same error.
I’ve checked that the new file and contents are persistent across
reboots, and they are.
Any thoughts what the problem may be

[Patrick]

Qubes vs persistence issue? Has to be done in TemplateVM.

sebuq:

I’m having difficulty following the thread.
My interpretation is: permanent solution to be Whonix 14. Temporary solution
disable check_systemd_clock
Is this a fair assessment?

Fair.

[sebuq]

I can confirm that changes were made to template whonix-gw. However, the
error persists

[0brand]

Hi sebuq

I can confirm that changes were made to template whonix-gw. However, the
error persists

There may be a typo in your 50_whonixcheck_user.conf file. Can you try to copying and pasting the following command and content. (works_for_me)

In whonix-gw konsole

sudo nano /etc/whonix.d/50_whonixcheck_user.conf

Add the following content

whonixcheck_skip_functions+=" check_systemd_clock "

[rehrar]

Add ‘.conf’ to the end of the file name. It worked for me. So it should be 50_whonixcheck_user.conf.

[mT8RQf]

the way I read this is: there is no solution, wait for whonix-14 … so in the meantime what? don’t use whonix ??

[mT8RQf]

1/2 the time whonixcheck on sys-whonix does this
ERROR: Tor Bootstrap Result:
Whonixcheck gave up waiting.
Tor Circuit: not established
Bootstrapping 100 % done. Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY=“Done”
Possible issues:

• Is the host’s internet connection working?
• Whonix-Gateway will need a few moments for bootstrapping the Tor network.
• Do you live in a censored area?
  Recommendations:

Shut down Whonix and try to get the Tor Browser Bundle from https://www.torproject.org working on your host. If you cannot get the Tor Browser Bundle to work, you will most certainly not get Whonix to work either.
The Tor Browser Bundle is great for testing if you live in a censored area. If you need bridges for the Tor Browser Bundle, you will need them for Whonix as well.
2)
Try again: dom0 → Start Menu → ServiceVM: sys-whonix → Whonix Check
or in Terminal: whonixcheck
or in Terminal with debugging: whonixcheck --debug --verbose
3)
Use arm, connection page two, to see if Tor is connected:
dom0 → Start Menu → ServiceVM: sys-whonix → Arm
or in Terminal: arm

[0brand]

the way I read this is: there is no solution, wait for whonix-14 … so in the meantime what? don’t use whonix ?

A temporary solution (to not receive this error at VM boot) would be to configure whonixcheck to skip check_systemd_clock

Whonix is still usable.

To configure whonixcheck to skip check_systemd_clock

1. In whonix-gw konsole

sudo nano /etc/whonix.d/50_whonixcheck_user.conf

2. Add the following content

whonixcheck_skip_functions+=" check_systemd_clock "

---

---

1/2 the time whonixcheck on sys-whonix does this

ERROR: Tor Bootstrap Result:

Whonixcheck gave up waiting.

This appears to be a separate issue. Could you please:

• use forum search engine to see if topic already exists
• if none exist, create a separate thread for this issue.

[mT8RQf]

afaik, the 2 may be connected, I am aware of your “solution” it pops up when the clock fails, so my point IS: it says “if you know what your doing”, and since I don’t really other than to throw those commands at it, then I probably shouldn’t … does that makes sense?

I’d rather not use whonix if a broken clock is going to defeat the purpose of using whonix …so would it ?

please don’t point me to the search bar , like superuser website did/does, I quickly stopped using that site, as it was so annoying thanks

[0brand]

@mT8RQf

and since I don’t really other than to throw those commands at it, then I probably shouldn’t … does that makes sense?

This issue should not stop you from using Whonix. If this was serious anonymity risk the Whonix devs would inform us.

As far as skipping check_systemd_clock That is up to you. As a rule of thumb, if you don’t know what you’re doing, you probably should not do it.

@mT8RQf

please don’t point me to the search bar , like superuser website did/does, I quickly stopped using that site, as it was so annoying thanks

Its good practice to get into the habit of doing;

https://www.whonix.org/wiki/Support#Brief_Recommendations

https://www.whonix.org/wiki/Forum_Best_Practices#Bumping_old_Threads_is_Okay

Related:

@entr0py

It’s the moderator’s job to keep threads on topic and sufficiently focused. And to lock them when they become unproductive and run in circles. I’ve always erred on the side of free speech but that comes at a cost of time and aggravation. And most importantly, as Patrick said, leads to a buildup of FUD when the community gets exhausted by intentional or misinformed trolling. Speaking for myself, I’ll be more assertive going forward along with:

• adding per-forum stickied posts describing what type of posts are appropriate; and what information needs to be provided to get help. also include links to troubleshooting, faq, how to ask questions, unsupported, free support principle, free speech, etc.

• marking posts with stackexchange-like tags when appropriate (too vague, off-topic, opinion-based, etc) and linking back to stickied posts

[mT8RQf]

ya, your template there in no way applies to what I said, but whatever man.

yes, I know its up to me, just forget the whole thing sigh

[0brand]

@mT8RQf

My intention was not to make thing difficult for you. By searching for threads that relate to your issue

• you may find a solution without having to wait for a reply
• all information about a specific topic is in 1 thread
  • keeps the forum nice and tidy
• keeps all information in a thread “On Topic”
  • off topic info/issues clutter the thread and make for confusion
• Whonix has limited resouces. If you can find an answer yourself, it allows the developers more time to focus in developing.

The " template" that i posted was to let you know what the job of the moderator is and what we are doing going forward. i.e. marking post off-topic, too-vague etc.

If you would like help with your second issue, please create a new thread. I already searched the forum for related threads.

[Patrick]

Every line of @0brand puts it well. Couldn’t answer any better.

Please proceed as @0brand suggests. @mT8RQf

//Whonix lead developer