I had a linux server running openvas actively for quite some time now and everything was working fine until now. My configuration is as follow:
Linux mint 18.3 Sylvia 64bits
Openvas 8 (scanner 5.0.7, manager 6.0.9)
Last week I was running a scanning campaign against several networks and everything went well until two days ago where I noticed my scans were stucked at various percentages, without progressing anymore.
Looking at both openvasmd and openvassd logsfiles gave me the following last messages:
md main:WARNING:2018-11-11 11h10.42 CET:6270: NVT ‘184.108.40.206.4.1.256220.127.116.11800’ not found. Result not created.
md main:WARNING:2018-11-11 11h10.46 CET:6270: NVT ‘18.104.22.168.4.1.25622.214.171.124800’ not found. Result not created.
[Sun Nov 11 09:59:54 2018] WARNING: Cannot connect to KB at ‘/var/run/redis/redis.sock’: Connection refused’
[Sun Nov 11 09:59:55 2018] WARNING: Cannot connect to KB at ‘/var/run/redis/redis.sock’: Connection refused’
So I restarted redis, openvas scanner and openvas manager and then I cannot resume my tasks anymore. If I try to run a task via omp, it gets stuck forever…
I know that in the past similar problems were often due to a configuration issue with redis, so I checked that and my redis settings are correct. It’s socket-listening and my redis save settings are:
save 900 1
save 300 10
save 60 10000
So really everything looks fine. I tried to rebuild openvasmd database with --rebuild parameter, but here also openvasmd gets stuck forever.
So really, openvasmd seems unable to talk to openvassd processes anymore.
I would appreciate if any of you guys would have any clue on this, as I’m currently stucked into a quite important campaign for my network !
Thanks guys, fixing redis configuration did the trick. My apologizes for this , for whatever reason I actually thought that those settings had to be commented out to avoid the redis problem, not the other way. I’m getting old, my memory is leaking…
Yes, I know openvas 8 is EOL. Problem is I can’t upgrade by now as I have written many scripts for reports generations which worked with omp but doesn’t with gvm. So I need to fix those first. But it’s definitely in my todo list.