hs_metrics_service_init: Non-fatal assertion when Tor reloads
Summary
I noticed that every night when my logs get rotated, a non-fatal assertion appears at the beginning the log.
I can manually trigger this issue but reloading Tor by hand (sudo systemctl reload tor).
What is the current bug behavior?
This bug message just appears, but I could not find any impact yet.
What is the expected behavior?
This message shouldn't appear, right?
Environment
- Tor version 0.4.5.6 (
0.4.5.6-1~d10.buster+1) - Debian 10
- Installed using apt (via the official Tor repository)
- This Tor instance is a bridge relay
- This Tor instance exposes a v3 HS (Bitcoin Core 0.21.0)
Relevant logs and/or screenshots
Mar 05 00:00:16.000 [notice] Tor 0.4.5.6 opening new log file.
Mar 05 00:00:16.000 [warn] tor_bug_occurred_(): Bug: ../src/feature/hs/hs_metrics.c:154: hs_metrics_service_init: Non-fatal assertion !(service->metrics.store) failed. (on Tor 0.4.5.6 )
Mar 05 00:00:16.000 [warn] Bug: Tor 0.4.5.6: Non-fatal assertion !(service->metrics.store) failed in hs_metrics_service_init at ../src/feature/hs/hs_metrics.c:154. Stack trace: (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(log_backtrace_impl+0x56) [0x56393b37be56] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0x16c) [0x56393b386fcc] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(+0x20302b) [0x56393b48f02b] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(hs_service_load_all_keys+0xd8b) [0x56393b49166b] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(set_options+0xd36) [0x56393b4103e6] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(+0x184f2f) [0x56393b410f2f] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(options_init_from_string+0x14d) [0x56393b4111bd] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(options_init_from_torrc+0x376) [0x56393b4117e6] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(+0x649b9) [0x56393b2f09b9] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x22a6c) [0x7f31454eda6c] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7) [0x7f31454ee537] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(do_main_loop+0xff) [0x56393b2f809f] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(tor_run_main+0x885) [0x56393b2f23f5] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(tor_main+0x3a) [0x56393b2f02ea] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(main+0x19) [0x56393b2efea9] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f3144dc1bbb] (on Tor 0.4.5.6 )
Mar 05 00:00:17.000 [warn] Bug: /usr/bin/tor(_start+0x2a) [0x56393b2efefa] (on Tor 0.4.5.6 )Let me know, if I can help you with any more information