Torflow logs hint that it's crazily misparsing control protocol lines
Here's a line from my data/scanner.1/bw.log file:
DEBUG[Wed Sep 18 18:50:22 2013]:0.000684022903442 CIRC 1048265 BUILT $4D8AB52858C08B65CD9119592F2C4A0AC295A167,$68EB5D04D9E81B3EF07B30E6A1710478F3BE50C6 REASON=EATED=2013-09-18T22:50:22.246008EATED? For real? and that's the REASON?
And here's another
DEBUG[Wed Sep 18 19:03:43 2013]:57.2632410526 CIRC 1048359 CLOSED $8DC59FB04EA3EC881D14E1CD806E9CF5B63EFA9E,$CDE18EB5FF62D741681F779CEA483C67A09C675F REASON=EATED=2013-09-18T22:58:56.688748 REMOTE_REASON=EDED, huh?