I went and tried to start the nsole directly and that’s when I got the exceptions “EPIC FAIL database disk image is malformed”, specifically when UpdateVersionInfo is called on migration 159. nothing else, so I supposed it just stopped but logs don’t show any errors or crash.the last actions it did was downloading and installing the update 3., then applying database migrations.I went to check the logs and what I understood was that:
I checked the service, try to start it but nothing happened beside an error from the Windows service panel saying Sonarr started then topped. You should see a list of global.db's with different dates. Rename the global.db file to global.db.old. 13:04:51 ErrorLog Database Vacuum Error: database disk image is malformeddatabase disk image is malformed 13:04:59 ErrorLog Database Vacuum Error: database disk image is malformeddatabase disk image is malformed I have restarted HS3 several times in hope that it would solve the problem but with no positive effect. Open file explorer and navigate to C:\ProgramData\Tenable\Nessus essus\.
When I finally gave up after trying a lot of rollback, updates, and testing (so a bit polluted, but with clear errors) -> Stop the Nessus services via services.msc or an administrator level command prompt. When i tried that fix, i got the error-message The database disk image is malformed and nothing else. Mono version (if Sonarr is not running on Windows):ĭebug logs: right after I noticed Sonarr was offline -> Something about reinstalling the windows10-apps).
