GitLab

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.