"Feed is currently syncing."

Community Containers
1

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.

image
image2187×479 38.7 KB

I’m not sure if this behaviour is ok, how can I troubleshoot or check if it work as expected and not stuck?

1 Like
2

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?

3

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?

4

See the documentation.

e.g.:

docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs
5

@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

6

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.

7

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.

8

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.

1 Like
9

same issue. have you already fixed it?

im looking at options like rescheduling the auto sync but cant find any documentation about it

10

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.

4 Likes
11

yep, same here. had all feeds upgraded on today’s date (did this today). Guess what, tried another scan TODAY and got the same warning. I added a SS to show proof that feeds are updated. NVT shows its updated to today.

2025-08-01_20-07
2025-08-01_20-072472×427 53.7 KB

Pls a solution guys

12

Hi @cyberic and welcome to the forum. What does the feed status page show (the one with the version numbers)?

13

Hi there, thx for the response. De feedstatus is like the post in the first message in this thread. It says Update in progress…. This while the update was done and completed earlier that day

1 Like
14

The Feed status page also has the info on the exact version of the feed that it’s retrieving (or in current use) so that information is important to see if it’s actually trying to update from an older version (going by the feed version number, not by the date it was run). So if you can post a screenshot of your current feed status we can look at the version numbers to see if it’s syncing normally.

15

Did i not send a screenshot in my post with the proof (sync IS doing its job -btw this takes loads of time, even hrs) of that? It states that the status of feed is august 1, 2025

16

@cyberic it takes lot of time. depending your disk and cpu and ram.

Eero

17

It does, but thats not the issue here. Im very willing to raise the ‘time’ issue if you want, and indeed i should do in future (thx for the reminder).

Lets focus on THIS issue ONLY for now (capitals are intentional in hoping to get some understanding):

  1. I upgraded ALL feeds. I had to because i CANT start a scan task if this is not done. Which makes you wonder why. Task should be able to start even WITHOUT an update to current feeds date, dont they? Im very fine with running a test with a 3 days (or even more) lag. Why cant i DO THIS?
  2. I wanted to do a new scan later that day. i CANT start that, because im in some sort of upgrading proces AGAIN (literally just a couple of hours later)
  3. So here is the MAIN issue: my feeds are updated to today, why can i NOT start a scan? Or even choose to have a scan with the feeds from yesterday, or the day before or even further back? Im BLOCKED by the updates running,

Again, get this fixed pls. Your app is simply NOT working for common use.

18

Few notes to avoid some possible misunderstandings:

  • @Eero is a community user without any relation to Greenbone. If there is actually something to fix here he is very unlikely able to fix anything
  • IIUC such a “Feed is currently syncing” problem should have been already solved many months ago (April 2025) in / via Fix: Use shared lock in get_feed_lock_status by timopollmeier · Pull Request #2414 · greenbone/gvmd · GitHub
  • For anyone posting a “i have the same problem” be aware that this thread / category is about the official Docker community containers provided by Greenbone
  • If you are NOT using these Docker community containers please create a new thread and provide more information on your environment, the used versions of the software stack and the install method
  • Before creating a new thread it would also make sense to check if you are using the latest releases of the software stack (e.g. Kali is known to lag behind a lot concerning up2date versions)
2 Likes
19

Thx for your response. I was not aware that this bug was fixed already, and thanks very much for that. I will install the latest version shortly and let you know if the issue still persist.

1 Like
20

My additional two cents besides the notes from @cfi

  • Please be aware that feed sync means two things:
    1. download of the feed content from our feed severs
    2. loading of the feed content by gvmd into the postgres db and openvas scanner into the redis store
  • Only the second part results in the “Update in progress” message at the feed page
  • The second part is started automatically if gvmd and/or openvas scanner detect changes in the feed content
  • While the feed content is loaded into the db, scans should not be run and the UI ensures that in current versions of GSA
  • If the feed content has been loaded is indicated at the feed status page in the UI or via the <get_feeds/> GMP command.
  • If there are issues, for example the loading of the feed content takes a long time, you need to look at the logs. especially the gvmd log (docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs gvmd)
  • There were some issues with the feed status because of locking file problems which @cfi already mentioned and are improved in current versions of our software
  • You can always stop all services and remove all volumes besides the greenbone-community-edition_psql_data_vol volume without losing data. all other volumes will be re-created automatically and filled with the necessary data
  • Removing the *_socket_vol volumes may fix some nasty permission issues caused by bugs in your docker installation
1 Like