Option "Consider Alive" dosen't seem to be work on GVM-20.08

Hello Guys…

I’m facing off an strange situation in my fresh install of GVM-20.08.
Looks like option “Consider Alive” don’t have effect against targets that is blocking “ping tests”. Bellow a piece of log with “Consider Alive” option enabled on target:

sd main:MESSAGE:2020-09-09 19h54.00 utc:10250: The remote host 200.x.x.x is dead
sd main:MESSAGE:2020-09-09 19h54.00 utc:10250: Vulnerability scan 0fde8778-1ad3-4d20-8079-0df836f68a83 finished for host 200.x.x.x in 2.21 seconds

Searching in the forum, I found this suggestion ““Consider Alive” not working?”, that’s works fine. But, I think that option “Consider Alive” is the better way to show for my scan that hosts is online, correct? This is a issue/bug?

GVM versions

gsad: Greenbone Security Assistant 20.08.0~git
gvmd: Greenbone Vulnerability Manager 20.08.0 (Manager DB revision 233)
openvas-scanner: OpenVAS 20.8.0
gvm-libs: gvm-libs 20.8.0


Operating system: Debian GNU/Linux 10 (buster)
Kernel: Linux gvm20 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux
Installation method / source: Source code from “GVM 20.08 (stable, initial release 2020-08-12)

Thanks in advance!!!

Andre R. Landim

Hi @andre.landim,

The following patch fix the issue.



Hi, is there a simple way to install this patch?
We’re using the rpm way by atomic and so far we don’t know how to replace those files.

we did a new installation from scratch last week, and no have the “host is dead” error as well on every tasks.

You can checkout bsdiff and bspatch if you need to patch your binary or simply do a error-reporting at Atomic and request the patch to be integrated.

1 Like

Thx, error reporting is done. But i don’t know if there is an answer in time.
maybe i have to patch the binaries…