[tor-relays] Notices.Log Message

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can someone explain the message below regarding bw_accounting and the lack of a master identity key in my notices.log file? [warn] Failed to unlink /var/lib/tor/bw_accounting: No such file or directory Feb 26 10:04:02.000 [notice] It looks like I need

Re: [tor-relays] Netflix overblocking non-exit Tor relays

Hello Jonas ! > You mention an 'official response from Netflix' - are you willing to share > this? Unfortunately this is nothing I got in writing yet after only 2 days. At the beginning of the last call, I heard a "this call might be recorded" announcement. When I realized that they are not wi

Re: [tor-relays] Nyx Project Ideas

Damian Johnson: > Hi wonderful relay operators. It's GSoC season again, where students > can be funded to make open source projects like Tor even better! > > Nyx (previously known as arm [1]) has been my main focus this last > year and is inching ever closer to release. For those unfamiliar with

Re: [tor-relays] Netflix overblocking non-exit Tor relays

On Sat, Feb 27, 2016 at 12:42:38AM +0100, Gero Kuehn wrote: > They did however not > leave the impression that they a) care or b) intend to fix this at some > point by parsing the Tor network information properly instead of using > whatever cheap&wrong hack they use now. There is actually a servi

Re: [tor-relays] Netflix overblocking non-exit Tor relays

I've also had several extensive conversations with Netflix support about this but haven't received an answer beyond a generic 'there is a problem with your router' type response. You mention an 'official response from Netflix' - are you willing to share this? Mostly I'm interested if this respons

[tor-relays] Netflix overblocking non-exit Tor relays

tl;dr: Even paying customers sharing IPs with non-exit Tor relays are now blocked from accessing Netflix Hello everyone ! After two very fruitless attempts to get the issue silently resolved through proper Netflix support channels, the time has come to make this public. As some of you have probab

Re: [tor-relays] Tor Process Being Killed on VPS

On Fri, 26 Feb 2016 22:56:05 + Toralf Förster wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Stephen R Guglielmo: > > NTPd is not running (I've tried, but the kernel does not have permission to > > set the clock; I assume this is due to the hypervisor setup). > Hhm, ntp sh

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 30

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 27 Feb 2016 00:20:38 +0500, you wrote: > > --Sig_/PllBt_/1sHfmWgs/aS1Ks.r > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > On Fri, 26 Feb 2016 18:24:57 + (GMT) > stea...@nym.mixmin.net wrote: >

Re: [tor-relays] Tor Process Being Killed on VPS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Stephen R Guglielmo: > NTPd is not running (I've tried, but the kernel does not have permission to > set the clock; I assume this is due to the hypervisor setup). Hhm, ntp should be able to set the unix time for and within your virtual machine. It

Re: [tor-relays] Tor Process Being Killed on VPS

On 26.02.2016 00:19, Stephen R Guglielmo wrote: > I have a VPS with 512 MB RAM. [...] The relay is an entry guard and moves > about 20 MB/s. Is that really 20 MegaByte per second? If so, I fear 512 MB RAM won't cut it. According to my experience, for a 100 Mbit/s relay you need at least 1 GB RA

Re: [tor-relays] Tor Process Being Killed on VPS

echo 3 | tee /proc/sys/vm/drop_caches On Thu, Feb 25, 2016 at 6:19 PM, Stephen R Guglielmo wrote: > Hello, > > I have a VPS with 512 MB RAM. I run nothing on it except nginx and a Tor > relay. The relay is an entry guard and moves about 20 MB/s. It seems that > the kernel is killing the Tor pro

Re: [tor-relays] Tor Process Being Killed on VPS

clearing the memory cache with a cron job cant hurt On Thu, Feb 25, 2016 at 6:19 PM, Stephen R Guglielmo wrote: > Hello, > > I have a VPS with 512 MB RAM. I run nothing on it except nginx and a Tor > relay. The relay is an entry guard and moves about 20 MB/s. It seems that > the kernel is killin

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 30

On Fri, 26 Feb 2016 18:24:57 + (GMT) stea...@nym.mixmin.net wrote: > > [1] https://packages.debian.org/wheezy/tor > > [2] https://www.torproject.org/docs/debian.html.en > > > Thanks for the links above. I have updated to 0.2.7.6. I had a > hickup initially trying to launch arm as user debian-t

Re: [tor-relays] Tor Process Being Killed on VPS

On Fri, 26 Feb 2016 08:05:06 -0500 Steve Snyder wrote: > I'm unfamiliar with the memory use of nginx, but 512MB ought to be more > than enough RAM to run just the relay on a 64-bit VPS.. > > Are you *sure* you're not running anything else? Not crond? Not ntpd? > Not iptables? If not SSH, how d

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 30

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 26 Feb 2016 04:39:26 +, you wrote: > > Message: 3 > Date: Thu, 25 Feb 2016 22:27:36 +0100 > From: Tomasz Nitecki > To: tor-relays@lists.torproject.org > Subject: Re: [tor-relays] Stable Flag Question > Message-ID: <56cf71c8.6000...@tnnn.p

Re: [tor-relays] Tor Process Being Killed on VPS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, More information is needed. Please indicate the type of virtualization used (VMware, Xen, KVM, OpenVZ), your operating system and Tor version as well as the "out of memory" log messages you mentioned - are these from kernel logs or Tor's log

Re: [tor-relays] Feedback

On 26.02.2016 13:50, Roman Mamedov wrote: > On Fri, 26 Feb 2016 12:27:07 +0100 > Random Tor Node Operator wrote: > >> So in terms of censorship resistance, bridges with occasionally changing >> IP are better for the Tor network than those with static IP. > > EVERY DAY != "occasionally". > > Yo

Re: [tor-relays] Tor Process Being Killed on VPS

I'm unfamiliar with the memory use of nginx, but 512MB ought to be more than enough RAM to run just the relay on a 64-bit VPS.. Are you *sure* you're not running anything else? Not crond? Not ntpd? Not iptables? If not SSH, how do you administer the VPS? What type of virtualization is the VP

Re: [tor-relays] Tor Process Being Killed on VPS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This happend before with my 512MB node, when it was set unlimited amount of Mbit/sec. Also swap might help. On February 26, 2016 12:19:44 AM GMT+01:00, Stephen R Guglielmo wrote: >Hello, > >I have a VPS with 512 MB RAM. I run nothing on it except

Re: [tor-relays] Feedback

On Fri, 26 Feb 2016 12:27:07 +0100 Random Tor Node Operator wrote: > So in terms of censorship resistance, bridges with occasionally changing > IP are better for the Tor network than those with static IP. EVERY DAY != "occasionally". Your idea may have some reason to it, but when the IP change

Re: [tor-relays] Feedback

On 26.02.2016 11:54, Tim Wilson-Brown - teor wrote: > >> On 26 Feb 2016, at 11:52, Random Tor Node Operator >> mailto:t...@unterderbruecke.de>> wrote: >> >> On 26.02.2016 05:15, torser...@datakanja.de >> wrote: >>> * Next, i noticed a frequent (daily) behavior of t

Re: [tor-relays] Light Bandwidth Monitor (like Munin)

On 02/26/2016 12:15 PM, Pierre L. wrote: > Hey all, > > May be RPi users... and others linux users! > I'm looking for a light bandwidth graph software producing html files, > to monitor and graph up/down eth0 bandwidth used on my RPi Tor relay. vnstat perhaps? I know vnstati produces graphs in th

Re: [tor-relays] Feedback

> On 26 Feb 2016, at 11:52, Random Tor Node Operator > wrote: > > On 26.02.2016 05:15, torser...@datakanja.de > wrote: >> * Next, i noticed a frequent (daily) behavior of the Tor server >>dropping traffic to around zero. Inspecting this, let me to >>und

Re: [tor-relays] Feedback

On 26.02.2016 05:15, torser...@datakanja.de wrote: > * Next, i noticed a frequent (daily) behavior of the Tor server > dropping traffic to around zero. Inspecting this, let me to > understand, my provider was disconnecting me and reassigning a new > IP on a daily basis, which took som