Ownership error on hidden service dir encountered on config reload kills Tor process
If you add a new hidden service to your torrc with a hidden service dir not owned by the Tor process user (I ran across this by rsyncing an HS dir from another box), and SIGHUP the Tor process, the error adding the HS is not handled cleanly:
Example:
Jun 26 20:14:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Jun 26 20:14:06.000 [notice] Read configuration file "/etc/tor/torrc".
Jun 26 20:14:06.000 [notice] Tor 0.2.4.20 opening log file.
Jun 26 20:14:06.000 [warn] /var/tor/bitcoind_hidden_service/ is not owned by this user (tor, 58) but by root (0). Perhaps you are running Tor as the wrong user?
Jun 26 20:14:06.000 [warn] Error loading rendezvous service keys
Jun 26 20:14:06.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information