Timeline for "Reloading tor daemon configuration... fail" after updating torrc
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 4, 2016 at 11:41 | history | edited | Eric | CC BY-SA 3.0 |
deleted 10137 characters in body
|
Jan 4, 2016 at 11:40 | vote | accept | Eric | ||
Jan 4, 2016 at 10:48 | answer | added | Richard Horrocks | timeline score: 1 | |
Jan 4, 2016 at 1:32 | comment | added | Alexey Vesnin♦ | Use Tor from official git sources - I have had similar issues myself. Ubuntu-packaged version fails alot - Git one no problem. | |
Jan 3, 2016 at 16:06 | comment | added | Richard Horrocks | Let us continue this discussion in chat. | |
Jan 3, 2016 at 16:04 | history | edited | Eric | CC BY-SA 3.0 |
added torrc file
|
Jan 3, 2016 at 15:58 | comment | added | Eric |
No joy, I still get this: * Reloading tor daemon configuration... [fail]
|
|
Jan 3, 2016 at 15:57 | comment | added | Richard Horrocks |
Sorry, I meant the reload command: sudo service tor reload
|
|
Jan 3, 2016 at 15:54 | comment | added | Eric |
If I run it with sudo I get the same Configuration was valid message.
|
|
Jan 3, 2016 at 15:51 | comment | added | Richard Horrocks |
Permissions issue? What happens if you run it with sudo ?
|
|
Jan 3, 2016 at 15:44 | comment | added | Eric |
I just ran $ tor --verify-config , and it spits back: Configuration was valid .
|
|
Jan 3, 2016 at 15:42 | comment | added | Richard Horrocks |
Try running with the --verify-config flag and see if it throws up anything useful. (i.e tor --verify-config ).
|
|
Jan 3, 2016 at 14:57 | review | First posts | |||
Jan 3, 2016 at 21:08 | |||||
Jan 3, 2016 at 14:54 | history | asked | Eric | CC BY-SA 3.0 |