Ran a scan against a /24 network last night and woke up to OpenVAS dead, an empty openvassd dump file in /var/log/openvas and the following error in openvasmd.log:
md manage:WARNING:2018-05-14 11h45.15 utc:23539: sql_exec_internal: sqlite3_step failed: cannot start a transaction within a transaction md manage:WARNING:2018-05-14 11h45.15 utc:23539: sqlv: sql_exec_internal failed md manage:WARNING:2018-05-14 11h45.15 utc:23539: manage_schedule: manage_update_nvti_cache error Platform is an odroid-c2 (arm64), 4 cores, 2GB RAM, running Kali 2018.2 with current updates. A bit of research seems to indicate a thread was started that attempted to start another sqlite transaction while one (possibly the scan?) was running. Is it possible having a scan running on the 4 cores available conflicted with some internal manager thread? What starts manage_update_nvti_cache()? Based on the code here: http://www.openvas.org/src-doc/openvas-manager/manage__sql_8c_source.html#l13388 it seems like the immediate giveup there is being hit, not sure why openvassd would core out as a result. any help would be appreciated, thanks.
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
