fsync: failed to connect to feed.openvas.org (89.146.224.58)

https://community.greenbone.net/t/community-feed-url-consolidation/5338

服务器地址更新了，原有地址 feed.openvas.org 更新为新地址 feed.community.greenbone.net

需要修改相应命令的URL:

vim /usr/sbin/greenbone-nvt-sync

vim /usr/sbin/greenbone-scapdata-sync

vim /usr/sbin/greenbone-certdata-sync

root@gors:~# cat /usr/bin/openvas-setup

#!/bin/bash

openvas-manage-certs -V 2>/dev/null

if [ $? -ne 0 ]; then

openvas-manage-certs -a

greenbone-nvt-sync

greenbone-scapdata-sync

greenbone-certdata-sync

service openvas-manager stop

service openvas-scanner stop

openvassd

openvasmd --migrate

openvasmd --rebuild

killall openvassd

sleep 15

service openvas-scanner start

service openvas-manager start

service greenbone-security-assistant restart

if ! openvasmd --get-users | grep -q ^admin$ ; then

openvasmd --create-user=admin

root@areas:~#

COMMUNITY_NVT_RSYNC_FEED=rsync://feed.openvas.org:/nvt-feed

COMMUNITY_NVT_RSYNC_FEED=rsync://feed.community.greenbone.net:/nvt-feed

COMMUNITY_SCAP_RSYNC_FEED=rsync://feed.community.greenbone.net:/scap-data

COMMUNITY_CERT_RSYNC_FEED=rsync://feed.community.greenbone.net:/cert-data

We are seeing no further transitions from old server feed.openvas.org to new server feed.community.greenbone.net. Since the server will simply not be available beyond September 30th, we decided the following steps to make all users of the deprecated server aware of the situation:

On September 1st 2020 we stop updating the Greenbone Community Feed as served via feed.openvas.org.
On the same day we add a VT that alerts for any scanned host a highest severity and it will inform about the options to either change the server name for the Greenbone Community Feed or to go with a professional Greenbone product.

and replacing the url, it started downloading the feeds!

Please note that this is not required if you have build GVM-20.08 as this release already includes the sync script pointing at the updated feed server.

If you had to change the URL you probably have some older sync scripts in your PATH which takes precedence over the updated ones from GVM-20.08.

I would strongly suggest to check how you have build your setup and to remove remains / leftovers from your old installation (at least the sync scripts are still the ones from an older GVM installation if you had to change the URL).

If the suggestion isn’t followed you might get into trouble into the future due to using outdated sync scripts not getting any updates.