Your message dated Sun, 6 May 2007 15:13:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line tor: confused by clock skew, doesn't start
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: tor
Version: 0.1.1.12-alpha-1
Severity: normal
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 :)
the solution of course is to manually remove/update the date from state
file
thanks,
filippo
-- System Information:
Debian Release: testing/unstable
APT prefers experimental
APT policy: (650, 'experimental'), (600, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages tor depends on:
ii adduser 3.84 Add and remove users and groups
ii libc6 2.3.6-1 GNU C Library: Shared libraries an
ii libevent1 1.1a-1 An asynchronous event notification
ii libssl0.9.8 0.9.8a-7 SSL shared libraries
ii tsocks 1.8beta5-2 transparent network access through
ii zlib1g 1:1.2.3-9 compression library - runtime
Versions of packages tor recommends:
ii privoxy 3.0.3-6 Privacy enhancing HTTP Proxy
ii socat 1.4.3.0-1 multipurpose relay for bidirection
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.1.2.13-1
On Fri, 24 Feb 2006, Filippo Giunchedi wrote:
> 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.
Parts of this issue were already addressed in later 0.1.1.x releases.
Now with 0.1.2.x this should be completely resolved. 0.1.2.13 has been
uploaded to unstable a few days ago. Please let us know if you still
encounter this problem.
Peter
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--- End Message ---
