> On 23 May 2017, at 04:29, tor-relay.d...@o.banes.ch wrote:
>
> we are operating two exit nodes with each two tor processes out of
> Switzerland.
> The nodes worked quite stable until about 2-3 weeks ago.
>
> Since then we experience frequent disruptions (Up to several times a
> day). This is
Hi Nusenu and Roman,
thanks for you recommendations. I already implemented as small ~ 10
lines script which does it job
and logs what's going on.
Mit Mai 24 21:45:01 CEST 2017 Process tor2 is not running -> starting
Don Mai 25 08:50:02 CEST 2017 Process tor2 is not running -> starting
Don Mai 25
On Wed, May 24, 2017 at 07:51:50PM -0400, Roger Dingledine wrote:
> Well, you are a winner, in that you found a new Tor bug (in
> 0.3.1.1-alpha):
> https://bugs.torproject.org/22368
>
> Once we resolve that one, I'll ask for another valgrind run. :)
Ok, we merged the fix for bug 22368.
If
On Thu, 25 May 2017 08:54:00 +
nusenu wrote:
> I noticed your comment [1] about your plans to write a script that
> restarts tor should it get killed.
>
> I just wanted to let you know that if you have plans to upgrade to
> Ubuntu 16.04 you will get this out of the
Hi Dirk,
I noticed your comment [1] about your plans to write a script that
restarts tor should it get killed.
I just wanted to let you know that if you have plans to upgrade to
Ubuntu 16.04 you will get this out of the box due to systemd Restart=
[2] service configuration.
[1]
On Wed, May 24, 2017 at 08:49:38PM +0200, tor-relay.d...@o.banes.ch wrote:
> Hello Roger,
>
> I updated the ticket. You will find the output of the valgrind there as
> well:
> https://trac.torproject.org/projects/tor/attachment/ticket/22255/valgrind.txt
Well, you are a winner, in that you found
Hello Roger,
I updated the ticket. You will find the output of the valgrind there as
well:
https://trac.torproject.org/projects/tor/attachment/ticket/22255/valgrind.txt
best regards
Dirk
On 23.05.2017 06:00, Roger Dingledine wrote:
> On Tue, May 23, 2017 at 03:01:10AM +, John Ricketts
On Mon, May 22, 2017 at 10:48:31PM +0200, niftybunny wrote:
> Same with 0.3.0.5. Upgrading to 0.3.0.7 helped on most relays.
We didn't change anything between 0.3.0.5 and 0.3.0.7 that would
have helped.
If somebody with a really really fast CPU wants to run their relay under
valgrind
Same with 0.3.0.5. Upgrading to 0.3.0.7 helped on most relays.
niftybunny
ab...@to-surf-and-protect.net
Where ignorance is bliss, 'Tis folly to be wise.
Thomas Gray
> On 22. May 2017, at 20:29, tor-relay.d...@o.banes.ch wrote:
>
> Dear all,
>
> we are operating two exit nodes with each two
Le 22/05/17 à 20:29, tor-relay.d...@o.banes.ch a écrit :
Dear all,
we are operating two exit nodes with each two tor processes out of
Switzerland.
The nodes worked quite stable until about 2-3 weeks ago.
Since then we experience frequent disruptions (Up to several times a
day). This is
Hi
We do also experience high memory consumptions by Tor from time to time
which result in a total halt of the system.
I'm now testing several values in MaxMemInQueues...
Greetings
tor-relay.d...@o.banes.ch:
> Dear all,
>
> we are operating two exit nodes with each two tor processes out of
>
Dear all,
we are operating two exit nodes with each two tor processes out of
Switzerland.
The nodes worked quite stable until about 2-3 weeks ago.
Since then we experience frequent disruptions (Up to several times a
day). This is caused by a significant rise in memory consumption
by the tor
12 matches
Mail list logo