System: Linux mint 18.3
_openvas9-scanner 5.1.3-1 _
redis-server 2:3.0.6-1ubuntu0.3 (with openvas configuration settings)
Starting a task on a somehow big target (1000 IP addresses) will lead openvasmd stop answering requests with error:
#### Internal error: exec_omp_get:3113 (GSA 7.0.3)
An internal error occurred. Diagnostics: Could not authenticate to manager daemon.
According to openvasmd.log the scan is started and task status changed to “Running”. Right after this, the following error is logged in openvasmd.log:
md manage:WARNING:2019-01-27 16h32.40 utc:18932: sql_exec_internal: sqlite3_step failed: interrupted
md manage:WARNING:2019-01-27 16h32.40 utc:18932: sqlv: sql_exec_internal failed
However the scan continue in the background.
The only way to restore access to openvasmd is either by flushing redis cache or by restarting openvasm, which will put the task status to “Stopped”.
This is a major issue as basically openvas9 is unuseable with big tasks in this environment. I must note that starting small tasks doesn’t create any issue.
Last point, this doesn’t seem related with bug described in https://community.greenbone.net/t/sqlite- error-and-tasks-stuck/199/10 as patching the current version with the patch available doesn’t fix the problem.
Any clue ?
Thanks a lot !