Scan interrupted at 98% or 99%

edv-support · February 23, 2023, 12:46pm

hello everybody,

we installed the greenbone community edition 22.4 from Soucre on a ubuntu server LTS 22.04.1.

Everything is looking fine so far but we have 4 different scans, 3 of them finished without a problem and the fourth is getting an “interrupted error” at 98% or 99%.
When i start them all at the same time, they all get an “interrupted or stopped” error, when i start them apart from each other, 3 are finishing and the fourth gets the “interrupted error” as mentioned.

I searched the forum allready but i get a differnt error message then the other members in the logs.

ospd-openvas.log

OSPD[844] 2023-02-23 08:20:22,751: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.6.
OSPD[844] 2023-02-23 08:20:22,768: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[844] 2023-02-23 08:20:33,019: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[844] 2023-02-23 08:21:28,960: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 0 to 202302221011.
OSPD[844] 2023-02-23 08:27:47,982: INFO: (ospd.command.command) Scan 8941a794-c5ec-45d5-b411-160792101889 added to the queue in position 2.
OSPD[844] 2023-02-23 08:27:54,863: INFO: (ospd.ospd) Currently 1 queued scans.
OSPD[844] 2023-02-23 08:27:54,993: INFO: (ospd.ospd) Starting scan 8941a794-c5ec-45d5-b411-160792101889.
OSPD[844] 2023-02-23 09:09:40,970: ERROR: (ospd.server) Error sending data to the client. [Errno 32] Broken pipe
OSPD[844] 2023-02-23 09:09:46,199: ERROR: (ospd.server) Error sending data to the client. [Errno 32] Broken pipe
OSPD[844] 2023-02-23 09:09:51,333: ERROR: (ospd.server) Error sending data to the client. [Errno 32] Broken pipe
OSPD[844] 2023-02-23 09:09:56,543: ERROR: (ospd.server) Error sending data to the client. [Errno 32] Broken pipe
OSPD[844] 2023-02-23 11:03:45,313: ERROR: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Exception Error while reading from socket: (104, ‘Connection reset by peer’) while scanning
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/redis/connection.py”, line 198, in _read_from_socket
data = recv(self._sock, socket_read_size)
File “/usr/lib/python3/dist-packages/redis/_compat.py”, line 72, in recv
return sock.recv(*args, **kwargs)
ConnectionResetError: [Errno 104] Connection reset by peer

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/local/lib/python3.10/dist-packages/ospd/ospd.py”, line 596, in start_scan
self.exec_scan(scan_id)
File “/usr/local/lib/python3.10/dist-packages/ospd_openvas/daemon.py”, line 1198, in exec_scan
got_results = self.report_openvas_results(kbdb, scan_id)
File “/usr/local/lib/python3.10/dist-packages/ospd_openvas/daemon.py”, line 819, in report_openvas_results
all_results = db.get_result()
File “/usr/local/lib/python3.10/dist-packages/ospd_openvas/db.py”, line 509, in get_result
return self._pop_list_items(“internal/results”)
File “/usr/local/lib/python3.10/dist-packages/ospd_openvas/db.py”, line 493, in _pop_list_items
return OpenvasDB.pop_list_items(self.ctx, name)
File “/usr/local/lib/python3.10/dist-packages/ospd_openvas/db.py”, line 207, in pop_list_items
results, redis_return_code = pipe.execute()
File “/usr/lib/python3/dist-packages/redis/client.py”, line 4019, in execute
return execute(conn, stack, raise_on_error)
File “/usr/lib/python3/dist-packages/redis/client.py”, line 3894, in execute_transaction
self.parse_response(connection, '')
File “/usr/lib/python3/dist-packages/redis/client.py”, line 3977, in parse_response
result = Redis.parse_response(
File “/usr/lib/python3/dist-packages/redis/client.py”, line 915, in parse_response
response = connection.read_response()
File “/usr/lib/python3/dist-packages/redis/connection.py”, line 739, in read_response
response = self._parser.read_response()
File “/usr/lib/python3/dist-packages/redis/connection.py”, line 324, in read_response
raw = self._buffer.readline()
File “/usr/lib/python3/dist-packages/redis/connection.py”, line 256, in readline
self._read_from_socket()
File “/usr/lib/python3/dist-packages/redis/connection.py”, line 222, in _read_from_socket
raise ConnectionError(“Error while reading from socket: %s” %
redis.exceptions.ConnectionError: Error while reading from socket: (104, ‘Connection reset by peer’)
OSPD[844] 2023-02-23 11:03:45,335: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Host scan got interrupted. Progress: 99, Status: RUNNING
OSPD[844] 2023-02-23 11:03:45,337: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan interrupted.
OSPD[844] 2023-02-23 11:03:47,098: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[844] 2023-02-23 11:03:50,028: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan process is dead and its progress is 99
OSPD[844] 2023-02-23 11:03:50,029: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan interrupted.
OSPD[844] 2023-02-23 11:03:50,033: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan process is dead and its progress is 99
OSPD[844] 2023-02-23 11:03:50,034: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan interrupted.
OSPD[844] 2023-02-23 11:03:50,138: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan process is dead and its progress is 99
OSPD[844] 2023-02-23 11:03:50,139: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan interrupted.
OSPD[844] 2023-02-23 11:03:50,886: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan process is dead and its progress is 99
OSPD[844] 2023-02-23 11:03:50,886: INFO: (ospd.ospd) 8941a794-c5ec-45d5-b411-160792101889: Scan interrupted.
OSPD[844] 2023-02-23 11:04:37,546: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 0 to None.
OSPD[844] 2023-02-23 11:04:37,587: INFO: (ospd.main) Shutting-down server …
OSPD[280594] 2023-02-23 11:05:39,146: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.6.
OSPD[280594] 2023-02-23 11:05:39,150: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[280594] 2023-02-23 11:05:49,203: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[280594] 2023-02-23 11:06:43,418: INFO: (ospd_openvas.daemon) VTs were up to date. Feed version is 202302221011.

openvas.log

sd main:MESSAGE:2023-02-23 10h53.39 utc:31732: Vulnerability scan 8941a794-c5ec-45d5-b411-160792101889 finished for host xxx.xxx.xxx.xxx in 7251.26 seconds
lib misc:MESSAGE:2023-02-23 11h02.09 utc:279345: open_sock_tcp: xxx.xxx.xxx.xxx:21 time-out.
lib misc:MESSAGE:2023-02-23 11h02.49 utc:279635: open_sock_tcp: xxx.xxx.xxx.xxx:21 time-out.
lib misc:MESSAGE:2023-02-23 11h02.49 utc:279652: open_sock_tcp: xxx.xxx.xxx.xxx:21 time-out.
lib misc:MESSAGE:2023-02-23 11h03.39 utc:280475: Function socket_negotiate_ssl called from gb_ssl_tls_renegotiation_dos_CVE-2011-1473_CVE-2011-5094.nasl: SSL/TLS connection (host: xxx.xxx.xxx.xxx, ip: xx.>
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280438: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280438: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280438: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:277049: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:277049: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:277049: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279526: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279526: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279526: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279526: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280461: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280485: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280485: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280485: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279405: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: Connection refused
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279405: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279405: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:279405: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280484: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280484: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280484: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280484: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280481: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280481: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280481: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280481: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280475: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280438: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280438: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280438: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:277049: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:277049: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:277049: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
libgvm util:CRITICAL:2023-02-23 11h03.45 utc:280473: get_redis_ctx: redis connection error to /run/redis-openvas/redis.sock: No such file or directory
lib misc:MESSAGE:2023-02-23 11h03.45 utc:280496: Function socket_negotiate_ssl called from gb_ssl_tls_renegotiation_dos_CVE-2011-1473_CVE-2011-5094.nasl: SSL/TLS connection (host: xxx.xxx.xxx.xxx, ip: x>
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.108162’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.108162’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.108162’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.108162’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.10919’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.10919’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.10919’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.19506’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.19506’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.19506’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.10919’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103739’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103739’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103739’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.19506’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103625’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103625’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103625’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103739’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.111091’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.111091’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.111091’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103625’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.108545’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.108545’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.108545’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.111091’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.108545’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.810002’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.810002’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.810002’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103962’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103962’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103962’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.810002’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.108291’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.108291’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103962’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.108291’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103963’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103963’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.108291’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103963’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103964’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103963’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103964’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103964’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103823’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103964’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103823’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103823’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103823’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.108449’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.108449’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.108449’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.103997’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.103997’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103997’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.108449’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.108442’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.108442’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.103997’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.108449’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.108442’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.108442’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.108442’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.103997’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.96171’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.96171’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.96171’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.108442’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31824: Plugin ‘1.3.6.1.4.1.25623.1.0.804787’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2532: Plugin ‘1.3.6.1.4.1.25623.1.0.804787’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.96171’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:2514: Plugin ‘1.3.6.1.4.1.25623.1.0.804787’ missing from nvticache.
sd main:MESSAGE:2023-02-23 11h03.46 utc:31839: Plugin ‘1.3.6.1.4.1.25623.1.0.804787’ missing from nvticache.
lib misc:WARNING:2023-02-23 11h03.46 utc:2532: check_kb_inconsistency_log: No internal/scanid found; abort to prevent data corruption.
lib misc:WARNING:2023-02-23 11h03.46 utc:31824: check_kb_inconsistency_log: No internal/scanid found; abort to prevent data corruption.
lib misc:WARNING:2023-02-23 11h03.46 utc:2514: check_kb_inconsistency_log: No internal/scanid found; abort to prevent data corruption.
lib misc:WARNING:2023-02-23 11h03.46 utc:31839: check_kb_inconsistency_log: No internal/scanid found; abort to prevent data corruption.
sd main:MESSAGE:2023-02-23 11h03.47 utc:2475: Vulnerability scan 8941a794-c5ec-45d5-b411-160792101889 finished in 9319 seconds: 25 alive hosts of 25
libgvm util:MESSAGE:2023-02-23 11h04.37 utc:280516: Updated NVT cache from version 0 to 202302221011

Does anybody have an idea what the problem might be? Help would be very appreciated.
Thank you for your time and help.

Best regards Matthias

bricks · February 23, 2023, 1:16pm

This message indicates that the VT data wasn’t loaded from the feed before you started the scan. That means your scanner wasn’t really ready for scanning.

This error indicates that redis-server wasn’t started/available. Without redis-server you aren’t able to scan too.

edv-support · February 23, 2023, 1:23pm

hello bricks,

thank you for the fast reply.

Does that mean i started the scan to early after a feed-syncronisation?

If i got this message at the ospd-openvas.log:

OSPD[280594] 2023-02-23 11:05:39,146: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.6.
OSPD[280594] 2023-02-23 11:05:39,150: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[280594] 2023-02-23 11:05:49,203: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[280594] 2023-02-23 11:06:43,418: INFO: (ospd_openvas.daemon) VTs were up to date. Feed version is 202302221011.

the VT data should be loaded and ready for a scan?

Can you tell me how i’m able to prof if the redis-server is ready? As i locked into the directory /run/redis-openvas/ the file redis.sock was there.

Thank you

bricks · February 23, 2023, 1:40pm

This means the scanner is ready, but it could be possible that gvmd is not.

I’ve written something about the “ready” state of the feed synchronization in our source build guide at the Performing a Feed Synchronization chapter in more detail.

I can only refer to the pasted logs and they indicate that redis-server wasn’t ready or had some issue and become ready between 11h 03.45 and 11h 03.46.

edv-support · February 24, 2023, 10:07am

hello bricks,

i need some time for research and tests. I’m going to reply next week. Have a nice weekend with
best regards Matthias

edv-support · March 2, 2023, 11:29am

hello bricks,
hello everybody,

in the meantime i conducted some tests but the resulsts are not making a lot of sense to me.
As i said before the scanner is working. I can run various tasks and they complete without an error.
But the one task fails.

The scan task that fails contains 11 targets. I suspected 2 targets to generate the error, so i removed them from the task, everything else staid the same and the scan task can now finish without an error.

When i create a separate task for each one of the before removed targets, they also complete withou an error.

But if i try to execute the original task with all the targets within it still can not finish and generates the “interrupted or stopped” error.

I got the following questions in mind:

Is there a best practice how many targets should be in one task?
Is there a limit how many targets should or could be scanned at the same time?
Maybe it does depend on the resources of the executing machine?

If anyone got some ideas, help would be appreciated.

Thank you all and best regards Matthias

Sanchous · March 3, 2023, 11:00am

HI, I can only speak from my own experience.
I had a task for 275 ips but where a month ago the task also started to stop at 22-25%, I decided to divide the scan into 3 parts of 120, 120 and 35 ips. It does not scan more than 125 hosts, although there were no problems before.
In general, the target limit for the community edition is 4096, as far as I remember

edv-support · March 9, 2023, 6:33am

hello sanchous,

thank you for the reply. Thats helpful for me and something to start with.

best regards Matthias

edv-support · March 13, 2023, 2:17pm

hello everybody,
i gave some thought to the toppic and i’m scanning a lot less ips then sanchous. max. 12. So the total number of hosts to scan should not be a problem.

best regards