Re: [tor-relays] scale_active_circuits assertion fail

On 2018-02-20 22:37:42, "teor" wrote: Please open a ticket with the full stack trace, and your OS. I opened a ticket: https://trac.torproject.org/projects/tor/ticket/25316#ticket Please let me know if there is anything more you need to know ___ tor

Re: [tor-relays] dns name

> On 21 Feb 2018, at 07:05, TorGate wrote: > > Hi onion friends :-) > i have 2 relays, configured with ipv4 adresses. > I have write to my isp and asked: can you change the ripe data ? > isp: no > my: ok :-( , i can also not change the reverse dnsname > > 1. So the question: is that a god way

Re: [tor-relays] scale_active_circuits assertion fail

> On 21 Feb 2018, at 03:13, Logforme wrote: > > My relay (855BC2DABE24C861CD887DB9B2E950424B49FC34) just crashed with the > following error: > Feb 20 14:33:40.000 [err] tor_assertion_failed_(): Bug: > ../src/or/circuitmux_ewma.c:711: scale_active_circuits: Assertion > e->last_adjusted_tick ==

[tor-relays] dns name

Hi onion friends :-) i have 2 relays, configured with ipv4 adresses. I have write to my isp and asked: can you change the ripe data ? isp: no my: ok :-( , i can also not change the reverse dnsname 1. So the question: is that a god way to change the config from IP-adress to dnsname in the torrc. 2

Re: [tor-relays] Publishing bridge contact information

On 2018-02-07 17:45, Karsten Loesing wrote: > We're now considering to drop one step in the sanitizing step, which is > to remove contact information. The result would be that we'd keep > contact information in sanitized descriptors in the exact same way as > the bridge operator put it into their t

[tor-relays] scale_active_circuits assertion fail

My relay (855BC2DABE24C861CD887DB9B2E950424B49FC34) just crashed with the following error: Feb 20 14:33:40.000 [err] tor_assertion_failed_(): Bug: ../src/or/circuitmux_ewma.c:711: scale_active_circuits: Assertion e->last_adjusted_tick == pol->active_circuit_pqueue_last_recalibrated failed; abor

Re: [tor-relays] Not in the cached consensus

> On 20 Feb 2018, at 23:02, "ka...@ono.com" wrote: > > My LorneMalvo relay not in the cached consensus. Flags ok: running, v2dir, > valid according to consensus-health. Only 4 of 9 directory authorities see your relay as Running: https://consensus-health.torproject.org/consensus-health-2018-02

[tor-relays] Not in the cached consensus

My LorneMalvo relay not in the cached consensus. Flags ok: running, v2dir, valid according to consensus-health. No estimate of my bandwidth never. Why? Best regards P.S.: Sorry for my english ___ tor-relays mailing list tor-relays@lists.torproject.or