Hi Roger, Thanks for your quick responses, I really appreciate it! Yes, thinking about it, this does look like an issue with the port forwarding helper. I’ve filed the following trac issue: https://trac.torproject.org/projects/tor/ticket/9781. I don’t have PortForwardingHelper set in the torrc at all (there must be some default). Regarding bufferevents, this flag is not actually on by default at all. I turned it on manually in portage, not knowing that it was still in testing (perhaps this can be better noted in the Gentoo ebuid’s use flag description). I’ve just recompiled with the flag off, and the relay is back up and running, still showing those “terminate process” messages.
Yours, ~ M.
On Sep 18, 2013, at 10:51 PM, Roger Dingledine arma@mit.edu wrote:
On Wed, Sep 18, 2013 at 08:20:18PM -0400, Michael Gorbach wrote:
Nope, I don?t have any special pluggable transports configured in my torrc, which is odd. What other processes would for be starting kicking off? All I have set in torrc is [...] PortForwarding
That's likely the one!
You might be one of the first users of this option. Please help us track down what's going on and file a trac ticket about it.
Do you set PortForwardingHelper? If not, I wonder what it's trying to run (and whether it finds it).
I do have tor compiled by gentoo?s portage package manager, with the for-hardening, bufferedevents, threads, and nat-pmp flags set.
You should be aware that bufferevents is experimental, and by experimental in this case I mean "known to not work sometimes and not really a good idea to use unless you're doing it in order to write patches for it". If you want to help your fellow Gentoo users, it sounds like you should file a ticket for gentoo to make it harder to accidentally turn on.
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays