Opened 10 years ago

Last modified 7 years ago

#1051 closed defect (Duplicate)

couldn't find start of hashed material "network-status-version"

Reported by: stars Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.1.19
Severity: Keywords:
Cc: stars, karsten, Sebastian, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

hello,

i think i have found a new bug on 2.17 rc on ubuntu jaunty 64 x86 64 , libevent 1.3e

août 06 11:16:43.602 [Avertissement] couldn't find start of hashed material "network-status-version"
août 06 11:16:43.680 [Avertissement] Unable to compute digest of network-status
août 06 11:16:43.680 [Avertissement] Unable to parse networkstatus consensus
août 06 11:16:43.680 [Avertissement] Unable to load consensus directory downloaded from server '80.190.246.100:80'. I'll try again soon.
août 06 11:55:23.720 [Avertissement] eventdns: All nameservers have failed
août 06 11:55:26.783 [Signalement] eventdns: Nameserver 192.168.2.1 is back up

my best

SwissTorExit / John

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (13)

comment:1 Changed 10 years ago by karsten

Interesting. I guess this behavior is not reproducible, is it? It would be
good to know the document that Tor fails to parse. Should we write the
first 500 (or 100) chars to the log statement?

comment:2 Changed 10 years ago by stars

new errors on matsre commit: 2dea20c7e19f5346a376a3abd8f9d670e7186615

août 14 17:12:35.069 [Avertissement] couldn't find start of hashed material "network-status-version"
août 14 17:12:35.069 [Avertissement] Unable to compute digest of network-status
août 14 17:12:35.069 [Avertissement] Unable to parse networkstatus consensus
août 14 17:12:35.069 [Avertissement] Unable to load consensus directory downloaded from server '80.190.246.100:80'. I'll try again soon.

comment:3 Changed 10 years ago by karsten

How about putting in the patch in fix-1051-maint-0.2.1 in my public branch
into maint-0.2.1 and master? It prints the first 100 chars of the
networkstatus Tor cannot parse. This might help us understand the issue.

comment:4 Changed 10 years ago by nickm

I'd actually prefer something that would dump the whole unparseable thing to a file.
For the general case: If there are problems, they are not necessarily going to be in
the first N characters.

comment:5 Changed 10 years ago by karsten

See new branch fix-1051-file-maint-0.2.1 in my public repo.

comment:6 Changed 10 years ago by stars

updated from your repo, thanks.

comment:7 Changed 10 years ago by nickm

Karsten: that looks fine for a special-purpose debugging patch, but I'd want a few tweaks before we can put it in
a generic Tor distribution:

1) debug/ should be a directory.
2) There should be some information stored in the filename or the file about what kind of data it was expected

to contain and whom it was downloaded from.

3) There needs to be some facility to prevent the debug/ directory from growing infinitely large.

comment:8 Changed 10 years ago by stars

hello,

Same error again and no more infos...

août 19 10:28:40.830 [Warning] couldn't find start of hashed material "network-status-version"
août 19 10:28:40.830 [Warning] Unable to compute digest of network-status
août 19 10:28:40.831 [Warning] Unable to parse networkstatus consensus
août 19 10:28:40.831 [Warning] Unable to load consensus directory downloaded from server '80.190.246.100:80'. I'll try again soon.

my best

commit: 2dea20c7e19f5346a376a3abd8f9d670e7186615

comment:9 Changed 10 years ago by Sebastian

I just received the same thing on fluxe3 (running 0.2.1.19 on Debian Lenny).

I have a copy of the data directory from 8 minutes later, if that would be of any help.

comment:10 Changed 10 years ago by stars

well i have a new error but with only:

août 21 10:13:25.584 [Warning] Received http status code 404 ("Not found") from server '213.73.91.31:80' while fetching consensus directory.

master patched "fix-1051" commit: commit d584a65c798b3a80a38d819b032a74ea9ce85691

comment:11 Changed 10 years ago by stars

sorry, i have delete the headers of my branch and have not see it was only on master branch, i restart on: commit 36420ccd78a1af52e80612c9846016207123d6af

comment:12 Changed 10 years ago by karsten

flyspray2trac: bug closed.
Very likely a duplicate of 1009.

comment:13 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.