Get this at my exit relay since yesterday:
# head /tmp/warn.log Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file. Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor
even with log level "debug" there seems to be no more information. Anything I should worry about?
Hi Toralf,
Thanks for reporting this issue.
On 24 Oct 2018, at 07:38, Toralf Förster toralf.foerster@gmx.de wrote:
Get this at my exit relay since yesterday:
# head /tmp/warn.log Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file. Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor
even with log level "debug" there seems to be no more information.
You should see an info-level message that starts:
"Unable to parse descriptor of type"
Can you send any messages like this to the list?
If those messages contain a filename, can you please send us a pastebin link to the contents of that file?
(If the messages just contain a hash, look for a file with a name that contains that hash in unparseable-descs in your data directory.)
I opened a ticket for this bug: https://trac.torproject.org/projects/tor/ticket/28223
T
Hi
Are the two warnings below of the same type for this issue?
Am 29.10.2018 um 07:03 schrieb teor:
Hi Toralf,
Thanks for reporting this issue.
On 24 Oct 2018, at 07:38, Toralf Förster toralf.foerster@gmx.de wrote:
Get this at my exit relay since yesterday:
# head /tmp/warn.log Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file. Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor
even with log level "debug" there seems to be no more information.
You should see an info-level message that starts:
"Unable to parse descriptor of type"
Can you send any messages like this to the list?
If those messages contain a filename, can you please send us a pastebin link to the contents of that file?
(If the messages just contain a hash, look for a file with a name that contains that hash in unparseable-descs in your data directory.)
I opened a ticket for this bug: https://trac.torproject.org/projects/tor/ticket/28223
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
Hi,
Thanks for reporting this bug.
On 30 Oct 2018, at 04:18, Felix zwiebel@quantentunnel.de wrote:
Are the two warnings below of the same type for this issue?
Not really: they're corrupt on disk, rather than from the network.
Am 29.10.2018 um 07:03 schrieb teor:
On 24 Oct 2018, at 07:38, Toralf Förster toralf.foerster@gmx.de wrote:
Get this at my exit relay since yesterday:
# head /tmp/warn.log Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file. Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor
even with log level "debug" there seems to be no more information.
...
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
This looks like file corruption, but we'd still like to see the corrupt file, because it might be tor's fault.
Oct 28 23:48:34.000 [warn] parse error: Malformed object: missing object end line Oct 28 23:48:34.000 [warn] Unparseable microdescriptor
This is probably also file corruption: tor won't download microdescs until it has a list of microdescs from a valid consensus.
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
Given the timing, this is probably also file corruption.
Please post any corrupt directory files that you have to: https://trac.torproject.org/projects/tor/ticket/28241
It would also be useful to have the logs from when tor last shut down. (Was it a clean shutdown?)
T
tor-relays@lists.torproject.org
-
Felix -
teor -
Toralf Förster