Maximum concurrently executed VTs per host = 4
Maximum concurrently scanned hosts = 20
Depending on power- and memory resources you can adjust these values.
What exactly do you mean with “stuck”?
What timeline do you refer to?
If you just see the scan running at 1%, even for a long time this does not mean it died or fell asleep. you can watch your openvassd.log to see what your scan task is currently doing. It’s not a surprise if you see this 1%, because in the beginning all the basic groundwork is done for all other vulnerability tests to follow.
Just start a scan and leave it alone. After its done you will know how long a scan takes.
I wouldnt wait for the task to complete. Maybe read the manual or articles here in between to learn what cool things you can do with this amazing software.
Hi after 3 days it was still not beyond 1%. I see that when I click 3 simultaneous task (discoveries) the service stops responding and a reboot is needed. systemctl stop gvmd is not working. So I guess the system becomes unstable as soon as load goes beyond acceptable.