Openvassd SIGSEGV when launching a task

[schnix]

Good day,

openvassd segfaults when launching a scan. Excerpt from openvassd.log:
sd main:MESSAGE:2019-07-18 13h04.21 utc:9623: Starts a new scan. Target(s) : <list of 221 targets>, with max_hosts = 5 and max_checks = 2
base hosts:WARNING:2019-07-18 13h04.23 utc:9623: Couldn’t resolve hostname (null)
sd main:WARNING:2019-07-18 13h04.31 utc:9623: SIGSEGV occurred!

No problems scanning a list of 1-3 targets yet. Crashfactor is unknown to me. All hostnames are valid, except two did not resolve to an IP at the time of the scan.

GVM versions

gsa: (‘gsad --version’) 8.0.0
gvm: (‘gvmd --version’) 8.0.0 Manager DB revision 205
openvas-scanner: (‘openvassd --version’) 6.0.0
gvm-libs: I don’t think I have that? No idea how to find out.

Environment

Operating system: Ubuntu 18.04
Kernel: (‘uname -a’) 4.15.0-1043-aws
Installation method / source: https://launchpad.net/~mrazavi/+archive/ubuntu/gvm

[cfi]

This might be a duplicate of the following existing topic:

Openvas-scanner 6.0 dies with segfault for too many hosts

Hi, the update to OpenVAS Scanner 6.0 broke one of my scan jobs. On closer inspection, /var/log/gvm/openvassd.log shows that the scanner tries to resolve interesting host names and subsequently falls over: [...] base hosts:WARNING:2019-05-24 09h09.08 utc:27074: Couldn't resolve hostname 0 base hosts:WARNING:2019-05-24 09h09.08 utc:27074: Couldn't resolve hostname base hosts:WARNING:2019-05-24 09h09.09 utc:27074: Couldn't resolve hostname ) $|crea1 sd main:WARNING:2019-05-24 09h09.09 utc:270…

[schnix]

This indeed looks like this is the case. Thank you very much for noticing!
I’ll keep track of that issue then.

[cfi]

So let’s close this as a duplicate then. I have added a short note about the availability of a new maintenance release to that topic which might already include a fix. Further questions around this topic could be asked in the linked topic as well.