I’ve built my system using container with the Greenbone Community Containers 22.4 - Greenbone Community Documentation scripts. All seems to go right. After a while, the feeds are on current state. But i cant make a scan of my host or my host network address.
The scans are interrupted with 0%, and the gvmd.log dont displays too much info:
root@91ba2e658a5e:/var/log/gvm# tail gvmd.log
event task:MESSAGE:2023-12-18 10h06.19 UTC:2140: Status of task Immediate scan of IP 10.34.29.105 (41c48fd6-1979-4d41-8a39-0cf1c0170ea7) has changed to Running
event task:MESSAGE:2023-12-18 10h07.00 UTC:2140: Status of task Immediate scan of IP 10.34.29.105 (41c48fd6-1979-4d41-8a39-0cf1c0170ea7) has changed to Interrupted
event target:MESSAGE:2023-12-18 10h26.03 UTC:2724: Target anfitrion (7bfa4e3b-db35-4b5b-9086-2f180d46cfee) has been created by admin
event task:MESSAGE:2023-12-18 10h26.33 UTC:2748: Status of task (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has changed to New
event task:MESSAGE:2023-12-18 10h26.33 UTC:2748: Task Prueba (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has been created by admin
event task:MESSAGE:2023-12-18 10h26.55 UTC:2778: Status of task Prueba (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has changed to Requested
event task:MESSAGE:2023-12-18 10h26.55 UTC:2778: Task Prueba (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has been requested to start by admin
event task:MESSAGE:2023-12-18 10h26.55 UTC:2781: Status of task Prueba (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has changed to Queued
event task:MESSAGE:2023-12-18 10h27.05 UTC:2781: Status of task Prueba (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has changed to Running
event task:MESSAGE:2023-12-18 10h27.11 UTC:2781: Status of task Prueba (2cf1cd68-55d8-4c83-9b5e-d3eb8846dc71) has changed to Interrupted
I’ve used the scan task wizard, and tested with my host network with CIDR form (x.x.x.x/24) and also the host ip itself. Both with same result
Can anyone help?
These are the containers running:
administrador@UDSK22-LUISMA:~/greenbone$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
66c6e4afa56f greenbone/gsa:stable "/usr/local/bin/entr…" 2 hours ago Up 2 hours 127.0.0.1:9392->80/tcp greenbone-community-edition-gsa-1
91ba2e658a5e greenbone/gvmd:stable "/usr/local/bin/entr…" 2 hours ago Up 2 hours greenbone-community-edition-gvmd-1
f5ad4b4d8732 greenbone/ospd-openvas:stable "/usr/bin/tini -- /u…" 2 hours ago Up 2 hours greenbone-community-edition-ospd-openvas-1
bb6fe655f010 greenbone/redis-server "/bin/sh -c 'rm -f /…" 2 hours ago Up 2 hours greenbone-community-edition-redis-server-1
18383bed469e greenbone/pg-gvm:stable "/usr/local/bin/entr…" 2 hours ago Up 2 hours greenbone-community-edition-pg-gvm-1
f65b181259b1 greenbone/mqtt-broker "/bin/sh -c 'mosquit…" 2 hours ago Up 2 hours greenbone-community-edition-mqtt-broker-1
I’ve made an installation from scratch and building composer yml following the manual steps. The result is the same. All scans are interrupted on 0%:
I can’t scan my local network, neither my localhost.
nbone-community-edition-gvmd-1 | event task:MESSAGE:2023-12-22 09h14.48 UTC:6224: Status of task Immediate scan of IP 10.34.29.105 (1bc63609-3451-4c5c-a8e4-01487f601e53) has changed to Running
greenbone-community-edition-mqtt-broker-1 | 1703236521: New connection from 172.18.0.4:38024 on port 1883.
greenbone-community-edition-mqtt-broker-1 | 1703236521: New client connected from 172.18.0.4:38024 as 37b824ac-82a9-4987-a2de-20182a3df402 (p5, c1, k0).
greenbone-community-edition-mqtt-broker-1 | 1703236526: Client 37b824ac-82a9-4987-a2de-20182a3df402 closed its connection.
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:27,093: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Host scan finished.
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:27,095: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Host scan got interrupted. Progress: 0, Status: RUNNING
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:27,096: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan interrupted.
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,066: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan process is dead and its progress is 0
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,066: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan interrupted.
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,070: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan process is dead and its progress is 0
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,071: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan interrupted.
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,102: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan process is dead and its progress is 0
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,102: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan interrupted.
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,130: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan process is dead and its progress is 0
greenbone-community-edition-ospd-openvas-1 | OSPD[7] 2023-12-22 09:15:29,130: INFO: (ospd.ospd) e1e76f50-048c-482d-a5b3-1a6eb8cae60b: Scan interrupted.
greenbone-community-edition-gvmd-1 | event task:MESSAGE:2023-12-22 09h15.29 UTC:6224: Status of task Immediate scan of IP 10.34.29.105 (1bc63609-3451-4c5c-a8e4-01487f601e53) has changed to Interr
Hi mcventur, and welcome to the Greenbone community
Some things to look at:
Are your feeds properly loaded into the scanner? Are they up to date? You can check the feed status under Administration > Feed Status.
In the scan report, you can check the tab Error Messages, which will tell you which errors occured (if any) during the scan.
Check the scanner’s logs at /var/log/gvm/openvas.log and /var/log/gvm/ospd-openvas.log. If there’s something like OpenVAS Scanner failed to load VTs or Updating VTs failed, you should update the feeds and, if necessary, restart the scanner. It can take some time for the scanner to load the VTs.
Al feeds are in current state in the feeds section.
In the scan repots, the error tab hardly any information is shown:
Scan process Failure
Scan process Failure
Task interrupted unexpectedly
In the openvas.log there is interesting info:
libgvm boreas:WARNING:2023-12-22 10h22.01 utc:115: set_socket: failed to open ARPV6/ICMPV6 socket: Address family not supported by protocol
libgvm boreas:WARNING:2023-12-22 10h22.01 utc:115: start_alive_detection. Boreas could not initialise alive detection. Boreas was not able to open a new socket. Exit Boreas.
My machine has disabled the IPV6 protocol. It’s possible to configure an scanner to use only IPv4?
I’ve tasked the search function and have seem to found the issue; the alive detection doesn’t work if IPv6 is disabled. Therefore, you have the options to:
Re-enable IPv6
Set the alive detection to “Consider alive”, which will drastically increase scan time if you have an IP range as target that contains not alive hosts.
