Tor never recovers when started with skewed clock
How to reproduce...
Start Tor with a skewed clock. For example, +/- one week.
Tor will detect, that the clock is skewed.
Received directory with skewed time (server '...'): It seems that our clock is ahead by 6 days, 23 hours, 59 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings. I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Then reset clock back to correct time. Tor will also detect that.
Your system clock just jumped 604800 seconds backward; assuming established circuits no longer work.
Tor still won't work (no connections possible).
Tor recovers and can now connect.
getinfo version: 250-version=0.2.3.25 (git-3fed5eb096d2d187) (On Debian Wheezy.)