I’m using GVM v22.04 on a Rocky Linux 9. I’m trying to scan a target that are two network IPs of our enterprise (this two contains 20 IPs). I don’t know exactly why but the scan always interrupts at 99%.
I checked the openvas.log and I see the following WARNING:
On task settings I incremented on ‘Maximum concurrently scanned hosts’ the value from 20 to 30, but it stills interrupted. As well it does not make so many sense because on the report indicates that have been scanned 15 hosts (I attach a pic showing this).
Please check your log, i would suggest you exceeded your memory and the out of memory killer was active. But this can only be investigated on system and log level.
I incremented RAM on the VM but it stills have the same issue. On the logs I only can see the same error (“pluginlaunch_wait_for_free_process: Interrupted system call (4)”) and also is interrupted at 5:00AM
I checked gvmd.log, gsad.log, openvas.log and ospd-scanner.log. This error that I indicate is the only interesting message that I saw.
I don’t see anything suspicius apparently. Nevertheless, I checked on openvas.log the following:
OSPD[857323] 2024-06-11 07:07:14,450: INFO: (ospd.ospd) Starting scan 6c2d32e4-4ccf-4a86-ab67-22110c467275.
OSPD[857323] 2024-06-11 07:27:03,145: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[857323] 2024-06-11 07:44:49,146: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 202406071641 to 202406100605.
OSPD[857323] 2024-06-12 05:00:02,188: INFO: (ospd.ospd) 6c2d32e4-4ccf-4a86-ab67-22110c467275: Stopping Scan with the PID 904036.
OSPD[857323] 2024-06-12 05:00:02,188: INFO: (ospd.ospd) 6c2d32e4-4ccf-4a86-ab67-22110c467275: Scan stopped.
OSPD[857323] 2024-06-12 05:00:02,189: INFO: (ospd.main) Shutting-down server …
OSPD[857323] 2024-06-12 05:00:02,626: WARNING: (ospd.ospd) Error sending data to the client while executing a scan 6c2d32e4-4ccf-4a86-ab67-22110c467275.
OSPD[1995358] 2024-06-12 05:00:03,559: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.3.
OSPD[1995358] 2024-06-12 05:00:03,582: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[1995358] 2024-06-12 05:00:13,638: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[1995358] 2024-06-12 05:00:13,877: INFO: (ospd_openvas.notus) hashsum verification is disabled
OSPD[1995358] 2024-06-12 05:34:02,359: INFO: (ospd_openvas.daemon) VTs were up to date. Feed version is 202406100605.
OSPD[1995358] 2024-06-12 07:23:00,950: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
Apparently, It seems that ospd-scanner restarted at the same timestamp (5.00AM). I don’t know if I there is a cron configured because ospd-scanner conf is default.
Also I checked the log of Error Messages in the interrupted scan report and I see the following:
“Task process exited abnormally (e.g. machine lost power or process was sent SIGKILL). Setting scan status to Interrupted.”
