Information
ID: 482
PHID: PHID-TASK-kd2qj7lbdoenyemmo6t4
Author: Patrick
Status at Migration Time: resolved
Priority at Migration Time: Normal
Description
/var/run/tor/log might include.
Mar 20 01:01:02.000 [warn] Our clock is 1 days, 12 hours, 58 minutes behind the time published in the consensus network status document (2016-03-21 14:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
Probably the most common cause for connection issues. Would have been useful for the following two tickets.
- VMs with Whonix-Tor networking timeout and do not recover · Issue #1779 · QubesOS/qubes-issues · GitHub
- sys-whonix doesn't connect to Tor after system suspend · Issue #1764 · QubesOS/qubes-issues · GitHub
Until sdwdate gets this feature (T151), a simple #whonixcheck test would be useful. Since Tor provides no great interface for this… anondate will be required for that purpose.
Barely related:
T480
Comments
Patrick
2016-03-22 09:20:16 UTC
Patrick
2016-03-22 10:39:32 UTC