Tor Atlas and https://torstatus.blutmagie.de does not report any activity in graphs for my Tor exit. This data has been missing for some days now. Says online. Not stable yet as I keep it rebooting my new server once a day for 30 mins as checking if there are any errors. Which leads to another question. Is /etc/tor/torrc read on the fly? That is editing torrc will change the server on writing the file, or does it need tor restart with each edit. I had assumed the latter. I am not sure where or how this data collected for the pretty graphs. My server seems busy with many gigs in and out on tor ports and its own IP address according to various iptraffic tools I run on the server, but no data on those graphs at Atlas and elsewhere. Tor 0.2.7.6 on Ubuntu Linux on a VPS. Is this just me and something wrong with torrc ? or a more general problem? Gerry
Am 15.05.2016 um 13:14 schrieb Dr Gerard Bulger:
Tor Atlas and https://torstatus.blutmagie.de does not report any activity in graphs for my Tor exit. This data has been missing for some days now. Says online. Not stable yet as I keep it rebooting my new server once a day for 30 mins as checking if there are any errors. Which leads to another question. Is /etc/tor/torrc read on the fly? That is editing torrc will change the server on writing the file, or does it need tor restart with each edit. I had assumed the latter.
I am not sure where or how this data collected for the pretty graphs. My server seems busy with many gigs in and out on tor ports and its own IP address according to various iptraffic tools I run on the server, but no data on those graphs at Atlas and elsewhere.
Tor 0.2.7.6 on Ubuntu Linux on a VPS.
Is this just me and something wrong with torrc ? or a more general problem?
Gerry
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Gerry, the "3 day" and "1 week" graph on Atlas are disabled. No relays has them. Did you mean that? ~Josef
On 05/15/2016 01:14 PM, Dr Gerard Bulger wrote:
for 30 mins as checking if there are any errors. Which leads to another question. Is /etc/tor/torrc read on the fly? That is editing torrc will change the server on writing the file, or does it need tor restart with each edit. I had assumed the latter.
You need to "reload" the Tor process, send it a SIGHUP signal, to make it reread the configuration. Some configuration options are only picked up on restart. No changes are picked up "on the fly".
Is this just me and something wrong with torrc ? or a more general problem?
You can post the log with "notice" enabled, and also post the fingerprint if you want more feedback. -- Moritz Bartl https://www.torservers.net/
As "root" user on the server : service tor reload Or as your usual user, on Ubuntu I remember "sudo" sudo service tor reload and it will eat the new torrc file ;) Don't forget, you can check some things with tor-arm package, it's quick and easy, then : sudo -u debian-tor arm (if Ubuntu is using the debian-tor user to launch the Tor process...) Le 15/05/2016 à 13:29, Moritz Bartl a écrit :
You need to "reload" the Tor process, send it a SIGHUP signal, to make it reread the configuration. Some configuration options are only picked up on restart. No changes are picked up "on the fly".
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
On Sun, May 15, 2016 at 09:02:40PM +0200, Petrusko wrote:
Don't forget, you can check some things with tor-arm package, it's quick and easy, then : sudo -u debian-tor arm (if Ubuntu is using the debian-tor user to launch the Tor process...)
This is the dangerous way to use arm: it gives arm access to your relay's private identity key and other files it has no business accessing. The safer way to use it is listed towards the bottom of https://www.torproject.org/docs/tor-relay-debian#after --Roger
Thx Roger for this correction! (oops I don't remember reading this doc to the number 14, my bad!) Le 15/05/2016 à 22:05, Roger Dingledine a écrit :
This is the dangerous way to use arm: it gives arm access to your relay's private identity key and other files it has no business accessing. The safer way to use it is listed towards the bottom of https://www.torproject.org/docs/tor-relay-debian#after
--Roger
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
participants (5)
-
Dr Gerard Bulger -
Josef Stautner -
Moritz Bartl -
Petrusko -
Roger Dingledine