[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Server node stalls on unsuccessful socks listener change


After unsuccessful hot-changing socks listener address using 'reload',
tor server node stalls breaking all connections.

This is a rude behavior against all current server node users.

a) Why the change of the listen address was unsuccessful? There was no
other process on that address. Are there known issues?

b) Wouldn't it be a better idea, to just reclaim the previous listen
address to continue service? Changing the socks listener address on a
server node is a minor incident and should not lead to sudden death on

Aug 21 08:20:08.094 [notice] Received reload signal (hup). Reloading
Aug 21 08:20:08.095 [notice] Closing no-longer-configured Socks listener
Aug 21 08:20:08.096 [notice] Opening Socks listener on
Aug 21 08:20:08.096 [warn] Could not bind to Address
already in use. Is Tor already running?
Aug 21 08:20:08.096 [warn] Failed to parse/validate config: Failed to
bind one of the listener ports.
Aug 21 08:20:08.096 [err] Reading config failed--see warnings above. For
usage, try -h.
Aug 21 08:20:08.096 [warn] Restart failed (config error?). Exiting.


BlueStar88 <BlueStar88@xxxxxxxxxxx>

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil