Hi,
Thanks for reporting this bug.
> On 30 Oct 2018, at 04:18, Felix 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ö
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 wrote:
>>
>> Get this at my exit relay since yesterday:
>>
>> # head /tmp/warn.log
>> Oct 23 23:3
Hi Toralf,
Thanks for reporting this issue.
> On 24 Oct 2018, at 07:38, Toralf Förster 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 ch
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: intern
