Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#1064 closed defect (fixed)

warnings in log related to consensus problems

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

Description (last modified by nickm)

Yesterday I had this in my logs:

Aug 19 06:25:08.854 [notice] Tor 0.2.1.19 opening new log file.
Aug 19 11:11:24.080 [warn] couldn't find start of hashed material "network-status-version"
Aug 19 11:11:24.080 [warn] Unable to compute digest of network-status
Aug 19 11:11:24.080 [warn] Unable to parse networkstatus consensus
Aug 19 11:11:24.080 [warn] Unable to load consensus directory downloaded from server '80.190.246.100:80'. I'll try again soon.
Aug 19 14:15:21.864 [warn] 1 unknown, 0 missing key, 3 good, 0 bad, 2 no signature, 4 required
Aug 19 14:15:21.864 [warn] Not enough good signatures on networkstatus consensus
Aug 19 14:15:21.866 [warn] Unable to load consensus directory downloaded from server '128.31.0.34:9031'. I'll try again soon.
Aug 19 14:25:30.496 [warn] 1 unknown, 0 missing key, 3 good, 0 bad, 2 no signature, 4 required
Aug 19 14:25:30.496 [warn] Not enough good signatures on networkstatus consensus
Aug 19 14:25:30.498 [warn] Unable to load consensus directory downloaded from server '86.59.21.38:80'. I'll try again soon.
Aug 19 14:56:01.852 [warn] 1 unknown, 0 missing key, 3 good, 0 bad, 2 no signature, 4 required
Aug 19 14:56:01.852 [warn] Not enough good signatures on networkstatus consensus
Aug 19 14:56:01.854 [warn] Unable to load consensus directory downloaded from server '216.224.124.114:9030'. I'll try again soon.
Aug 20 06:25:09.481 [notice] Received reload signal (hup). Reloading config and resetting internal state.

No idea where these warnings would come from. Does anyone with an authority have any useful logs?

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (8)

comment:1 Changed 10 years ago by karsten

Looks like a usual intermittent voting problem.

Aug 19 13:50:01.943 [notice] Time to vote.
Aug 19 13:50:02.462 [notice] Choosing valid-after time in vote as 2009-08-19 12:00:00: consensus_set=1, last_interval=3600
Aug 19 13:50:05.388 [notice] Vote posted.
Aug 19 13:50:08.443 [warn] We just marked ourself as down. Are your external addresses reachable?
Aug 19 13:52:31.315 [notice] Time to fetch any votes that we're missing.
Aug 19 13:52:31.315 [notice] We're missing votes from 3 authorities. Asking every other authority for a copy.
Aug 19 13:55:01.262 [notice] Time to compute a consensus.
Aug 19 13:55:04.605 [notice] Consensus computed; uploading signature(s)
Aug 19 13:55:04.605 [notice] Signature(s) posted.
Aug 19 13:57:31.515 [notice] Time to fetch any signatures that we're missing.
Aug 19 13:57:41.593 [notice] Got a signature from 128.31.0.34. Adding it to the pending consensus.
Aug 19 13:57:41.593 [warn] Problem adding detached signatures from 128.31.0.34:9031: Digest mismatch when adding detached signatures to consensus
Aug 19 13:58:13.602 [warn] We just marked ourself as down. Are your external addresses reachable?
Aug 19 13:58:16.798 [notice] Got a signature from 86.59.21.38. Adding it to the pending consensus.
Aug 19 13:58:16.798 [warn] Problem adding detached signatures from 86.59.21.38:80: Digest mismatch when adding detached signatures to consensus
Aug 19 14:00:01.282 [notice] Time to publish the consensus and discard old votes
Aug 19 14:00:01.282 [warn] 0 unknown, 0 missing key, 1 good, 0 bad, 6 no signature, 4 required
Aug 19 14:00:01.282 [warn] Not enough info to publish pending consensus
Aug 19 14:00:01.439 [notice] Choosing expected valid-after time as 2009-08-19 13:00:00: consensus_set=1, interval=3600

Two ideas to fix this are 1) upgrading the remaining authority to the new list of 7 authorities and 2) reducing some load on gabelmoo to make sure that the "We just marked ourself as down" messages go away. "Putting it on the list..."

comment:2 Changed 10 years ago by arma

From moria1:

Aug 19 06:55:01.927 [notice] Time to compute a consensus.
Aug 19 06:55:02.585 [warn] Parse error: missing consensus-digest element.
Aug 19 06:55:02.585 [warn] Error tokenizing detached networkstatus signatures
Aug 19 06:55:02.585 [warn] Could not add queued signature to new consensus: Coul
dn't parse detached signatures.

...

Aug 19 07:52:52.921 [warn] couldn't find start of hashed material "network-statu
s-version"
Aug 19 07:52:52.921 [warn] Unable to compute digest of network-status
Aug 19 07:52:52.921 [warn] Couldn't parse vote: length was 497
Aug 19 07:52:52.921 [warn] Error adding retrieved vote: Unable to parse vote

comment:3 Changed 10 years ago by arma

Karsten: do you have any more details on the "we just marked ourself as down"
line on gabelmoo?

It looks like gabelmoo voted by itself on the consensus that it created. I
wonder why that could be.

comment:4 Changed 10 years ago by arma

Another thing here that might count as a bug: I think an authority that fails
to generate a consensus won't try to fetch one from any other authorities for
that interval. It just sits about being wrong.

At least, the confirmed version of my bug is that if I kill moria1 at 56 after
an hour, it will never generate a consensus. When I start it at 2 after the hour,
it doesn't try to fetch one from anybody else.

comment:5 Changed 10 years ago by nickm

Can we close this out (since the original problem is fixed) and open new tickets for the "usual intermittent voting problems" and the "try to fetch a consensus if we couldn't make one ourself" problem?

comment:6 Changed 10 years ago by nickm

The "Try to fetch a consensus if we couldn't make it ourself" problem apparently has its own ticket already, as bug #1300.

Is there a remaining bug here?

comment:7 Changed 9 years ago by nickm

Description: modified (diff)
Resolution: Nonefixed
Status: newclosed

I think this bug is partly fixed, and partly duplicate with others, including #1300. Closing

comment:8 Changed 7 years ago by nickm

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