Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #28241
Closed
Open
Issue created Oct 30, 2018 by teor@teor

Corrupt cached consensus and microdescs

A relay operator reported file corruption on disk:

Non-exit
Oct 28 23:48:32.587 [notice] Tor 0.3.5.3-alpha running on FreeBSD with
Libevent 2.1.8-stable, OpenSSL LibreSSL 2.7.4, Zlib 1.2.11, Liblzma
5.2.3, and Libzstd 1.3.5.
...
Oct 28 23:48:33.000 [notice] Bootstrapped 0%: Starting
Oct 28 23:48:34.000 [warn] couldn't find start of hashed material
"network-status-version"
Oct 28 23:48:34.000 [warn] Unable to compute digest of network-status
Oct 28 23:48:34.000 [warn] Unable to parse networkstatus consensus
Oct 28 23:48:34.000 [warn] Couldn't load consensus microdesc
networkstatus from cache
Oct 28 23:48:34.000 [warn] parse error: Malformed object: missing object
end line
Oct 28 23:48:34.000 [warn] Unparseable microdescriptor

Bridge:
Oct 28 14:35:17.667 [notice] Tor 0.3.3.9 (git-45028085ea188baf) running
on FreeBSD with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.7.4, Zlib
1.2.11, Liblzma 5.2.3, and Libzstd 1.3.5.
...
Oct 28 14:35:53.000 [notice] Bootstrapped 0%: Starting
Oct 28 14:35:55.000 [warn] parse error: Annotations mixed with keywords
Oct 28 14:35:55.000 [warn] Unparseable microdescriptor

I replied:

This looks like file corruption, but we'd still like to see the corrupt file, because it might be tor's fault.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking