"Ping host" NVT alive detection stuck

I’m trying to detect alive hosts inside my network in order to run scan on them using “Alive Test”: “Scan Config Default” and “Ping host” NVT. With default NVT preferences it can’t found alive hosts at all, so i’ve changed option “nmap: try also with only -sP” and “Mark unrechable Hosts as dead (not scanning)” to “yes”. With that configuration actual alive hosts are detected properly, but scan gets stuck on 2% for IP that is actually down/never existed. Any suggestions on what can cause that issue or what kind of additional information could be useful for this issue?
GVM version 20.08 build from source (inside docker containers) is used.
Default “OpenVAS Default” scanner is used.
Targets with single IP are used for each task (alive and unreachable).
Network topology: single router, both machines are in same subnet ( and, target is Windows 10 machine, for unreachable target is used (there was no usage of that IP previously).
Direct nmap command results (run inside container with ospd-openvas):

gvm@pt-openvas:/$ nmap -sP
Starting Nmap 7.70 ( https://nmap.org ) at 2022-03-25 09:53 UTC
Nmap scan report for
Host is up (0.0037s latency).
Nmap done: 1 IP address (1 host up) scanned in 2.22 seconds

gvm@pt-openvas:/$ nmap -sP
Starting Nmap 7.70 ( https://nmap.org ) at 2022-03-25 09:57 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.02 seconds

Hi @Timofey and welcome to the forum :slight_smile:

I’ve moved this to the Greenbone Source Edition category for better visibility and I’d also like to point you to information on the current versions of the modules for GVM here
(20.08 is End of Life): GVM Release Version 21.4.4