signature download for consensuses fail.
In order to ensure that each directory authority has all the signatures from other authorities before they publish a consensus an authority X goes out and fetches the list of all detached sigs from every other authority if X is missing sigs from at least one.
However, this doesn't work.
With some additional/louder logging I can see this at tor26: Jan 24 15:57:31.143 [notice] Time to fetch any signatures that we're missing. Jan 24 15:57:31.143 [notice] Fetching missing votes/signatures from all authorities (purpose 13) Jan 24 15:57:31.143 [notice] Sending command to fetch detached sigs. base.state is 1 Jan 24 15:57:31.143 [notice] Asking 128.31.0.34:9031 for /tor/status-vote/next/consensus-signatures.z Jan 24 15:57:31.143 [notice] Sending command to fetch detached sigs. base.state is 1 Jan 24 15:57:31.143 [notice] Asking 140.247.60.64 for /tor/status-vote/next/consensus-signatures.z Jan 24 15:57:31.143 [notice] Sending command to fetch detached sigs. base.state is 1 Jan 24 15:57:31.143 [notice] Asking 216.224.124.114:9030 for /tor/status-vote/next/consensus-signatures.z Jan 24 15:57:31.143 [notice] Sending command to fetch detached sigs. base.state is 1 Jan 24 15:57:31.143 [notice] Asking 88.198.7.215 for /tor/status-vote/next/consensus-signatures.z Jan 24 15:57:31.143 [notice] Sending command to fetch detached sigs. base.state is 1 Jan 24 15:57:31.143 [notice] Asking 213.73.91.31 for /tor/status-vote/next/consensus-signatures.z Jan 24 15:57:31.165 [notice] Dir connection to router 88.198.7.215:80 established. Jan 24 15:57:31.165 [notice] client finished sending command (88.198.7.215). Jan 24 15:57:31.174 [notice] Dir connection to router 213.73.91.31:80 established. Jan 24 15:57:31.174 [notice] client finished sending command (213.73.91.31). Jan 24 15:57:31.187 [notice] 'fetch' response not all here, but we're at eof. Closing. Jan 24 15:57:31.187 [notice] conn to 88.198.7.215 reached eof, retval is -1 Jan 24 15:57:31.187 [notice] Giving up downloading detached signatures from '88.198.7.215' Jan 24 15:57:31.206 [notice] 'fetch' response not all here, but we're at eof. Closing. Jan 24 15:57:31.206 [notice] conn to 213.73.91.31 reached eof, retval is -1 Jan 24 15:57:31.206 [notice] Giving up downloading detached signatures from '213.73.91.31' Jan 24 15:57:31.247 [notice] Dir connection to router 128.31.0.34:9031 established. Jan 24 15:57:31.247 [notice] client finished sending command (128.31.0.34). Jan 24 15:57:31.322 [notice] Dir connection to router 216.224.124.114:9030 established. Jan 24 15:57:31.322 [notice] client finished sending command (216.224.124.114). Jan 24 15:57:31.352 [notice] 'fetch' response not all here, but we're at eof. Closing. Jan 24 15:57:31.352 [notice] conn to 128.31.0.34 reached eof, retval is -1 Jan 24 15:57:31.352 [notice] Giving up downloading detached signatures from '128.31.0.34' Jan 24 15:57:31.521 [notice] 'fetch' response not all here, but we're at eof. Closing. Jan 24 15:57:31.521 [notice] conn to 216.224.124.114 reached eof, retval is -1 Jan 24 15:57:31.521 [notice] Giving up downloading detached signatures from '216.224.124.114' Jan 24 16:00:01.895 [notice] Time to publish the consensus and discard old votes
Note the "'fetch' response not all here, but we're at eof. Closing." log entry.
The problem appears to be that a) we send bogus Content-Length headers for compressed stuff like next/conensus.z and next/consensus-signatures.z, and b) we declare a download failed when we don't have as many bytes as the Content-Length says there should be.
Point (a) also confuses the hell out of wget.
[Automatically added by flyspray2trac: Operating System: All]