-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/4/2015 8:25 PM, Damian Johnson wrote:
> For what it's worth process permissions aren't at play here. Arm
> is failing to talk with the control port - permissions could cause
> us to be unable to read the authentication cookie, but that would
> be a different message.
>
> Cheers! -Damian
>
>
> On Fri, Dec 4, 2015 at 5:36 PM, Manager Bahia del Sol LLC
> <manager@bahiadelsol.io> wrote:
>>
>> No worries,
>>
>> Are you sure the user or group is debian_tor? The default is
>> debian-tor in Ubuntu.
>>
>> If that isn't the problem,
>>
>> First I would be sure tor is actually running. top or top -u
>> debian-tor The second will show if tor is actually running as the
>> user you think it is.
>>
>> If it is, then see if it is listening on the control port sudo
>> netstat -ntlp | grep LISTEN
>>
>> If it is I would suspect that either a firewall is blocking that
>> port. If you have one running try shutting it down for a few
>> minutes while you try to start arm.
>>
>> Or maybe it is a permissions issue where arm is not running as
>> the same user as tor. You could try starting arm as root to see
>> if it would start. But, do not run arm as root full time. Only
>> try to start it as a test.
>>
>>
>>
>> -- Manager of Bahia del Sol LLC
>>
>>
>> _______________________________________________ tor-relays
>> mailing list tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
> _______________________________________________ tor-relays mailing
> list tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>

> Dec 05 21:17:46.000 [notice] Your IP address seems to have changed
> to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46.000
> [notice] Our IP Address has changed from 142.4.217.95 to
> 167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE).
> Dec 05 21:18:42.000 [notice] Your IP address seems to have changed
> to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com).
> Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
> from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
> METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05
> 21:18:43.000 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent. Publishing server
> descriptor. Dec 05 21:38:37.000 [warn] Your server
> (142.4.217.95:9030) has not managed to confirm that its DirPort is
> reachable. Please check your firewalls, ports, address, /etc/hosts
> file, etc. Dec 05 21:58:37.000 [warn] Your server
> (142.4.217.95:9030) has not managed to confirm that its DirPort is
> reachable. Please check your firewalls, ports, address, /etc/hosts
> file, etc.
I've gotten this far, not being much good at networking I can't tell
where the problem lies.. do I need to forward something?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYzh6AAoJEJQqkaGlFNDPCeYIAJln5C5Z+7n69zcoW1/RdUxi
iduyKB/lnXc1Be190dSsHikjXVWv2hYvbnwvn3RuGOAft29WHd/OJi+GK9qBAB57
qdL+sl4PvlJVlWYH8hDK65FHqmZ85UYRX0nP5KsvRLbzKlNiX1rGSJPfpVSeOlK8
2bvSG/b4+Y4ZqmlxmLyJW5eJnMMzOHJdTf/OgUefnqic5KB1BLXygFi566lYYNMC
d8R8RObw8Rez/9H4+cKXcbNfnN2Yh0RMwpHF8nqpU8D292kO+Koz/xhfsu9VXRfe
DBKhCSfKdDJBNiP0zI13Y1OB5tq4SG0sKhhGCCavW+3oelT2ujyTBgB4xAyszkY=
=U+4y
-----END PGP SIGNATURE-----

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays