Re: [tor-relays] Consensus Weight calculation

[Vort]

> This could be part of your issue.
> The code for tor relays on Windows is not maintained very well.

There are many relays on Windows, which are not stuck.
And many relays on Linux, which are stuck.


> What is the connection / handle limit on the tor process and the user
> you are using for the tor process?

> For a non-exit relay, it needs to be around 10,000.
> For an large exit relay, it needs to be 50,000 or so.

Windows does not limit connection count for processes and users.
There are also no system-wide limit for sockets.
Except for available dynamic port range (1025-64510 on my computer).


> Now check the latency and bandwidth to these directory authorities.
> But only do to once, they have a lot of load already.

> Also, use gabelmoobwauth, rather than gabelmoo.
> And check Faravahar.

Latency (ping):
longclaw   / 199.254.238.53 : 187 ms
gabelmoobwscan / 131.188.40.189 : 44 ms
moria1 / 128.31.0.34: 128 ms
faravahar  / 154.35.175.225 : 147 ms

Bandwidth (via PrivacyRepublic0001 and 16M file from 38.229.72.16):
longclaw: 285 KiB/s
gabelmoobwscan  : 1195 KiB/s
moria1  : 404 KiB/s
faravahar   : 141 KiB/s


> Ok, the next limit will be the observed bandwidth.

After the yesterday test #5, observed bandwidth changed to 1.12 MiB/s.


> You need to be patient.

That's not a problem if I know that something will definitely
  change in the future.


-- Vort

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

Re: [tor-relays] 申请

[I]

 https://zh.greatfire.org/




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

Re: [tor-relays] 申请

[I]

Ming Fu,你也可以在这里找到帮助。 https://en.greatfire.org/Rob



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

Re: [tor-relays] 申请

[I]

哦！ 你想订阅列表！看看这两个可以加入的页面。tor-relay是用于聊天运行一个继电器，电话是关于更通用的东西。继续写中文，有人可能回信。https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talkhttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays抢-Original Message-From: gmf...@gmail.comSent: Wed, 28 Jun 2017 09:17:20 +0800To: tor-relays@lists.torproject.orgSubject: [tor-relays] 申请





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

[tor-relays] 申请

[龚明福]

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

Re: [tor-relays] Consensus Weight calculation

[teor]

> On 27 Jun 2017, at 23:52, Vort  wrote:
> ...
> 
>> I made a wiki page to tell people how to do that:
>> https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow
>> ...
> 
>> 1. Check RAM, CPU, and socket/file descriptor usage on your relay
> 
> Private bytes amount for tor.exe process is 116 MiB,

This could be part of your issue.
The code for tor relays on Windows is not maintained very well.

>  ...
> 
> Tor process have 573 handles open and about 380 established TCP
>  connections. But this is unusual activity, related to Faravahar
>  downtime and, respectively, obtaining of Fast and HSDir flags.
> Usually, it have only 20-30 connections established.

What is the connection / handle limit on the tor process and the user
you are using for the tor process?

For a non-exit relay, it needs to be around 10,000.
For an large exit relay, it needs to be 50,000 or so.

> ...
> 
>> 3. Check each of the votes for your relay on consensus-health
>>  (large page), and check the median:
> 
> Consensus was published 2017-06-27 12:00:00.
> longclaw: bw=34
> gabelmoo: bw=41
> moria1  : bw=23
> 
> *median*: bw=34

This is the limit on your relay.

Now check the latency and bandwidth to these directory authorities.
But only do to once, they have a lot of load already.

Also, use gabelmoobwauth, rather than gabelmoo.
And check Faravahar.

>> 4. Check your relay's observed bandwidth and bandwidth rate (limit).
> 
> Bandwidth rate: 1 MiB/s
> Bandwidth burst   : 3 MiB/s
> Observed bandwidth: 250.77 KiB/s

Ok, the next limit will be the observed bandwidth.

> ...
>> It might not be me that helps you.
>> So please talk to the list when you write back.
> 
> But no one else shown the interest on answering to this topic.

If you just write to me, that won't change.
You need to be patient.

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org






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

Re: [tor-relays] Exit / Bad Gateway

[Roger Dingledine]

On Tue, Jun 27, 2017 at 03:52:31PM +0200, Sebastian Urbach wrote:
> Well Faravahar is finally back but im still wondering why my System (located
> in France) is measured by exactly 1 System a few thousand miles away.

Actually, it's measured by three bwauths. You can look it up on
https://www.freehaven.net/~arma/moria1-v3-status-votes
(Careful, it is a very large file.)

In ParEpistemenTaksis's case, it has bwauth measurements from moria1,
longclaw, and Faravahar.

It looks like teor's thought that at least one bwauth is sufficient to
get moved off of consensus weight 20 wasn't right. You need three:
https://gitweb.torproject.org/tor.git/tree/src/or/dirvote.c?id=tor-0.3.0.8#n1990

Which on further thought makes sense -- if only rogue dir auth could
by itself declare that all its friends in the unmeasured relays set
are actually consensus weight 1e9, that wouldn't be cool.

So then your question would be "ok, there are four bwauths, how come
gabelmoo hasn't measured me?"
https://consensus-health.torproject.org/#bwauthstatus
And that is a fine question, but I fear the answer is the same as all
the other "why is the torflow stuff broken" questions. Tom Ritter has
been looking lately at making it better, at least.

(Thanks for running an exit relay! :)

--Roger

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

Re: [tor-relays] Consensus Weight calculation

[Vort]

> Before we investigate the measurements:
> * We need to know if anything on your relay or at your provider
>   is making your relay slow,
> * We need to be know which measurement of your relay is slow.

> I made a wiki page to tell people how to do that:
> https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow

> Please go through the steps, and let us know what results you get.
> Then someone can help you more.

> 1. Check RAM, CPU, and socket/file descriptor usage on your relay

Private bytes amount for tor.exe process is 116 MiB,
  3.4 GiB of system memory is available (out of 8 GiB total).
Log shows that: "Based on detected system memory, MaxMemInQueues
  is set to 2048 MB. You can override this by setting MaxMemInQueues by hand."

Tor is using 0-1% of CPU resource on the average.
Sometimes it consumes 25% of CPU (100% of 1 core) for 10 seconds.
And then returns back to normal 0-1% usage.

Tor process have 573 handles open and about 380 established TCP
  connections. But this is unusual activity, related to Faravahar
  downtime and, respectively, obtaining of Fast and HSDir flags.
Usually, it have only 20-30 connections established.


> 2. Check the internet peering (bandwidth, latency) from your relay's
>   provider to other relays.

Latency (ping):
hviv104 / 192.42.116.16  : 40 ms
PrivacyRepublic0001 / 178.32.181.96  : 39 ms
Unnamed / 185.170.41.8   : 36 ms
McCormickRecipes/ 18.85.22.204   : 135 ms
PhantomTrain4   / 65.19.167.131  : 184 ms

Bandwidth (via dopper / 192.42.113.102 and bwauth's 16M file):
hviv104  : 50 KiB/s
PrivacyRepublic0001  : 1.3 MiB/s
Unnamed  : 155 KiB/s
McCormickRecipes : 947 KiB/s
PhantomTrain4: 899 KiB/s


> 3. Check each of the votes for your relay on consensus-health
>   (large page), and check the median:

Consensus was published 2017-06-27 12:00:00.
longclaw: bw=34
gabelmoo: bw=41
moria1  : bw=23

*median*: bw=34


> 4. Check your relay's observed bandwidth and bandwidth rate (limit).

Bandwidth rate: 1 MiB/s
Bandwidth burst   : 3 MiB/s
Observed bandwidth: 250.77 KiB/s


> 5. Run a test using tor to see how fast tor can get on your network/CPU:

This will alter observed bandwidth. But okay.
Depending on exit node, result varies from 117 KiB/s to 1 MiB/s. Example:

$ curl --socks5-hostname localhost:9050 --insecure -O 
https://38.229.72.16/bwauth.torproject.org/16M
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100 16.0M  100 16.0M0 0   857k  0  0:00:19  0:00:19 --:--:--  967k


> 6. Run a test using tor and chutney to find out how fast tor can get on
>   your CPU. Keep increasing the data volume until the bandwidth stops 
> increasing:

As this tool is designed for Linux, I can run it only within virtual machine.
But results are still good:

$ CHUTNEY_DATA_BYTES=104857600 ./chutney verify networks/basic-min
...
Single Stream Bandwidth: 99.46 MBytes/s
Overall tor Bandwidth: 397.85 MBytes/s

$ CHUTNEY_DATA_BYTES=1048576000 ./chutney verify networks/basic-min
...
Single Stream Bandwidth: 43.52 MBytes/s
Overall tor Bandwidth: 174.07 MBytes/s


> It might not be me that helps you.
> So please talk to the list when you write back.

But no one else shown the interest on answering to this topic.


-- Vort

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

Re: [tor-relays] Exit / Bad Gateway

[Sebastian Urbach]

Dear list,

Well Faravahar is finally back but im still wondering why my System 
(located in France) is measured by exactly 1 System a few thousand miles away.


--
Sincerely yours / M.f.G. / Sincères salutations

Sebastian Urbach

---
Those who surrender freedom for security will
not have, nor do they deserve, either one.
---
Benjamin Franklin (1706-1790)



Am 27. Juni 2017 14:04:50 schrieb teor :


TL;DR:

Faravahar is down, that's probably what's causing it.

On 27 Jun 2017, at 21:05, Florentin Rochet  
wrote:

...

Same for my exit. I just count that 220 exit relays over 869 have their 
Consensus Weight at 20.

...

On 2017-06-27 12:49, Logforme wrote:

On 2017-06-27 12:35:21, "Sebastian Urbach"  wrote:

...
My Exit:

https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99FE

My Consendus Weight dropped to 20 today


Hi Florentin, Sebastian,

Faravahar is down, so we are down to 3 bandwidth authorities, which
changes the median bandwidth for some relays. It also means that
relays that were only measured by Faravahar will get a bandwidth of
20. (Relays with 1 or 2 measurements will have unstable bandwidths.)

You can just wait it out until North America wakes up :-)

You can check the measurement details for your relay if you want.
There's a wiki page for relay operators with slow relays:

https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow


and i found the following in notices.log:

Jun 27 12:03:35.000 [warn] http status 502 ("Bad Gateway") reason 
unexpected while uploading descriptor to server '154.35.175.225:80').
Jun 27 12:07:35.000 [warn] Received http status code 502 ("Bad Gateway") 
from server '154.35.175.225:80' while fetching 
"/tor/server/d/C8B7BA97808F42802FCC2DF231A85ACB5B8D848A.z". I'll try again 
soon.

…


Faravahar is down, so that might be why its caching proxy is giving
this response.

https://atlas.torproject.org/#details/CF6D0AAFB385BE71B8E111FC5CFF4B47923733BC

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org







--
___
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

[tor-relays] Tor relay

[Cryptic Admin]

Tor relay
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Exit / Bad Gateway

[teor]

TL;DR:

Faravahar is down, that's probably what's causing it.

> On 27 Jun 2017, at 21:05, Florentin Rochet  
> wrote:
> ...
> 
> Same for my exit. I just count that 220 exit relays over 869 have their 
> Consensus Weight at 20.
> ...
> 
> On 2017-06-27 12:49, Logforme wrote:
>> On 2017-06-27 12:35:21, "Sebastian Urbach"  wrote:
>>> ...
>>> My Exit:
>>> 
>>> https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99FE
>>> 
>>> My Consendus Weight dropped to 20 today

Hi Florentin, Sebastian,

Faravahar is down, so we are down to 3 bandwidth authorities, which
changes the median bandwidth for some relays. It also means that
relays that were only measured by Faravahar will get a bandwidth of
20. (Relays with 1 or 2 measurements will have unstable bandwidths.)

You can just wait it out until North America wakes up :-)

You can check the measurement details for your relay if you want.
There's a wiki page for relay operators with slow relays:

https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow

>>> and i found the following in notices.log:
>>> 
>>> Jun 27 12:03:35.000 [warn] http status 502 ("Bad Gateway") reason 
>>> unexpected while uploading descriptor to server '154.35.175.225:80').
>>> Jun 27 12:07:35.000 [warn] Received http status code 502 ("Bad Gateway") 
>>> from server '154.35.175.225:80' while fetching 
>>> "/tor/server/d/C8B7BA97808F42802FCC2DF231A85ACB5B8D848A.z". I'll try again 
>>> soon.
>>> …

Faravahar is down, so that might be why its caching proxy is giving
this response.

https://atlas.torproject.org/#details/CF6D0AAFB385BE71B8E111FC5CFF4B47923733BC

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org






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

Re: [tor-relays] Consensus Weight calculation

[teor]

> On 27 Jun 2017, at 14:57, Vort  wrote:
> 
> Hello, teor.
> 
> Is it worth to wait till you have time to investigate stuck relays problem?

You can help yourself!

Before we investigate the measurements:
* We need to know if anything on your relay or at your provider
  is making your relay slow,
* We need to be know which measurement of your relay is slow.

I made a wiki page to tell people how to do that:
https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow

Please go through the steps, and let us know what results you get.
Then someone can help you more.

It might not be me that helps you.
So please talk to the list when you write back.

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org






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

Re: [tor-relays] Exit / Bad Gateway

[Florentin Rochet]

Hello,

Same for my exit. I just count that 220 exit relays over 869 have their 
Consensus Weight at 20.

Best,

Florentin

On 2017-06-27 12:49, Logforme wrote:

On 2017-06-27 12:35:21, "Sebastian Urbach"  wrote:

Dear list,

My Exit:

https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99FE 



My Consendus Weight dropped to 20 today and i found the following in 
notices.log:


Jun 27 12:03:35.000 [warn] http status 502 ("Bad Gateway") reason 
unexpected while uploading descriptor to server '154.35.175.225:80').
Jun 27 12:07:35.000 [warn] Received http status code 502 ("Bad 
Gateway") from server '154.35.175.225:80' while fetching 
"/tor/server/d/C8B7BA97808F42802FCC2DF231A85ACB5B8D848A.z". I'll try 
again soon.


Any ideas what to do or just sit it out ?
-- Sincerely yours / M.f.G. / Sincères salutations

Sebastian Urbach
Same for my non-exit: 
https://atlas.torproject.org/#details/855BC2DABE24C861CD887DB9B2E950424B49FC34


Looks like the drop in cw coincided with messages like these in the log:
Jun 27 04:35:48.000 [warn] Received http status code 502 ("Bad 
Gateway") from server '154.35.175.225:80' while fetching 
"/tor/server/d/44C3629D79C5366209DB976F1F1588A39B923123+C4716B2DA2AB2CAC2DA0256CD2484050B75371BF.z". 
I'll try again soon.



154.35.175.225 is the authority server faravahar which have had 
network issues in the past.


___
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

Re: [tor-relays] Exit / Bad Gateway

[Logforme]

On 2017-06-27 12:35:21, "Sebastian Urbach"  wrote:

Dear list,

My Exit:

https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99FE

My Consendus Weight dropped to 20 today and i found the following in 
notices.log:


Jun 27 12:03:35.000 [warn] http status 502 ("Bad Gateway") reason 
unexpected while uploading descriptor to server '154.35.175.225:80').
Jun 27 12:07:35.000 [warn] Received http status code 502 ("Bad 
Gateway") from server '154.35.175.225:80' while fetching 
"/tor/server/d/C8B7BA97808F42802FCC2DF231A85ACB5B8D848A.z". I'll try 
again soon.


Any ideas what to do or just sit it out ?
-- Sincerely yours / M.f.G. / Sincères salutations

Sebastian Urbach
Same for my non-exit: 
https://atlas.torproject.org/#details/855BC2DABE24C861CD887DB9B2E950424B49FC34


Looks like the drop in cw coincided with messages like these in the log:
Jun 27 04:35:48.000 [warn] Received http status code 502 ("Bad Gateway") 
from server '154.35.175.225:80' while fetching 
"/tor/server/d/44C3629D79C5366209DB976F1F1588A39B923123+C4716B2DA2AB2CAC2DA0256CD2484050B75371BF.z". 
I'll try again soon.



154.35.175.225 is the authority server faravahar which have had network 
issues in the past.


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

[tor-relays] Exit / Bad Gateway

[Sebastian Urbach]

Dear list,

My Exit:

https://atlas.torproject.org/#details/4198BD138E5E11B15B05C826B427148CED7D99FE

My Consendus Weight dropped to 20 today and i found the following in 
notices.log:


Jun 27 12:03:35.000 [warn] http status 502 ("Bad Gateway") reason 
unexpected while uploading descriptor to server '154.35.175.225:80').
Jun 27 12:07:35.000 [warn] Received http status code 502 ("Bad Gateway") 
from server '154.35.175.225:80' while fetching 
"/tor/server/d/C8B7BA97808F42802FCC2DF231A85ACB5B8D848A.z". I'll try again 
soon.


Any ideas what to do or just sit it out ?
--
Sincerely yours / M.f.G. / Sincères salutations

Sebastian Urbach

---
Those who surrender freedom for security will
not have, nor do they deserve, either one.
---
Benjamin Franklin (1706-1790)


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