Along with my recent OS upgrade I have also updated my tor relay from 0.2.4.3-alpha to 0.2.4.20. The latter version write two identical copies of every message to the log file. I have only one uncommented "Log " line in my torrc, which is Log notice file /var/log/tor/notices.log but every single message is getting written to the file twice. Jan 27 19:31:58.213 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening log file. Jan 27 19:31:58.214 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening log file. Jan 27 19:31:58.220 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Jan 27 19:31:58.220 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Jan 27 19:31:58.325 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Jan 27 19:31:58.325 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Jan 27 19:31:58.360 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Jan 27 19:31:58.360 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Jan 27 19:31:58.513 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 023220505A550D6FDF0C20FF7C48E66BA06A49A6' Jan 27 19:31:58.513 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 023220505A550D6FDF0C20FF7C48E66BA06A49A6' Jan 27 19:32:00.387 [notice] We now have enough directory information to build circuits. Jan 27 19:32:00.387 [notice] We now have enough directory information to build circuits. Jan 27 19:32:00.388 [notice] Bootstrapped 80%: Connecting to the Tor network. Jan 27 19:32:00.388 [notice] Bootstrapped 80%: Connecting to the Tor network. Jan 27 19:32:01.399 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor. Jan 27 19:32:01.399 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor. Jan 27 19:32:01.815 [notice] Bootstrapped 85%: Finishing handshake with first hop. Jan 27 19:32:01.815 [notice] Bootstrapped 85%: Finishing handshake with first hop. Jan 27 19:32:02.287 [notice] Bootstrapped 90%: Establishing a Tor circuit. Jan 27 19:32:02.287 [notice] Bootstrapped 90%: Establishing a Tor circuit. Jan 27 19:32:03.671 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jan 27 19:32:03.671 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jan 27 19:32:03.672 [notice] Bootstrapped 100%: Done. Jan 27 19:32:03.672 [notice] Bootstrapped 100%: Done. Jan 27 19:32:03.672 [notice] Now checking whether ORPort 67.175.219.175:32323 and DirPort 67.175.219.175:32326 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) Jan 27 19:32:03.672 [notice] Now checking whether ORPort 67.175.219.175:32323 and DirPort 67.175.219.175:32326 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) Jan 27 19:32:06.509 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jan 27 19:32:06.509 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jan 27 19:32:07.093 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Jan 27 19:32:07.093 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Jan 27 19:32:25.752 [notice] Performing bandwidth self-test...done. Jan 27 19:32:25.752 [notice] Performing bandwidth self-test...done. Jan 27 19:33:02.567 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. Jan 27 19:33:02.567 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. Jan 27 20:32:01.397 [notice] Heartbeat: Tor's uptime is 1:00 hours, with 7 circuits open. I've sent 2.93 MB and received 7.98 MB. Jan 27 20:32:01.397 [notice] Heartbeat: Tor's uptime is 1:00 hours, with 7 circuits open. I've sent 2.93 MB and received 7.98 MB. Jan 27 20:32:01.397 [notice] Average packaged cell fullness: 87.404% Jan 27 20:32:01.397 [notice] Average packaged cell fullness: 87.404% Jan 27 20:32:01.397 [notice] TLS write overhead: 9% Jan 27 20:32:01.397 [notice] TLS write overhead: 9% Jan 27 20:32:02.394 [notice] Circuit handshake stats since last time: 25/25 TAP, 13/13 NTor. Jan 27 20:32:02.394 [notice] Circuit handshake stats since last time: 25/25 TAP, 13/13 NTor. ...and so on. Is there some way to stop this behavior and get only a single copy of each message? Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *or* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************
On Tue, Jan 28, 2014 at 03:10:57AM -0600, Scott Bennett wrote:
Along with my recent OS upgrade I have also updated my tor relay from 0.2.4.3-alpha to 0.2.4.20. The latter version write two identical copies of every message to the log file. I have only one uncommented "Log " line in my torrc, which is
Log notice file /var/log/tor/notices.log
but every single message is getting written to the file twice.
Which package did you install? If it was the deb, look at /usr/share/tor/tor-service-defaults-torrc (these are the default defaults, if you will). --Roger
Roger Dingledine <arma@mit.edu> wrote:
On Tue, Jan 28, 2014 at 03:10:57AM -0600, Scott Bennett wrote:
Along with my recent OS upgrade I have also updated my tor relay from 0.2.4.3-alpha to 0.2.4.20. The latter version write two identical copies of every message to the log file. I have only one uncommented "Log " line in my torrc, which is
Log notice file /var/log/tor/notices.log
but every single message is getting written to the file twice.
Which package did you install? If it was the deb, look at /usr/share/tor/tor-service-defaults-torrc (these are the default defaults, if you will).
I'm guessing FreeBSD in which case the culprit is probably the rc script which enables notice logging by default: fk@r500 ~ $grep Log /usr/jails/tor-jail/usr/local/etc/rc.d/tor command_args="-f ${tor_conf} --PidFile ${tor_pidfile} --RunAsDaemon 1 --DataDirectory ${tor_datadir} --+Log ${tor_loglevel}\ file\ ${tor_logfile}" Fabian
On 28/01/2014 10:16 PM, Fabian Keil wrote:
Roger Dingledine <arma@mit.edu> wrote:
On Tue, Jan 28, 2014 at 03:10:57AM -0600, Scott Bennett wrote:
Along with my recent OS upgrade I have also updated my tor relay from 0.2.4.3-alpha to 0.2.4.20. The latter version write two identical copies of every message to the log file. I have only one uncommented "Log " line in my torrc, which is
Log notice file /var/log/tor/notices.log
but every single message is getting written to the file twice.
Which package did you install? If it was the deb, look at /usr/share/tor/tor-service-defaults-torrc (these are the default defaults, if you will).
I'm guessing FreeBSD in which case the culprit is probably the rc script which enables notice logging by default:
fk@r500 ~ $grep Log /usr/jails/tor-jail/usr/local/etc/rc.d/tor command_args="-f ${tor_conf} --PidFile ${tor_pidfile} --RunAsDaemon 1 --DataDirectory ${tor_datadir} --+Log ${tor_loglevel}\ file\ ${tor_logfile}"
Fabian
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I run my relays on FreeBSD too. Just leave all log settings commented in torrc: #Log notice file /usr/local/var/log/tor/notices.log #Log debug file /usr/local/var/log/tor/debug.log #Log notice syslog #Log debug stderr And you won't get duplicate entries in /var/log/tor. -- bsdbox.co
Roger Dingledine <arma@mit.edu> wrote:
On Tue, Jan 28, 2014 at 03:10:57AM -0600, Scott Bennett wrote:
Along with my recent OS upgrade I have also updated my tor relay from 0.2.4.3-alpha to 0.2.4.20. The latter version write two identical copies of every message to the log file. I have only one uncommented "Log " line in my torrc, which is
Log notice file /var/log/tor/notices.log
but every single message is getting written to the file twice.
Which package did you install? If it was the deb, look at
I used portmaster to install it from security/tor-devel in the FreeBSD ports tree.
/usr/share/tor/tor-service-defaults-torrc (these are the default defaults, if you will).
In FreeBSD, anything from ports and packages normally gets installed somewhere under /usr/local, not /usr. /usr/local/share/tor contains only two files, geoip and geoip6. However, I now see that Fabian Keil <freebsd-listen@fabiankeil.de> has responded, too:
I'm guessing FreeBSD in which case the culprit is probably the rc script which enables notice logging by default:
fk@r500 ~ $grep Log /usr/jails/tor-jail/usr/local/etc/rc.d/tor command_args="-f ${tor_conf} --PidFile ${tor_pidfile} --RunAsDaemon 1 --DataDirectory ${tor_datadir} --+Log ${tor_loglevel}\ file\ ${tor_logfile}"
Aw, hell. This is the first time in many years that I have built and installed tor from the ports tree, and I had forgotten all about the script. This sort of nonsense was one of several reasons I took to building tor manually and apart from the ports system. I would have done so again, except that 0.2.4.3-alpha was the last version that I was able to compile and have execute correctly. The port apparently chooses a set of build configuration options that works, so I used it. :-( So the makefile for the port replaced the old, slightly tailored version of that script that I had used for any years. :-( I guess I"m going to delve further into what it will take to resume building and installing tor outside the ports system. Thanks, Fabian and Roger. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *or* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************
participants (4)
-
Fabian Keil -
nano -
Roger Dingledine -
Scott Bennett