[tor-relays] Bandwidth Accounting troubles

Hello! I've enabled bandwidth accounting on my tor relay, but encountering issues when the relay attempts to wake from hibernation Mar 20 23:47:25 tcj Tor[74346]: Bandwidth soft limit reached; commencing hibernation. No new connections will be accepted Mar 20 23:52:30 tcj Tor[74346]:

Re: [tor-relays] Problem with arm

Hello i was able to open the port by reading a guide in digitalocean thank you for helping me realizing it was a firewall problem El 21/03/2017 a las 20:55, nusenu escribió: > > Javier Benito Santoni: >> Mar 21 06:27:37.000 [notice] Tor 0.2.4.27 (git-412e3f7dc9c6c01a) opening >> new log file. >>

Re: [tor-relays] Strange behaviour Tor 0.2.9.10

On Tue, Mar 21, 2017, at 09:27 AM, teor wrote: > > Can you try setting an explicit IP address for your bridge, using: > Address NNN.NNN.NNN.NNN > in the torrc? > > We might not have fixed all instances of this issue in 20423. > Done, (SIGINT still hadn't shut down after 10 minutes btw) then

Re: [tor-relays] What kind of hardware do I need for my relay

On Mon, 20 Mar 2017 22:49:53 +, Farid Joubbi wrote: > I do mean Megabits. > I have learned a long time ago that Tor traffic throughput can't be compared > with ssh. No, but it can be used to roughly judge what the hardware is capable of. It doesn't help to throw more hardware at a node when

Re: [tor-relays] Problem with arm

Javier Benito Santoni: > Mar 21 06:27:37.000 [notice] Tor 0.2.4.27 (git-412e3f7dc9c6c01a) opening > new log file. > Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9001) has not > managed to confirm that its ORPort is reachable. Please check your > firewalls, ports, address, /etc/hosts file,

Re: [tor-relays] Problem with arm

Mar 21 06:27:37.000 [notice] Tor 0.2.4.27 (git-412e3f7dc9c6c01a) opening new log file. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Mar 21 06:31:19.000 [warn]

Re: [tor-relays] Problem with arm

Hello, your experience with ARM I have it on my different systems too. A new version of this tool is in active development. Some minutes ago I was on one of my servers an used ARM. After some seconds the tool had a freeze. It is not possible to use it over a longer time. In the past I had

Re: [tor-relays] Problem with arm

Is it possible that the Tor service uses the config from /etc and that arm reads a torrc created under the user who runs arm? That's how I explain the same message on my server... Your server isn't shown on globe/atlas... what says your tor logfile? Everything ok there? > Am 21.03.2017 um

Re: [tor-relays] Problem with arm

Javier Benito Santoni: > Hello, im having a problem with arm. > > Everytime i open it it apears this: [ARM_WARN] The torrc differs from > what tor's using. You can issue a > x sighup to reload the torrc values by pressing x. > qj - torrc values differ on lines: 2, 3 > > Even by

[tor-relays] Problem with arm

Hello, im having a problem with arm. Everytime i open it it apears this: [ARM_WARN] The torrc differs from what tor's using. You can issue a x sighup to reload the torrc values by pressing x. qj - torrc values differ on lines: 2, 3 Even by restarting tor service it shows the same error

Re: [tor-relays] What kind of hardware do I need for my relay

Ok, N3050 cpu count was my mistake. It are 2 cores. It is a hand-size mini pc (ZOTAC 323 nano). It act as a middle node. Now checked: The cpu load is ~15% with 1184 connected relays! (home connection with 10MBit/s; actual modem usage: 5MBit/s upload average, 8MBit/s peak. Downstream equal

Re: [tor-relays] Strange behaviour Tor 0.2.9.10

> On 21 Mar 2017, at 02:19, Geoff Down wrote: > > > > On Mon, Mar 20, 2017, at 01:44 PM, teor wrote: Mar 19 11:52:37.000 [notice] Tried for 32496 seconds to get a connection to [scrubbed]:80. Giving up. >> >> We fixed a bug like this in 0.2.9.6-rc. >> >> It