Luckily, this server doesn’t do anything else besides OpenVAS and most of my files are already backed up so really I am up for trying anything at this point.
-----Original Message----- From: Openvas-discuss [mailto:[email protected]] On Behalf Of Reindl Harald Sent: Monday, June 12, 2017 10:09 AM To: [email protected] Subject: Re: [Openvas-discuss] sql errors Am 12.06.2017 um 15:38 schrieb Brandon Perry: > >> On Jun 12, 2017, at 8:33 AM, Thijs Stuurman >> <[email protected] >> <mailto:[email protected]>> wrote: >> >> No, never. These are also the kind of errors I never ever wish to see! >> If your data is still there, scan tasks .. history etc’ I strongly >> urge you to make a backup and repeat making backups just in case. >> Many things can cause these errors, I cannot give you any specific >> place to start looking for a problem or solution. >> Perhaps it helps to get more log/verbose/debug information out of >> sqlite if possible. >> Check versions, is everything up to date? (sqlite, openvas) > > Perhaps consider PostgreSQL instead, simply for potential visibility > and easier diagnostics. maybe easier diagnostics *for you* - for everybody who is not usging postgresql in his daily workflow it leads sooner or later to more problems than it solves "disk I/O error" sounds RDBMS agnostic and the only real answer to that is find the hardware issue and grab your backups _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
