Re: [tor-relays] new relay - not working right
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-10-13 01:47 PM, Green Dream wrote: > Hi. Thanks for running a relay. Thank you both for answering me. The relay's nickname is "ClydeBoy" and is listed on blutmagie so I presume is on Atlas & Globe. I have a "normal" flag and "running". The website now shows a bandwidth of 1. However, some preliminary items I probably have wrong. The only way I can stop tor is ps -Al | grep tor and then kill . Is there not a more elegant way? Also, if I start it as su: root it runs as root. If I start it "tor" as me it runs as me. There is a user listed in the password file of debian-tor but I am not sure how or if it is being used. How should tor be started and who should it be running as? The current /var/log/tor/log (fresh, new) has nothing in it?? Bruce Ganton -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWHnv5AAoJEAnfV8n5U7IzX0gH+waKd75Dx71OE9VaujJR9Qgu LxsOgvxqb60AWb4G2q/Bhswpy9tSl9PWEklCOyv55NswXRRkYA+Ac+sNATCY8QUb qs+FlZ4lXMrtVq2Kpec5ixpw9ZV013ucx/ZK7cDQdF3AM/8jXGUMiP/i4y37BDUc aI61+QLAZAX9MTGIaRa2LRkuV/oG/xF8esM/7s1zggNCfNradE90PfaxClj8Yoj1 WuRWSlMMcOp0+w93w277bzFRumQQE1Nu3Qoj5VVuMwGjXrWOHAKCYHEYsXm1quWG 9rtytAt1/ndUcJU9gUUMfKuHQfSZnOZEp6nK4/nhWUjnfnah2mcts8bj39vThYY= =rZ0o -END PGP SIGNATURE- 0xF953B233.asc Description: application/pgp-keys 0xF953B233.asc.sig Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] new relay - not working right
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-10-14 10:18 AM, Green Dream wrote: > ClydeBoy is listed three times on Atlas. It appears to be running > from the same server, as the IP/port are the same for all 3 nodes, > however the fingerprint is different for each instance on Atlas: I was able to identify two tor processes running and killed them both. I then used your recommended way of starting tor. Now the log filed is being filled with good stuff and ARM is behaving as I am used to. FWIW, I googled around quite a bit and never noticed specific instructions on stopping tor. So thanks for giving me the magic bullet. > > I'm guessing that during your testing and config changes, the > existing Tor processes weren't getting killed and so you wound up > with multiple Tor processes fighting for attention and resources. > That's not going to work very well. ;-) > > I'm not sure how you installed Tor. For Ubuntu or Debian, I > normally follow the instructions here: > > https://www.torproject.org/docs/debian.html.en#ubuntu Yes, these are the directions I followed. In fact I installed Debian just so I could use option 1 as it seemed preferable. I was reasonably careful with this; how wrong can you go with sudo apt-get install? However, I have learned from hard experience to never be too cocky about having everything done right. :-) Bruce Ganton -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWHpW6AAoJEAnfV8n5U7Izf94H/2b2/z/TJ/nx1fhx3AETJSei /p1EUENFx2Whf74hgBwOhkWFonFwKJ3BAle5rFa//R77GSginU9x4YzSEXZXQNYY o3+5reGDV7BKOnOVzHDs1fHUJ20yv73wjPso9f4IU+8xoSVUFGuiTe9L8q5HcHSQ FTb6lkLsE+VTqck4VEg+a71rL9VjfeR3Z4GYobmJB5GB/tjbZ/bZ7ZqIpcMvpy+w tyJ0DWKOcBJxHNigUniITX42qDeWJNqUnQvVqhjh7IW7DznjKTnGlMQq1y9zFgzM bzOUPaU5V1ZdWIlpThXpzWb/inFHe+6SJ0U7BIxx9gZZBHOQxD1KG1nXygeNMgQ= =y0cH -END PGP SIGNATURE- 0xF953B233.asc Description: application/pgp-keys 0xF953B233.asc.sig Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] new relay - not working right
Pardon the bad copy/paste in the last email. The third listing on Atlas is: https://atlas.torproject.org/#details/3FE1025A1E779CAFD21F593AC200C7447703343D ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] new relay - not working right
ClydeBoy is listed three times on Atlas. It appears to be running from the same server, as the IP/port are the same for all 3 nodes, however the fingerprint is different for each instance on Atlas: https://atlas.torproject.org/#details/68F162C50F22205FB3B728ACE67470B17D7430D6 https://atlas.torproject.org/#details/53C1C1A27F9CD0A87383FB473ABD7E8D4378F703 https://atlas.torproject.org/#details/53C1C1A27F9CD0A87383FB473ABD7E8D4378F703 I'm guessing that during your testing and config changes, the existing Tor processes weren't getting killed and so you wound up with multiple Tor processes fighting for attention and resources. That's not going to work very well. ;-) I'm not sure how you installed Tor. For Ubuntu or Debian, I normally follow the instructions here: https://www.torproject.org/docs/debian.html.en#ubuntu If you go this route, you should wind up with Tor installed as a proper service, which can then be controlled via the standard methods, like: sudo service tor start sudo service tor stop sudo service tor restart This will also take care of running the Tor process as the debian-tor user. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] new relay - not working right
Hi. Thanks for running a relay. > For several days now its bandwidth, according to ARM, is in the > bits/second and there seems to be some problem reading its own > torrc file. Also, while it had four connections for a while, there are > none now. Regarding the low bandwidth and a low number of connections, this could be typical for a new relay. Reference https://blog.torproject.org/blog/lifecycle-of-a-new-relay > [ARM NOTICE] Read last day of bandwidth history from state file > (-7502 seconds is missing) This is normal in my experience. Arm is trying to read your node's bandwidth history to populate the graphs with data collected before you started Arm. I don't know why it fails, but you can squelch it by adding the following config line to ~/.arm/armrc (or wherever you keep your armrc file): features.graph.bw.prepopulate false > [ARM WARN] The torrc differs frm what tor's using. You an issue a > sighup to reload the torrc values by pressing x. Pretty much what it sounds like; you edited torrc after starting up Arm. To bring in the chages such that Arm is in sync, just press 'x' in Arm twice and it will issue a HUP signal to the Tor process, which reloads the config. > [ARM NOTICE] Tor is preventing system utiliites like netstat and lsof > from working. This means arm can't provide you with connection > information You need to add the following to /etc/tor/torrc if you want to utilize all the features of Arm: DisableDebuggerAttachment 0 It's disabled by default for security (with a value of '1'), so think carefully before doing this. It "reduces security by enabling debugger attachment to the Tor process. This can be used by an adversary to extract keys." (Quoting from https://trac.torproject.org/projects/tor/ticket/13880). If you do enable the deubgger attachment for Arm, make sure your control port is locked down (not reachable from the Internet or from other hosts you don't control, etc.) It does seem a little odd you're still at 0 bandwidth with no connections. Without more data, it's hard to say what else might be going wrong (if anything). What does /var/log/tor/log have to say? There should be some lines in there that indicate if it's reachable from the internet. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
