search

immauss / openvas

Containers for running the Greenbone Vulnerability Manager. Run as a single container with all services or separate single applications containers via docker-compose.
GNU Affero General Public License v3.0
360 stars 102 forks source link

Scan remain 15 minutes on queued instead of start immediately #112

Closed JoseW3b closed 2 years ago

JoseW3b commented 2 years ago

Hi everybody,

anyone knows if there is some reason why the scan doesn't start immediately??? it runs over last immauss docker. After that 15 minutes it start and ends correctly. docker has enough resources. progress pass from requested to queued (a lot of time).

thanks in advance

immauss commented 2 years ago

Are you seeing that delay in the logs, or via the web interface? if web, check to see if the logs show the same, it could just be a delay in the web interface updating. If not, you might want to check on the community forum.

JoseW3b commented 2 years ago

It seems on first scan it waits for load redis nvts... ps aux shows a process 'openvas --update-vt-info' and another process with the progress... when it has finished, the scan starts. now I'm going to research how to preload redis with that data in a docker image.

immauss commented 2 years ago

Yes. This is normal. Once you have the most recent data from Greenbone, it goes quite a bit faster. I've preloaded relatively recent copies of the data into the base image. If you start the container with -e SKIPSYNC=true , then you should get an operational scanner much quicker.