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]
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?
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
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?
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
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
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.