Opened 6 weeks ago

Last modified 8 days ago

#31364 new defect

tor_bug_occurred_(): Bug: ../src/feature/nodelist/microdesc.c:494: warn_if_nul_found: Non-fatal assertion !(nul_found) failed. (on Tor 0.4.0.5 )

Reported by: computer_freak Owned by:
Priority: Medium Milestone: Tor: 0.4.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: microdesc assert 042-should
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Aug 07 11:00:15.000 [notice] Tor 0.4.0.5 opening log file.
Aug 07 11:00:15.393 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 101000af: OpenSSL 1.1.0j  20 Nov 2018; running with 101000bf: OpenSSL 1.1.0k  28 May 2019).
Aug 07 11:00:15.395 [notice] Can't get entropy from getrandom(). You are running a version of Tor built to support getrandom(), but the kernel doesn't implement this function--probably because it is too old? Trying fallback method instead.
Aug 07 11:00:15.398 [notice] Tor 0.4.0.5 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0k, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
Aug 07 11:00:15.398 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download
Aug 07 11:00:15.398 [warn] Tor was compiled with zstd 1.1.2, but is running with zstd 1.3.8. For safety, we'll avoid using advanced zstd functionality.
Aug 07 11:00:15.399 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Aug 07 11:00:15.399 [notice] Read configuration file "/etc/tor/torrc".
Aug 07 11:00:15.407 [notice] Based on detected system memory, MaxMemInQueues is set to 384 MB. You can override this by setting MaxMemInQueues by hand.
Aug 07 11:00:15.410 [notice] I think we have 40 CPUS, but only 1 of them are available. Telling Tor to only use 1. You can override this with the NumCPUs option
Aug 07 11:00:15.411 [notice] Opening OR listener on 0.0.0.0:443
Aug 07 11:00:15.411 [notice] Opened OR listener on 0.0.0.0:443
Aug 07 11:00:15.411 [notice] Opening OR listener on [***]:443
Aug 07 11:00:15.412 [notice] Opened OR listener on [***]:443
Aug 07 11:00:15.412 [notice] Opening Directory listener on 0.0.0.0:9030

Aug 07 11:00:15.412 [notice] Opened Directory listener on 0.0.0.0:9030
Aug 07 11:00:15.000 [notice] Not disabling debugger attaching for unprivileged users.
Aug 07 11:00:15.000 [warn] Found empty file "1037" in consensus cache; removing it.
Aug 07 11:00:15.000 [warn] Unable to map file (null) from consensus cache: No such file or directory
Aug 07 11:00:16.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Aug 07 11:00:17.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Aug 07 11:00:17.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Aug 07 11:00:17.000 [notice] Your Tor server's identity key fingerprint is '***'
Aug 07 11:00:17.000 [notice] Bootstrapped 0% (starting): Starting
Aug 07 11:00:17.000 [warn] tor_bug_occurred_(): Bug: ../src/feature/nodelist/microdesc.c:494: warn_if_nul_found: Non-fatal assertion !(nul_found) failed. (on Tor 0.4.0.5)
Aug 07 11:00:17.000 [warn] Bug: Non-fatal assertion !(nul_found) failed in warn_if_nul_found at ../src/feature/nodelist/microdesc.c:494. Stack trace: (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(log_backtrace_impl+0x47) [0x55e3b15b98e7] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(tor_bug_occurred_+0xc0) [0x55e3b15b4db0] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(+0x11e43f) [0x55e3b14d643f] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(microdesc_cache_reload+0xce) [0x55e3b14d89ee] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(get_microdesc_cache+0x48) [0x55e3b14d8ad8] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(nodelist_set_consensus+0x3fd) [0x55e3b14e4e3d] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(networkstatus_set_current_consensus+0x927) [0x55e3b14dd9d7] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(+0x125dfe) [0x55e3b14dddfe] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(router_reload_consensus_networkstatus+0x45) [0x55e3b14ddeb5] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(run_tor_main_loop+0xec) [0x55e3b141564c] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(tor_run_main+0x11e5) [0x55e3b1416b05] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(tor_main+0x3a) [0x55e3b1413c8a] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(main+0x19) [0x55e3b1413809] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f10090512e1] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] Bug:     /usr/bin/tor(_start+0x2a) [0x55e3b141385a] (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] warn_if_nul_found(): Bug: Found unexpected NUL while reading microdesc journal, offset 0at position 295945/331210. (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] warn_if_nul_found(): Bug:       surrounding string: 595630544A522B5159546D49496A300A00000000000000000000000000000000 (on Tor 0.4.0.5 )
Aug 07 11:00:17.000 [warn] parse error: internal NUL character.
Aug 07 11:00:17.000 [warn] Unparseable microdescriptor found in journal
Aug 07 11:00:27.000 [notice] Starting with guard context "default"
Aug 07 11:00:27.000 [notice] Signaled readiness to systemd
Aug 07 11:00:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay

Apart from that error message Tor seems to work fine.

The relay was running on a VM and when i saw that error the whole VM behaved strange. I think the ISP corrupted something so maybe that error isnt Tor's fault.

Child Tickets

Change History (5)

comment:1 Changed 6 weeks ago by nickm

Milestone: Tor: 0.4.2.x-final

comment:2 Changed 5 weeks ago by dgoulet

Component: Core TorCore Tor/Tor
Keywords: microdesc assert added

comment:3 Changed 13 days ago by nickm

Keywords: crash added

comment:4 Changed 12 days ago by nickm

Keywords: crash removed

comment:5 Changed 8 days ago by nickm

Keywords: 042-should added
Note: See TracTickets for help on using tickets.