My OpenVAS (Version 26.4.0 (in Docker)) started displaying the message “NVT: Synchronization issue: Could not connect to scanner to get feed info” in the Feed Status.
Checking the containers, I noticed that the “ospd-openvas:latest” container is constantly restarting. I’ve already tried rebuilding the container, but without success.
Has anyone else experienced this and can help me?
Hi, you can view the logs of your container by running the following command:
docker logs -f 2d86ee4dd183
Could you share the output ? It will help to identify what is preventing the container from starting.
Hi, it’s showing the message “ERROR: (ospd_openvas.db) Redis Error: Not possible to connect to the kb”;
Please run :
docker ps
And check whether you see a Redis container, for example:
Id registry.community.greenbone.net/community/redis-server “/bin/sh -c 'rm -f /…” 2 months ago Up 2 weeks greenbone-community-edition-redis-server-1
if you don’t see it, try starting it manually:
docker start greenbone-community-edition-redis-server-1
if it fails to start, please send me the logs so I can help diagnose the issue.
Helped
docker volume rm greenbone-community-edition_redis_socket_vol
For such problems please take a look at
for further advices.
Hey friend, for me all the containers are starting up, including “redis-server”, but I noticed that the “ospd-openvas” container is always restarting, it always has low uptime.
Hi piresand, could you take a look at the redis-server logs?
Even if the container is running, it doesn’t necessarily mean that everything is working correctly.
There might be useful information in the logs that could help us troubleshoot the issue.
Could you please share the output?
Different user here. Today I’ve seen the same problem after updating the Greenbone docker images and restarting all containers.
As a workaround, I’ve used this (based on official Greenbone documentation):
docker compose -f $DOWNLOAD_DIR/docker-compose.yml \
rm -s -f redis-server ospd-openvas
docker volume rm greenbone-community-edition_redis_socket_vol
docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d
Now the feed status is shown as ‘Current’ again. All good.
I only briefly looked at the logs and saw the same Redis error discussed above, but I understand you’d like to see more detailed logs to find the root cause. Unfortunately I can’t share logs because I already restarted the containers.
Hi Daniel. I saw that solution and already tried it, but it didn’t solve my problem.
I managed to solve the problem by following the steps below:
I restored a backup of the OpenVAS machine, where I didn’t have the problem with the feed and container restarting, but the OpenVAS version was 26.1.0.
With this backup, I only updated the feed services;
docker compose -f /root/greenbone-community-container/docker-compose.yml -p greenbone-community-edition pull \
notus-data \
vulnerability-tests \
scap-data \
dfn-cert-data \
cert-bund-data \
report-formats \
data-objects
Then I recreated the feed containers;
docker compose -f /root/greenbone-community-container/docker-compose.yml -p greenbone-community-edition up -d \
notus-data \
vulnerability-tests \
scap-data \
dfn-cert-data \
cert-bund-data \
report-formats \
data-objects
Only after ensuring that the feeds were up-to-date did I perform a full pull.
docker compose -f /root/greenbone-community-container/docker-compose.yml -p greenbone-community-edition pull
docker compose -f /root/greenbone-community-container/docker-compose.yml -p greenbone-community-edition up -d
After the full pull, OpenVAS went to version 26.6.0, but I noticed a problem with “rm: cannot remove ‘/run/redis/redis.sock’: Permission denied”, from the “redis-server” container;
To solve this problem, it was necessary to pause all containers.
docker compose down
After pausing, I removed the redis volume.
docker volume rm greenbone-community-edition_redis_socket_vol
I confirmed that redis stopped restarting and the feed status remained Current.
docker compose ps
