I’m using the new containter 24.10 that was installed 3 days ago and already were scans.
Yesterday I detected that I can’t start the new scan and there is the message “Please wait while the feed is syncing. Scans are not available during this time. For more information, visit the Documentation.”.
I waited around ~10 hours and nothing changed.
I’m not sure if this behaviour is ok, how can I troubleshoot or check if it work as expected and not stuck?
Hey @test_qweqwe!
We would need to see the logs, to see if something is odd.
But in your case you may want to start from scratch again and reinstall it, as you probably do not have any data to loose?
Yeap, I have nothing to loose. But I have already install everything from scratch on the same server and this issue is persist. Maybe, I don’t remove everything.
How I removed it:
docker compose down --volumes --remove-orphans
docker image prune -a
docker system prune -a --volumes
Then I run the script from guide that autoinstall everything. Then I down all containers and changed the yaml file (changed from localhost to internal IP) and again
docker compose up -d
What logs do you need? Where I can find them?
@y0urself How can I send this logs? Or were I can upload it? I can’t attach .txt file or I can’t put this text here because of limit text restriction.
But from what I see based on grep | error:
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | createuser: error: could not connect to database template1: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | createdb: error: could not connect to database template1: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
pg-gvm-1 | psql: error: FATAL: the database system is starting up
I did this:
docker compose down -v
docker compose -f docker-compose.yml pull
docker compose -f docker-compose.yml up -d
and I don’t see anymore errors expept:
gvmd-1 | libgvm util:MESSAGE:2025-05-14 16h59.51 utc:19: error searching for OpenPGP key ‘GVM Credential Encryption’: Not found
and still have issue with: Feed is currently syncing.
But I checks logs and I see that updating is still in progress and nothing stuck, so I will just wait.
This is strange, when I first install it, it was working from the start without any sync and so on.
The message “Feed is currently syncing.” means the system is updating the latest content. Please wait a moment for the feed to refresh and display new information.
same issue. have you already fixed it?
im looking at options like rescheduling the auto sync but cant find any documentation about it
Just to summarize the topic heading (again): If it says “Feed is currently syncing” it means our management daemon gvmd is loading the feed content into the postgresql database. This may take a while especially for the initial startup. Check the logs of the gvmd container to get further information and some progress messages.
