Torbel stops receiving NEWCONSENSUS events
A couple of hours after starting up, Torbel stops logging about NEWCONSENSUS events. The accompanying torctl log clearly shows there are events, but torbel is either in some deadlock state or otherwise doesn't know to handle them. This means the scanner goes black, because it takes NEWCONSENSUS events as a motivation to rescan. I'm not sure yet why this happens at all, need to investigate...
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information