> On 17 Oct 2017, at 21:43, tor wrote:
>
> > There's a bug in 0.3.0 and later that causes clients to fetch
> > microdescriptors from fallbacks. So fallbacks (and authorities)
> > will have extra load until that's fixed.
> >
> > https://trac.torproject.org/projects/tor/ticket/23862
>
> Makes se
> There's a bug in 0.3.0 and later that causes clients to fetch
> microdescriptors from fallbacks. So fallbacks (and authorities)
> will have extra load until that's fixed.
>
> https://trac.torproject.org/projects/tor/ticket/23862
Makes sense. The relay can't keep up with the extra load. It's basi
> On 17 Oct 2017, at 17:02, tor wrote:
>
> > You are on 0.2.9.11 and #20059 was merged in 0.2.9.12
> > https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?h=release-0.2.9
>
> I see. I'm trying to stay on 0.2.9.x since that is considered the "long-term
> support" release. This is a fallback
> You are on 0.2.9.11 and #20059 was merged in 0.2.9.12
> https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?h=release-0.2.9
I see. I'm trying to stay on 0.2.9.x since that is considered the "long-term
support" release. This is a fallback directory mirror which I'd like to keep as
stable as
tor wrote:
> Hi,
>
> I'm troubleshooting a Linux relay where the Tor service is having
> problems. External monitoring alerts indicate both the ORPort and
> DirPort are unreachable (TCP connection timeout). I can ssh in and the
> Tor service is still running. The node seems to have increased memor
Hi,
I'm troubleshooting a Linux relay where the Tor service is having problems.
External monitoring alerts indicate both the ORPort and DirPort are unreachable
(TCP connection timeout). I can ssh in and the Tor service is still running.
The node seems to have increased memory usage at this poin
