| Michael Uplawski |
05-30-2016 06:24 AM |
Tor does no longer start automatically after update to tor 0.2.7.6
Hi.
Since my upgrade and dist-upgrade yesterday, and with the current package tor 0.2.7.6, the client has problems and does not start automatically.
I will quote the relevant section from the syslog.
In the meantime, I have found previous reports and discussions that were promising because of similarities in the reported errors, but they concern older tor-versions and are in the end not describing the same kind of failures. My phenomenon appears to be unique as there is this “ Too many levels of symbolic links”.
I am unable to deduce what causes the problem or if and which changes to the file system would be sufficient to solve it.
Here are the lines from the syslog that I deem significant:
Code:
May 30 12:46:58 drusus systemd[836]: tor@default.service: Failed at step NAMESPACE spawning /usr/bin/install: Too many levels of symbolic links
May 30 12:46:58 drusus systemd[1]: Started Permit User Sessions.
May 30 12:46:59 drusus systemd[1]: Started Getty on tty1.
May 30 12:46:59 drusus systemd[1]: Reached target Login Prompts.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Control process exited, code=exited status=226
May 30 12:46:59 drusus systemd[1]: Failed to start Anonymizing overlay network for TCP.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Unit entered failed state.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Failed with result 'exit-code'.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
May 30 12:46:59 drusus systemd[1]: Stopped Anonymizing overlay network for TCP.
May 30 12:46:59 drusus systemd[1]: Starting Anonymizing overlay network for TCP...
May 30 12:46:59 drusus systemd[895]: tor@default.service: Failed at step NAMESPACE spawning /usr/bin/install: Too many levels of symbolic links
May 30 12:46:59 drusus systemd[1]: tor@default.service: Control process exited, code=exited status=226
May 30 12:46:59 drusus systemd[1]: Failed to start Anonymizing overlay network for TCP.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Unit entered failed state.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Failed with result 'exit-code'.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
May 30 12:46:59 drusus systemd[1]: Stopped Anonymizing overlay network for TCP.
May 30 12:46:59 drusus polkitd[870]: started daemon version 0.105 using authority implementation `local' version `0.105'
(... omitting other services starting ...)
May 30 12:46:59 drusus systemd[1]: Starting Anonymizing overlay network for TCP...
May 30 12:46:59 drusus systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks.
May 30 12:46:59 drusus systemd[912]: tor@default.service: Failed at step NAMESPACE spawning /usr/bin/install: Too many levels of symbolic links
May 30 12:46:59 drusus systemd[1]: tor@default.service: Control process exited, code=exited status=226
May 30 12:46:59 drusus systemd[1]: Failed to start Anonymizing overlay network for TCP.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Unit entered failed state.
May 30 12:46:59 drusus systemd[1]: tor@default.service: Failed with result 'exit-code'.
(... omitted other services starting, tor restarting again...)
(... finally: )
May 30 12:47:01 drusus systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
May 30 12:47:01 drusus systemd[1]: Stopped Anonymizing overlay network for TCP.
May 30 12:47:01 drusus systemd[1]: tor@default.service: Start request repeated too quickly.
May 30 12:47:01 drusus systemd[1]: Failed to start Anonymizing overlay network for TCP.
May 30 12:47:01 drusus systemd[1]: tor@default.service: Unit entered failed state.
May 30 12:47:01 drusus systemd[1]: tor@default.service: Failed with result 'start-limit-hit'.
|
