@Tom-Elliott Tom I can confirm that I had to do a FULL wipe as well for it to work. I think it may be database related. I upgraded to the latest, took a copy of the DB then did a FULL wipe. Tested it and everything worked. Restored the database backup, and it started the issue again. Not a huge deal since I have my snapshots and went to a known working version again though.
@Tom-Elliott Gotcha. We’re just imaging like crazy and that is creating a lot of these errors which filled about 12GB of logspace up. I’ve adjusted my logrotation (which is probably the better answer anyways).