Peter Palfrader wrote: > Can you retry with an info level log (see Tor#21019[1]), and maybe > strace -p <pid> -e connect the process while you're at it? > > Also, which kernel and which systemd? > > I had tried it on sid, using systemd 232-8, tor 0.2.9.7-rc-dev-.., > and 4.8.0-2-amd64 with apparmor enabled to boot.
Here are the versions on the two systems I've tried: linux 4.8.0-2-amd64 linux 4.6.0-1-amd64 systemd 232-7 systemd 232-3 tor 0.2.8.11 tor 0.2.8.9 Neither system has apparmor* packages installed. But, I was able to get it to work using /var/lib/bla/sock when I tried once more. Beginning to think that it's not related to filesystem perms, and is some intermittent or timing related problem getting the onion address published or querying it. I can consistently reproduce the problem by adding a new hidden service, starting up tor, and trying to connect to its onion address from the same system within about 1 minute. The telnet hangs, and this shows in the log: Dec 18 18:23:29.000 [info] connection_ap_handshake_rewrite_and_attach(): Got a hidden service request for ID '[scrubbed]' Dec 18 18:23:29.000 [info] connection_ap_handshake_rewrite_and_attach(): Unknown descriptor [scrubbed]. Fetching. Dec 18 18:23:29.000 [debug] rend_client_refetch_v2_renddesc(): Fetching v2 rendezvous descriptor for service [scrubbed] Dec 18 18:23:29.000 [info] pick_hsdir(): Could not pick one of the responsible hidden service directories, because we requested them all recently without success. (Still don't see how the apparmor config would let it read /var/lib/bla/sock tho.) -- see shy jo
signature.asc
Description: PGP signature
