NVT Synchronization issue

Building from Source and Advanced Topics
1

Hello Everyone,

This is my first post in the community.

This morning, I opened the OpenVAS Web UI and noticed I was unable to run any tasks. Upon checking the Feed Status, I saw an error indicating a synchronization issue with the NVT feed.

The error message reads:
Synchronization issue: Could not connect to scanner to get feed info.

To troubleshoot, I started updating the feeds. While the feeds are updating, the NVTs are not being updated. See the screenshot below for reference:

feeds
feeds2125Ă—634 50.5 KB

Is anyone encountering this issue?
Any suggestions on how to resolve it would be greatly appreciated!

Thanks.

Best,
Nick

1 Like
2

Same problem here. Anyone have any ideas on how to resolve?
Thanks.

3

Hi,

Please check if your scanner is running or killed by OOM or the process crashed.

4

Update:

During troubleshooting, I found that the /run/ospd/ospd-openvas.sock file was missing, and a feed-update.lock file was in its place.

To resolve, I removed the feed-update.lock file and re-pulled all OpenVAS containers, ensuring that I did not remove any volumes. This preserved the database records and previous scan data, and restored the ospd-openvas.sock file.

Afterward, I updated the feed, and the update completed successfully.

For safety, I recommend making a backup or taking a snapshot of the VM before performing similar actions.

5

Hi @nickvas I’ve exactly the same problem, every time I restart the host.
Do you running Greenbone via docker? I’m running it via Docker on Debian (VM). Do you know how to get to the /run/ospd/feed-update.lock file inside docker?

Update
After the following command, the error message disappear (Status = Current):
docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d

After this command I can connect to the ospd-openvas terminal with this command:
docker compose -f $DOWNLOAD_DIR/docker-compose.yml exec ospd-openvas /bin/bash
Inside run/ospd/ I found feed-update.lock and ospd-openvas.sock and removed the lock file (rm feed-update.lock). But after a reboot the error message still appears. Why Service “ospd-openvas” is not running after reboot? Do I have to run the pull and up commands after a reboot?

Run this command to set the Download dir var.
export DOWNLOAD_DIR=$HOME/greenbone-community-container && mkdir -p $DOWNLOAD_DIR

6

@nickvas I think it cannot connect to ospd-openvas. so you must fix that service.

Eero

7

Thats correct because the service is not running. But why? I followed the official instructions to install Docker on a fresh Debian VM.

I can start the service manually with this command:
docker compose -f $DOWNLOAD_DIR/docker-compose.yml restart ospd-openvas

Update:

8

The logs should give you some hints about the issue

docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs ospd-openvas
1 Like
9

I’d already looked at the log. But it only says:
(ospd.main) Shutting-down server …
And that’s it. After a reboot, it doesn’t start. Maybe that’s because I’m running Debian in a VM. Now I have a check and restart script. This works.

10

THIS is the fix: Docker ospd-openvas not starting at boot - #7 by voron