On Mon, Jan 18, 2016 at 01:26:05AM +0100, AJ NOURI wrote:
> *sudo service tor reload*
>
> * Reloading tor daemon configuration... [fail]
>
> > Jan 08 12:31:58.000 [notice] Received reload signal (hup). Reloading
> > config and resetting internal state.
> > Jan 08 12:31:58.000
Try restart instead of reload.
It looks like you've installed from a package, which allows the daemon
to bind to any port then "drop privileges" (according to the FAQ).
https://www.torproject.org/docs/faq.html.en#PackagedTor
On Mon, 18 Jan 2016, at 12:26 AM, AJ NOURI wrote:
> *sudo service tor
*sudo service tor reload*
* Reloading tor daemon configuration... [fail]
*/var/log/tor/log*
>
> Jan 08 08:01:25.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd)
> opening new log file.
> Jan 08 10:19:40.000 [notice] Heartbeat: Tor's uptime is 3 days 0:00
> hours, with 0
relays] Relay configuration issue "Could not bind to
0.0.0.0:443: Permission denied"
*sudo service tor reload*
* Reloading tor daemon configuration... [fail]
*/var/log/tor/log*
>
> Jan 08 08:01:25.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd)
> opening new
Removed and reinstalled Tor. Now works fine.
Appreciate your prompt answers guys!
On Fri, Jan 22, 2016 at 10:42 AM, Louie Cardone-Noott
wrote:
> Try restart instead of reload.
>
> It looks like you've installed from a package, which allows the daemon to
> bind to any port