I don't have any knowledge or suggestions for preventing this corruption... but you could do daily database backups.
Restoring from a night-old backup would be a lot less disruptive than losing all your data. Even something this easy could be helpful: echo ".dump" | sqlite3 tasks.db > tasks-backup.sql The corresponding restore would look like this mv tasks.db tasks.db.old sqlite3 tasks.db < tasks-backup.sql Obviously you should try a backup and restore before counting on it. Hope this helps! Date: Mon, 23 May 2016 22:38:28 +0200 From: tatooin <tato...@free.fr> To: openvas-discuss@wald.intevation.org Subject: [Openvas-discuss] openvasmd regular tasks.db corruption issue Message-ID: <1464035908.12620.10.camel@wisukind> Content-Type: text/plain; charset="UTF-8" Hello, I'm trying to open a new thread on this issue as apparently my previous question did not raised a lot of interest... I am using OpenVas since 6 months now, and I have regular database corruptions issue which happens right after adding serveral targets and tasks with omp. When this happens, openvas continue to work correclty except that I cannot run any tasks. I can still create / delete tasks and targets, but I cannot run any scans. openvasmd --rebuild / --update will hang forever. No informations in OpenVAS logfiles. If I run an omp command to start a task, like : omp -v -h 127.0.0.1 --details -u admin -w admin -S 7e75c909-f376-41f6-abb0-b14cee30ca9e WARNING: Verbose mode may reveal passwords! Will try to connect to host 127.0.0.1, port 9390... It just hangs forever... This is the second time this is happening in 3 months. Last time I couldn't find any fix to this problem and I had to delete the database completely and create a new one, meaning I lost all my data. This problem is clearly critical from my point of view, so I'm a bit surprised nobody is reacting. I saw a lot of articles regarding gnutls issues which may create this problem, but it's clearly not my situation since the box has not been updated recently. Really I'm stuck here, so I would really appreciate some help at least to understand where the problem comes from. I am not the only one to face this problem, and so far I saw no resolution to this which means there is a severe bug somewhere. Thanks for your comments, if any. Best, _______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
