I checked it seems one user is really abusive abusing our feed services. I will block that specific user network.
1 Like
Well, in this particular case, I don’t think the feed server is actually full. Do you have any way to check ? I am asking, because I have some nodes which can no longer update since mid november, while other update without problems since then. All nodes are pointing to the latest IP address.
So I find this very unlikely that’s it’s due to a feed beeing full. Perhaps my IPs were blocked for some reasons (My nodes are configured to try updating once per day, no more)
Thank you
That user for that service was trying to sync: 2290907 times since 2021/12/29 so we blocked his source address range.
We run multiple server to sync the feed. And if all simultaneous connection are full you will get this message. If you run a commercial installation and you need a SLA you need to buy a appliance with guaranties to sync.
All decisions are still based on IPs due to GDPR we don´t have any other user information.
2 Likes
You did not read me well. I said several nodes were continuously syncing well while others (always the same) did not since mid november. How could that be that the feed servers get always full for some nodes, and never full for others, during such a long time period ?
You are perfectly right for SLA and professional feeds. I am fighting for this internally, but unfortunately, this doesn’t depend on me, sadly.
Last update; seems like blocking that network range did the trick. I just retried and now I’m able to sync on those long outdated nodes. That still doesn’t look logical to me I could update other nodes without issues, but well… at least now it works 
So thanks for blocking that rogue traffic and helping me get back in !
2 Likes
Never heard of load balancing based on source IP address 
Hi Greenbone Team,
just a short question regarding bandwith for “greenbone-feed-sync --type SCAP”.
I just get 5 kB/s
nvdcve-2.0-2012.xml
25,078,777 100% 6.33kB/s 1:04:26 (xfr#1, to-chk=33/46)
nvdcve-2.0-2013.xml
28,583,826 100% 5.00kB/s 1:33:01 (xfr#2, to-chk=32/46)
nvdcve-2.0-2014.xml
29,424,792 100% 5.00kB/s 1:35:45 (xfr#3, to-chk=31/46)
nvdcve-2.0-2015.xml
31,274,523 100% 5.00kB/s 1:41:47 (xfr#4, to-chk=30/46)
nvdcve-2.0-2016.xml
42,056,358 100% 5.00kB/s 2:16:55 (xfr#5, to-chk=29/46)
nvdcve-2.0-2017.xml
50,921,472 85% 5.00kB/s 0:29:06
This results in looooong running downloads for these few XML files. As i understood you have limited the number of connections. Did you also limit the speed? Is it possible to increase it a little or did we reach the bandwith borders?
thx
As a side note, I confirm I have experienced those bandwidth limitations to greenbone feed from various locations in the world. I don’t know if there is anything Greenbone can / want to do about this, but it’s occuring recently.
Hi Homer and welcome to the forum
It might have reached the bandwidth limit, how many simultaneous connections do you have to the server?