Agreed . My relay is well
Below all of the thresholds for “overloaded”, for gods sake 64gb ram and 12 cpus should be adequate for a tor relay? 10gb connection?
I’ve asked multiple times for help trying to figure this out and have gotten zero response.
It seems to be very difficult to get any help with running relays. I’d think the tor community would want exit relays running, and would be more forthcoming with information, but the docs and help sections are almost useless.
The troubleshooting page for an overloaded relay mentions running metricsport, but with no instructions or even links to anywhere to explain how to do this.
The relay search/status website shows 2 extra links below some relays but not others, I get no extra info on mine.
My relay has a dirport of 9030 in my config and nyx confirms this. The relay status website says I have no dirport configured.
There are so many little issues at play, you’d think this would be simpler to have everything running.
Sent from ProtonMail for iOS
On Fri, Oct 1, 2021 at 21:29, torix via tor-relays <tor-relays@lists.torproject.org> wrote: My relays (Aramis) marked overloaded don't make any sense either. Two of the ones marked with orange are the two with the lowest traffic I have (2-5 MiB/s and 4-9 MiB/s - not pushing any limits here); the third one with that host has more traffic and is fine.
So far this indicator seems to be no help to me.
--Torix
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, October 1st, 2021 at 12:22 PM, David Goulet <dgoulet@torproject.org> wrote:
> On 01 Oct (03:08:20), Andreas Kempe wrote:
>
> > Hello David!
> >
> > On Mon, Sep 27, 2021 at 08:22:08AM -0400, David Goulet wrote:
> >
> > > On 24 Sep (12:36:17), lists@for-privacy.net wrote:
> > >
> > > > On Thursday, September 23, 2021 3:39:08 PM CEST Silvia/Hiro wrote:
> > > >
> > > > > When a relay is in the overloaded state we show an amber dot next to the
> > > > >
> > > > > relay nickname.
> > > > >
> > > > > Nice thing. This flag has noticed me a few days ago.
> > > >
> > > > > If you noticed your relay is overloaded, please check the following
> > > > >
> > > > > support article to find out how you can recover to a "normal" state:
> > > > >
> > > > > https://support.torproject.org/relay-operators/relay-bridge-overloaded/
> > > > >
> > > >
> > > > A question about Enabling Metricsport. Is definitely Prometheus necessary?
> > > >
> > > > Or can the Metrics Port write into a LogFile / TextFile?
> > >
> > > The output format is Prometheus but you don't need a prometheus server to get
> > >
> > > it.
> > >
> > > Once opened, you can simply fetch it like this:
> > >
> > > wget http://<IP_OF_METRICSPORT>:<METRICS_PORT>/metrics -O /tmp/output.txt
> > >
> > > or
> > >
> > > curl http://<IP_OF_METRICSPORT>:<METRICS_PORT>/metrics -o /tmp/output.txt
> >
> > I've only ever gotten an empty reply when trying to extract metrics
> >
> > and I still do on Tor 4.6.7. I have some vague memory of the metrics
> >
> > previously only being for hidden services.
> >
> > All the metrics mentioned in the overload guide[1] seem to be missing.
> >
> > Having a quick look at the Git repository, it seems that only
> >
> > 0.4.71-alpha and latest master contain the necessary changes for these
> >
> > metrics.
> >
> > Is my assumption correct or am I doing something wrong?
>
> Correct, relay metrics are only available on >= 0.4.7.1-alpha. Hopefully, we
>
> should have an 0.4.7 stable by end of year (or around that time).
>
> David
>
> -------------------------------------------------------------------------
>
> xX/GscsnOTkKMqPla5JDOc2EqZ3GG/imhQ7gx+DQhVE=
>
> tor-relays mailing list
>
> tor-relays@lists.torproject.org
>
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays