Greenbone feed not getting updated to current status

The greenbone feed update is not done completely . The update process completes after one sync itself . There is no error after the command execution either .Below is the scapdata-sync execution .
Greenbone community feed server -
This service is hosted by Greenbone Networks -

All transactions are logged.

If you have any questions, please use the Greenbone community portal.
See for details.

By using this service you agree to our terms and conditions.

Only one sync per time, otherwise the source ip will be temporarily blocked.

receiving incremental file list
13 100% 1.59kB/s 0:00:00 (xfr#1, to-chk=0/1)

sent 43 bytes received 113 bytes 24.00 bytes/sec
total size is 13 speedup is 0.08

So as of now the feed has not been updated since 22 days .

Can I know the solution for this issue ?
openvas installed details
gsa - 7.0.3
openvas-manager -7.0.3
openavs-scanner - 5.1.3

We update the database everytime before the scan .Facing this issue for the first time.


Hey Gangambika,

this happened 22 days ago:

Hi @_OR

As a workaround for now ,I have patched new URL in the sync routines as mentioned in the topic you pasted . But that seems to be not working .
What is the latest revision we should be updated to ?
Or the feed updates will be provided post September 30th ?

In fact is not reachable .



you are using an outdated and unsupported version of our software. It may be possible that the feed is incompatible with the version you are using. Please update at least to GVM 11 or even better GVM 20.08 (stable, initial release 2020-08-12)

1 Like


Thanks for response .
But we also have version GVM 11 installed . And I made the URL changes in the sync routines . But that seems to be not working .

New observation : NVT feed status has disappeared .

Installed version details :
GVM Libraries 11.0.0
OpenVAS 7.0.0
OSPd 2.0.0
ospd-openvas 1.0.0
Greenbone Vulnerability Manager 9.0.0
Greenbone Security Assistant 9.0.0
OpenVAS SMB 1.0.5

Can I know the issue please ?

If no NVT feed status is showing up there then this means the greenbone-nvt-sync command isn’t working anymore / doesn’t return the expected data. I guess some syntax error or similar slipped in while doing the URL changes in the sync routines.

Instead of manually editing the files it is recommended to update this outdated versions:

to the more recent ones listed here:

So, I seem to be unable to see the new feed system.

using: 20.08.0, Manager DB revision 223

any assistance would be great.

thank you.

feed openvas org is pingable and traceable all the way
80 157 131 229
po1-2064 ccr1 whp26 fra iag eu
dl greenbone net

feed community greenbone net “failed to connect to feed community greenbone net”
Ping fails
tracing fails after:
80 157 131 229

I think something is down today.

I get rsync: failed to connect to ( Connection refused (111)

That is telling you nothing, we have a Enterprise Firewall before the new feed server. You need to check the service port with rsync or try to do a TCP connect with netcat.

1 Like

Please check your firewall and other active network components.

1 Like