Logs warn me about unparseable microdescriptors and internal NUL characters

[Not_Ambrose]

Hi all.
Recently my relay logs have been showing odd issues. It’s warning me that there’s a issue with about unparseable microdescriptors and internal NUL characters, which I have no idea why. I’ve recently switched from the Debian LTS release of Tor to using Debian backports, but that shouldn’t be an issue.

Tor[841]: Bug: /usr/bin/tor(tor_main+0x5c) [0x5559f8715c] (on Tor 0.4.8.9 )
Tor[841]: Bug: /usr/bin/tor(main+0x20) [0x5559f86c20] (on Tor 0.4.8.9 )
Tor[841]: Bug: /lib/aarch64-linux-gnu/libc.so.6(+0x27780) [0x7f9a477780] (on Tor 0.4.8.9 )
Tor [841]: Bug: /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98) [0x7f9a477858] (on Tor 0.4.8.9 )
Tor[841]: Bug: /usr/bin/tor(_start+0x30) [0x5559f86cb0] (on Tor 0.4.8.9 )
Tor[841]: warn_if_nul_found(): Bug: Found unexpected NUL while reading microdesc journal, offset 0at position 210763>
Tor[841]: warn_if_nul_found(): Bug: surrounding string: 4746565065796450424A6C654C34380A0000000000000000000000>
Tor[841]: parse error: internal NUL character.
Tor[841]: Unparseable microdescriptor found in journal
Tor[841]: parse error: internal NUL character.
Tor[841]: Unparseable microdescriptor found in journal
Tor[841]: parse error: internal NUL character.
Tor[841]: Unparseable microdescriptor found in journal

[Vort]

Did your computer turned off because of power outage recently?
It looks like some files in Tor data directory are damaged.
But it is not a problem, only key files are really important.
So you should be able to delete corrupted file and Tor will redownload it.
Probably cached-microdescs is having problems.
Also it is better to make backup of data directory before deleting problematic file.