Re: [tor-relays] exit relay "internal error"

2019-06-19 Thread dns1983
Thank you very much for your support.

I think i'll wait a few days to find a solution, otherwise I'll ask for a reset 
of my VM.

Cheers
Gigi



Il 18 giugno 2019 17:26:11 CEST, David Goulet  ha 
scritto:
>On 18 Jun (12:51:45), dns1...@riseup.net wrote:
>> Hello,
>
>Hi!
>
>> 
>> I have an exit relay on a debian remote vm. Yesterday, after I
>installed the
>> last linux security update, I rebooted It, and than I had a problem
>with
>> additional IPs, that were no more being assigned. In order to
>understand if
>> it were a problem caused by the last upgrade I restored a previous
>backup,
>> that I made on May with tar.
>> 
>> I didn't solved the problem restoring the backup, so I opened a
>ticket with
>> my provider. Now they have fixed this issue, but my tor instance is
>going in
>> loop. The log says:
>
>Thanks for the report!
>
>First time we see this! We've opened
>https://trac.torproject.org/projects/tor/ticket/30916 about this.
>
>We hope to get this fixed soon.
>
>Huge thanks for taking the time to report this! :)
>
>Cheers!
>David
>
>> 
>> ...
>> 
>> Jun 18 13:33:31.000 [notice] Bootstrapped 0%: Starting
>> Jun 18 13:33:32.000 [notice] Starting with guard context "default"
>> 
>>  T=
>1560854012
>> INTERNAL ERROR: Raw assertion failed at
>../src/lib/ctime/di_ops.c:179: !
>>
>old_val/usr/bin/tor(dump_stack_symbols_to_error_fds+0x33)[0x55a17b410943]
>> /usr/bin/tor(tor_raw_assertion_failed_msg_+0x86)[0x55a17b410fd6]
>> /usr/bin/tor(dimap_add_entry+0xa0)[0x55a17b411ba0]
>> /usr/bin/tor(construct_ntor_key_map+0x69)[0x55a17b357969]
>> /usr/bin/tor(server_onion_keys_new+0x4d)[0x55a17b39f4dd]
>> /usr/bin/tor(+0x66e27)[0x55a17b287e27]
>> /usr/bin/tor(threadpool_new+0x18b)[0x55a17b3b3f0b]
>> /usr/bin/tor(cpu_init+0x9d)[0x55a17b28828d]
>> /usr/bin/tor(run_tor_main_loop+0x136)[0x55a17b27a496]
>> /usr/bin/tor(tor_run_main+0x1215)[0x55a17b27b935]
>> /usr/bin/tor(tor_main+0x3a)[0x55a17b278a8a]
>> /usr/bin/tor(main+0x19)[0x55a17b278609]
>>
>/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ffb901ba2e1]
>> /usr/bin/tor(_start+0x2a)[0x55a17b27865a]
>> Jun 18 13:33:33.000 [notice] Tor 0.3.5.8 opening log file.
>> 
>> ...
>> 
>> What could be the problem?
>> 
>> thanks
>> 
>> Gigi
>> 
>> 
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>-- 
>iWmpKF5Ma8MfvMetoDN1BUw5ttwe8pkvgxAvuLMu008=
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] exit relay "internal error"

2019-06-18 Thread David Goulet
On 18 Jun (12:51:45), dns1...@riseup.net wrote:
> Hello,

Hi!

> 
> I have an exit relay on a debian remote vm. Yesterday, after I installed the
> last linux security update, I rebooted It, and than I had a problem with
> additional IPs, that were no more being assigned. In order to understand if
> it were a problem caused by the last upgrade I restored a previous backup,
> that I made on May with tar.
> 
> I didn't solved the problem restoring the backup, so I opened a ticket with
> my provider. Now they have fixed this issue, but my tor instance is going in
> loop. The log says:

Thanks for the report!

First time we see this! We've opened
https://trac.torproject.org/projects/tor/ticket/30916 about this.

We hope to get this fixed soon.

Huge thanks for taking the time to report this! :)

Cheers!
David

> 
> ...
> 
> Jun 18 13:33:31.000 [notice] Bootstrapped 0%: Starting
> Jun 18 13:33:32.000 [notice] Starting with guard context "default"
> 
>  T= 1560854012
> INTERNAL ERROR: Raw assertion failed at ../src/lib/ctime/di_ops.c:179: !
> old_val/usr/bin/tor(dump_stack_symbols_to_error_fds+0x33)[0x55a17b410943]
> /usr/bin/tor(tor_raw_assertion_failed_msg_+0x86)[0x55a17b410fd6]
> /usr/bin/tor(dimap_add_entry+0xa0)[0x55a17b411ba0]
> /usr/bin/tor(construct_ntor_key_map+0x69)[0x55a17b357969]
> /usr/bin/tor(server_onion_keys_new+0x4d)[0x55a17b39f4dd]
> /usr/bin/tor(+0x66e27)[0x55a17b287e27]
> /usr/bin/tor(threadpool_new+0x18b)[0x55a17b3b3f0b]
> /usr/bin/tor(cpu_init+0x9d)[0x55a17b28828d]
> /usr/bin/tor(run_tor_main_loop+0x136)[0x55a17b27a496]
> /usr/bin/tor(tor_run_main+0x1215)[0x55a17b27b935]
> /usr/bin/tor(tor_main+0x3a)[0x55a17b278a8a]
> /usr/bin/tor(main+0x19)[0x55a17b278609]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ffb901ba2e1]
> /usr/bin/tor(_start+0x2a)[0x55a17b27865a]
> Jun 18 13:33:33.000 [notice] Tor 0.3.5.8 opening log file.
> 
> ...
> 
> What could be the problem?
> 
> thanks
> 
> Gigi
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-- 
iWmpKF5Ma8MfvMetoDN1BUw5ttwe8pkvgxAvuLMu008=


signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays