On Fri, 20 Feb 2015 12:02:14 +0100 Peter Palfrader <[email protected]> wrote:
> On Tue, 30 Dec 2014, Clayton wrote: > > > On Tue, 30 Dec 2014 11:16:29 +0100 > > intrigeri <[email protected]> wrote: > > > > > clayton wrote (29 Dec 2014 10:23:43 GMT) : > > > > "The communication stream of managed proxy '/usr/bin/obfsproxy' > > > > is 'closed'. Most probably the managed proxy stopped running. > > > > <etc....>" > > > > > > > Then I added the logging bits in the ClientTransportPlugin line > > > > above. But, no /tmp/obfsproxy.log file is created. However, if > > > > I run > > > > > > > /usr/bin/obfsproxy --log-min-severity info > > > > --log-file /tmp/obfsproxy.log managed > > > > > > > straight from the command line, a /tmp/obfsproxy.log is created. > > > > > > Do you have AppArmor enabled? > > > > Nope, not a trace of it. > > I can't reproduce it. Does that still happen on your system? What > does an strace -f report? What is your complete and uncensored > configuration? What else is weird on your system? As luck would have it, I just got a newer laptop and did a clean Jessie install. My configuration works perfectly on the newly installed machine. On the old machine where things are not working, I updated everything. Both machines are running an almost identical testing/Jessie setup with a smattering of unstable packages, enforced in large part by Puppet. I try to deviate from 'testing' as little as possible, generally speaking. I then purged both tor and obfsproxy, and re-installed. Still not working. My torrc (enforced by Puppet on both machines!) is very simple: ClientTransportPlugin obfs3 exec /usr/bin/obfsproxy --log-min-severity info --log-file /tmp/obfsproxy.log managed UseBridges 1 Bridge obfs3 <IP>:<port> <key> Bridge obfs3 <IP>:<port> <key> Bridge obfs3 <IP>:<port> <key> I can share the bridge details privately with you if it would be helpful, but I re-iterate: this works on one of my machines. The difference between the two machines is the broken one's install is older, with the obvious consequences. I have at least one more machine I am going to try this on, another day. And now the final kick in the pants ;-) : strace -o /tmp/tor-strace.log -f /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc actually works! I get to "Bootstrapped 100%: Done" in the Tor log. But if I then kill the strace'd process and go back and start Tor with systemd, it fails again. I iterated a couple times, and it is repeatable. Perhaps an issue with systemd? Or a race condition (this is a slightly older/slower machine, Thinkpad x201i)? apt-get purge install sysvinit-core and then reboot with sysvinit resulted in no gain. Tor still cannot start obfsproxy, same symptoms. I am inclined to no longer suspect systemd. Clayton -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
