Running as root. Switching to user ‘gvm’ and group ‘gvm’.
Trying to acquire lock on /var/lib/openvas/feed-update.lock
Acquired lock on /var/lib/openvas/feed-update.lock
Downloading Notus files from rsync://feed.community.greenbone.net/community/vulnerability-feed/22.04/vt-data/notus/ to /var/lib/notus
rsync: read error: Connection reset by peer (104)
rsync error: error in socket IO (code 10) at io.c(806)
rsync: connection unexpectedly closed (20610 bytes received so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(231)
Any thoughts why I can’t download the Notus files?
Server seems to be up for me. Is it possible you have network congestion?
$ rsync feed.community.greenbone.net::
Greenbone community feed server - http://feed.community.greenbone.net/
This service is hosted by Greenbone Networks - http://www.greenbone.net/
All transactions are logged.
If you have any questions, please use the Greenbone community portal.
See https://community.greenbone.net 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.
data-objects Greenbone community data objects, see https://community.greenbone.net/
nvt-feed Greenbone community NVT feed, see https://community.greenbone.net/
scap-data Greenbone community SCAP data feed, see https://community.greenbone.net/
cert-data Greenbone community CERT data feed, see https://community.greenbone.net/
community-legacy Greenbone community legacy feed, see https://community.greenbone.net/
community Greenbone community feed, see https://community.greenbone.net/
$ sudo nping --tcp --traceroute -c 13 -p 873 feed.community.greenbone.net
Password:
Starting Nping 0.7.93 ( https://nmap.org/nping ) at 2023-09-27 17:53 EDT
SENT (1.0506s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=1 id=46105 iplen=40 seq=1822093195 win=1480
SENT (2.0508s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=2 id=46105 iplen=40 seq=1822093195 win=1480
SENT (3.0519s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=3 id=46105 iplen=40 seq=1822093195 win=1480
SENT (4.0524s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=4 id=46105 iplen=40 seq=1822093195 win=1480
SENT (5.0535s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=5 id=46105 iplen=40 seq=1822093195 win=1480
SENT (6.0547s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=6 id=46105 iplen=40 seq=1822093195 win=1480
SENT (7.0558s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=7 id=46105 iplen=40 seq=1822093195 win=1480
SENT (8.0560s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=8 id=46105 iplen=40 seq=1822093195 win=1480
SENT (9.0562s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=9 id=46105 iplen=40 seq=1822093195 win=1480
SENT (10.0563s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=10 id=46105 iplen=40 seq=1822093195 win=1480
SENT (11.0565s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=11 id=46105 iplen=40 seq=1822093195 win=1480
SENT (12.0566s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=12 id=46105 iplen=40 seq=1822093195 win=1480
SENT (13.0568s) TCP 10.5.0.2:31201 > 45.135.106.143:873 S ttl=13 id=46105 iplen=40 seq=1822093195 win=1480
Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 13 (520B) | Rcvd: 0 (0B) | Lost: 13 (100.00%)
Nping done: 1 IP address pinged in 14.06 seconds
Most likely the issue is on your side and some network device is blocking the connection to the server on the TCP port 873. The feed sync uses the rsync protocol on port 873 and not http(s) on port 80 or 443.