Hot answers tagged

5

Edit (after realizing Homebrew is a osx only pakage manager): on OS X: To install arm: Simply install arm using brew install arm. To just view the logs: var/log dir doesn't exist by defult. You need ot make it under /usr/local/Cellar/tor/{Tor version}/ and perhaps turn notices or debug logs on in your torrc. And Tor will print logs on /usr/local/Cellar/...


4

The exiting cleanly sounds like you or something else is closing Tor. Can you check whether the process is still running? Can it be that you run the Tor command in foreground (seeing all the output) and then close the SSH session? If you do so Tor will be shut down. You may want to adapt /etc/tor/torrc and then use service start tor. This will start Tor as ...


4

Arm includes within itself a readme... https://gitweb.torproject.org/arm.git/blob/HEAD:/README


3

You are not doing anything wrong. The message you see is in fact a false alarm. According to the arm maintainer: That message simply means that tor is currently running with the 'RunAsDaemon' option enabled, but this setting isn't in your torrc. This message is meant to help people who edit their torrc, forget to restart tor, and are then confused ...


2

The measured bandwidth is mostly determined by external measurements by the Bandwidth Authorities. The following should help explain it... https://blog.torproject.org/blog/lifecycle-of-a-new-relay


2

Your best bet is Vidalia. This must be installed manually. However one of the Tor developers has some pre-built binaries. Select the one which fits you best and download it. You can extract (or execute in Windows) the package to any directory. Within the extracted files is a script called start-vidalia. When you execute it Vidalia comes up. When Vidalia ...


2

Perhaps this would help: How to use Arm with Tor Browser Bundle


2

You set values for RelayBandwidthRate and RelayBandwidthBurst in your torrc. RelayBandwidthRate is set to 500 KB. This translates to 500 kilo Bytes per second, which is 500*8=4000 Kilo Bits per second. arm somehow rounds this number down to 3.9 Mb/s. On your screenshot that shows the torrc inside arm you changed the number to 250 KB and arm shows 2 Mb/s. ...


2

SOLUTION!! : all it needed was this flag in the torrc DisableDebuggerAttachment 0


2

A quick Google resulted in the following page, which details both how to set up a relay on CentOS, and how to install ARM: https://www.pixeljumble.com/how-to-setup-a-tor-relay-on-centos/ The pertinent parts are: Download ARM from https://www.atagar.com/arm/download.php Install the package: rpm -ivh arm-replace-with-version-downloaded.rpm Restart Tor: ...


2

Tor recently switched to providing bandwidth history in 4-hour intervals rather than 15-minute intervals. This caused a lot of the bandwidth displaying tools to have issues with displaying the histories. These issues should be raised on Tor's bug tracker for the individual components if they haven't been mentioned there already so they can be fixed ...


2

From the ARM project page, navigate to the Git repository. You'll notice that here ARM is actually referred to as Nyx. One of the files at the top level of the repository tree is nyxrc.sample which provides a sample of different config options that can be set in your nyxrc file. (Of course, you don't have a nyxrc file, you have an armrc. If you've created ...


2

No, arm is not available for Windows unless you use Cygwin (ticket).


2

You must include the line DisableDebuggerAttachment 0 in your torrc file in order to force Tor to allow arm access to the list of currently open sockets it has which it then uses to create the list of connections.


2

Due to regression introduced in OpenSSL 1.1.1a. Openssl says fix in next openssl release: https://github.com/openssl/openssl/issues/7712 Until then, workaround for coping with OpenSSL 1.1.1a added to Tor: https://trac.torproject.org/projects/tor/ticket/28616 Can confirm that Tor 0.3.5.7 no longer issues these errors. Look for this in the Tor log: [warn] ...


1

I have the same error since upgrade from openssl to version openssl-1.1.1.a-1 on linux arch. Downgrading openssl to version openssl-1.1.1-1 solved the problem.


1

Why should I run arm monitoring tool using this command: sudo -u debian-tor arm Running any process as root should generally be avoided. If anyone compromises the process, she'll have full root access. In case of Tor, Tor itself is running as debian-tor. If you your Tor processes is compromised the next logical step is to try to evaluate ...


1

Not normal for Tor, but normal for Whonix. It's sdwdate. Details: https://www.whonix.org/wiki/Dev/TimeSync


1

It shows you all the conections your node uses. The example you're cited is one single circle, a 3-hop one. It says, thay you've used a Guard node as an entry, selected an intermediate(Middle) and exiting through a french node. This can be your connection through Tor, and - generally speaking - you should not be in Exit role in any of your connections, that'...


1

"ps aux | grep torrc from the command line. Use torrc in your grep to weed out any other strings containing "tor". The user will be the first field in the output" - Richard Horrocks This command worked but was submitted as a comment. I just wanted to place this into an answer so my question can be considered solved. All credit to Richard Horrocks for ...


1

I asked that March '14 in another post. ARM don't differentiates between internal and external (to the normal web) circuits. Your relay is probably correct configured and will not relay as an Exit to the normal web. 2 tickets exist to clarify that UX problem in ARM. Ticket: 6430 Perhaps internal circuits which are not for directory fetches could simply ...


1

Thanks for running a relay. (: Clients choose which relays to use based on their consensus weight. The consensus weight is assigned by the directory authorities after measuring the throughput for your relay. There are a number of things that can impact the speed at which your relay can be used, including the CPU speed, CPU architecture, the network ...


1

Same with Globe. I'm getting the same things as you since last night at around 8 PM CST. Appears to be a problem with the main Tor website. Just give it a few hours. I'm sure they are working on it already. :)


1

it's about a CPU consumption and IRQ's. Check your top - an process named irqballance may be causing some problem. If so, kill it every 8-12 hours via crontab and it will be fine. if not - please tell me your full hw and sw specs, so I'll be able to take a deeper look. Cheers!


1

Do once. (Install missing dependencies. Only required for Whonix 8. Will be no longer required on Whonix 9.) sudo apt-get update sudo apt-get install telnet Do every time you want a new circuit. Run tor-ctrl (installed by default) with signal newnym. bash -x tor-ctrl -p notrequired -c "signal newnym" If you see at the bottom of the output. + sendcmd ...


1

ARM is designed to use the Tor control port to interact with Tor, not manage the Tor service itself. I know that it's also added features to manage starting and stopping the Tor service but that's just for lazy admins. You should start the tor service, connect to it via ARM, and then close both when you no longer need a client.


Only top voted, non community-wiki answers of a minimum length are eligible