Scan Process Error and Interupted 0%

[RichieRich]

I have read some of the other post about Interrupted 0% and have left the system run for over 12 hrs. When I check the GVMD.log file I see all the item have been completed. All services are up and running. I have rebooted the system and tried and still the same process.
gvmd.log:
d main:MESSAGE:2023-05-03 08h41.33 utc:1046: Greenbone Vulnerability Manager version 22.4.2 (DB revision 250)
md manage: INFO:2023-05-03 08h41.35 UTC:1087: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h41.45 UTC:1813: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h41.55 UTC:1847: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h42.05 UTC:1883: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h42.15 UTC:1917: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h42.25 UTC:1922: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h42.35 UTC:1926: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h42.45 UTC:1959: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h42.55 UTC:1996: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-05-03 08h43.05 UTC:2000: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md main:MESSAGE:2023-05-03 08h52.01 utc:3383: Greenbone Vulnerability Manager version 22.4.2 (DB revision 250)
md manage: INFO:2023-05-03 08h52.01 utc:3383: Getting users.
md main:MESSAGE:2023-05-03 08h52.02 utc:3389: Greenbone Vulnerability Manager version 22.4.2 (DB revision 250)
md manage: INFO:2023-05-03 08h52.02 utc:3389: Modifying setting.
event task:MESSAGE:2023-05-03 07h13.02 EDT:7322: Status of task Laptop (5f6056e6-6e02-4cf9-a1f2-3cede16f2bca) has changed to Requested
event task:MESSAGE:2023-05-03 07h13.02 EDT:7322: Task Laptop (5f6056e6-6e02-4cf9-a1f2-3cede16f2bca) has been requested to start by admin
event task:MESSAGE:2023-05-03 07h13.25 EDT:7325: Status of task Laptop (5f6056e6-6e02-4cf9-a1f2-3cede16f2bca) has changed to Queued
event task:MESSAGE:2023-05-03 07h13.35 EDT:7325: Status of task Laptop (5f6056e6-6e02-4cf9-a1f2-3cede16f2bca) has changed to Running
event task:MESSAGE:2023-05-03 07h14.05 EDT:7325: Status of task Laptop (5f6056e6-6e02-4cf9-a1f2-3cede16f2bca) has changed to Interrupted

ospd-ovenvas.log:
OSPD[889] 2023-05-03 08:41:15,040: INFO: (ospd.main) Shutting-down server …
OSPD[975] 2023-05-03 08:41:32,036: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.6.
OSPD[975] 2023-05-03 08:41:32,039: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[975] 2023-05-03 08:41:42,084: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[975] 2023-05-03 08:42:40,812: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 0 to 202305021011.
OSPD[975] 2023-05-03 11:13:25,451: INFO: (ospd.command.command) Scan 49075f5c-0640-4058-8500-991815179323 added to the queue in position 2.
OSPD[975] 2023-05-03 11:13:31,770: INFO: (ospd.ospd) Currently 1 queued scans.
OSPD[975] 2023-05-03 11:13:31,878: INFO: (ospd.ospd) Starting scan 49075f5c-0640-4058-8500-991815179323.
OSPD[975] 2023-05-03 11:14:03,160: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Host scan finished.
OSPD[975] 2023-05-03 11:14:03,162: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Host scan got interrupted. Progress: 0, Status: RUNNING
OSPD[975] 2023-05-03 11:14:03,162: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan interrupted.
OSPD[975] 2023-05-03 11:14:05,835: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan process is dead and its progress is 0
OSPD[975] 2023-05-03 11:14:05,835: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan interrupted.
OSPD[975] 2023-05-03 11:14:05,837: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan process is dead and its progress is 0
OSPD[975] 2023-05-03 11:14:05,837: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan interrupted.
OSPD[975] 2023-05-03 11:14:05,885: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan process is dead and its progress is 0
OSPD[975] 2023-05-03 11:14:05,886: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan interrupted.
OSPD[975] 2023-05-03 11:14:05,909: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan process is dead and its progress is 0
OSPD[975] 2023-05-03 11:14:05,909: INFO: (ospd.ospd) 49075f5c-0640-4058-8500-991815179323: Scan interrupted.

Should I be concerned that in the ospd-openvas.log that when I restart the system I still get the “The VT cache has been updated from version 0 to 202305021011” and that it hasn’t changed from “version 0 to” .

This is a fresh install and I am running Ubuntu 22.04 which is also a fresh install, running on a laptop NOT in a VM. By the way, get the same error in a VM as well.

I feel like something is not set correctly or there is a rights issue somewhere. Please help me to find what I am missing. To make things a bit harder, I am a newbie in regards to Ubuntu as the base OS.

Thank you for your help.

[bricks]

Hi, could you take a look at the Error Messages tab in the report?

[RichieRich]

Sorry here is the screenshot. I have also included the gvmd.log as well as the ospd-openvas.log.

[bricks]

If you get osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting you can’t run a scan because ospd-openvas and gvmd are not ready yet. You will get that message when ospd-openvas is (re)started and has to load all VT meta data from the nasl and notus files into the redis database. If ospd-openvas has loaded this VT meta data, gvmd needs to synchronize it. Only if both steps are done you can scan successfully. You can find that even more detailed in the source build docs at https://greenbone.github.io/docs/latest/22.4/source-build/index.html#vulnerability-tests-data

[RichieRich]

I have left the system run for over 12 hours (overnight) and still at the same point. Is there something which I can check to see that it is building. I would have expected it to have been synchronize by now.

Am I missing something or should I be checking something to make sure it is synchronizing?
gvmd.log (26.1 KB)

When I check this log, I see all the items have succeeded. This is what I don’t understand.

[RichieRich]

I think I have solved this. I stopped all services and then started them up and then forced a new resync of the VTs. This seemed to get everything going again.

[RichieRich]

still getting the same error.

There has to be something I am doing very basically wrong. Ahrrrr

[bricks]

Scan interrupted. is most likely caused by an issue with ospd-openvas. From your screenshots at Scan Process Error and Interupted 0% - #3 by RichieRich it is obvious that ospd-openvas was still loading the VTs and not ready yet. Same for the gvmd.log file at Scan Process Error and Interupted 0% - #5 by RichieRich

Personally I would try the following steps:

• Stop gvmd and ospd-openvas
• Delete the ospd-openvas.log, gvmd.log and openvas.log files in /var/log/gvm
• Restart gvmd and ospd-openvas.log
• Look at the ospd-openvas.log file and wait until the message Finished loading VTs. The VT cache has been updated from version X to Y. appears
• Look at the gvmd.log file and wait until the message Updating VTs in database ... done (X VTs). appears

Just to note: loading the VTs is done on every startup of gvmd and ospd-openvas!

[RichieRich]

Thank you for that information. I followed what you suggested and after I deleted the old log files, with all 4 services stopped (Notus-scanner, ospd-openvas, gmvd ,gsad), I did a feed sync and then started each service one at a time. After I started the ospd-openvas, I waited until I received the “Finished loading VTs. The VT cache has been updated from version 202305031011 to 202305041214.” Then and only then did I start the gvmd. I again waited until OSP, SCAP and Cert all were updated. Then I waited a bit longer then started the gsad. Left that along for about 1 hour then I logged into the GSA and started to do a scan. When I did that, I received the same error. This time I looked at the openvas.log file where I found the following warnings:

set_socket: failed to open ICMPV4 socket: Operation not permitted
start_alive_detection. Boreas could not initialise alive detection. Boreas was not able to open a new socket. Exit Boreas.
Vulnerability scan f758971d-e6b6-4465-a3b7-96909374ec62 finished in 4 seconds: 0 alive hosts of 1

So it appears that I have something else going on. In looking through the forum, I found something saying that I needed to add the following path in the sudoers.tmp file “/opt/gvm/sbin”.

I made this change but still have the same error (this was done prior the prior day).

Attached please find my screenshots.

Thank you so much for all your help.

Rich