For context, I've been an openvas user off and on over several years, in various contexts and build support levels (especially itiligent, love your work!)
I have tried this build on Debian 12 and 13 with the same results. 4 vCPU systems with 16GB of RAM in both AWS and GCP.
Building and deploying, and waiting on the feeds to sync...
I am able to perform discovery scans, but scan configs that include NVT always time out on the NVT step.
The report logs these errors:
NVT timed out after 1200 seconds.
Research indicates there may be a resource issue, such as number of CPUs, amount of RAM, network connectivity issues, etc. I've systematically eliminated these by temporarily increasing up to 32GB of RAM, and decreasing concurrent scans to 1 (from 4); and verified good connectivity using nmap to scan from the openvas host to the target.
I suspect the NVT scanner is having some kind of problem, but I don't see anything in the relevant logs (syslog, /var/log/g*, etc).
Help?
Thanks,
Josh
For context, I've been an openvas user off and on over several years, in various contexts and build support levels (especially itiligent, love your work!)
I have tried this build on Debian 12 and 13 with the same results. 4 vCPU systems with 16GB of RAM in both AWS and GCP.
Building and deploying, and waiting on the feeds to sync...
I am able to perform discovery scans, but scan configs that include NVT always time out on the NVT step.
The report logs these errors:
NVT timed out after 1200 seconds.
Research indicates there may be a resource issue, such as number of CPUs, amount of RAM, network connectivity issues, etc. I've systematically eliminated these by temporarily increasing up to 32GB of RAM, and decreasing concurrent scans to 1 (from 4); and verified good connectivity using nmap to scan from the openvas host to the target.
I suspect the NVT scanner is having some kind of problem, but I don't see anything in the relevant logs (syslog, /var/log/g*, etc).
Help?
Thanks,
Josh