confused by clock skew, doesn't start [debian #354259]
Hi!
first thanks for your effort in tor! It's great!
from time to time I have my hw clock resetted back to 1904 if I leave my
laptop without battery, tor gets confused and won't start:Jan 01 01:24:26.452 [notice] Tor 0.1.1.12-alpha opening log file.
[...working normally here...]
Jan 01 01:24:28.608 [warn] router_set_networkstatus(): Network status
from directory server "moria1" at 18.244.0
.188:9031 was published in the future (2006-02-24 12:05:52 GMT).
Somebody is skewed here: check your clock. Not
caching.but warping the clock to the future isn't liked by tor who eats almost
all the cpu. Then I try to restart it:Feb 24 14:41:09.619 [notice] Tor 0.1.1.12-alpha opening log file.
Feb 24 14:41:09.619 [warn] parse_iso_time(): Got invalid ISO time
"1904-01-01 00:39:26". (Before 1970)
Feb 24 14:41:09.620 [warn] Invalid time '1904-01-01 00:39:26' for
keyword 'BWHistoryReadEnds'
Feb 24 14:41:09.620 [err] set_options(): Acting on config options left
us in a broken state. Dying.that is, it stores dates it can't parse back :)
Ooops, I'm sorry I have missed this bug report. I'm forwarding it to the developers for their attention.
tor-bugs, please CC 354259@bugs.debian.org on future mails about that bug.
[Automatically added by flyspray2trac: Operating System: All]