Rsync: failed to connect to feed.openvas.org

Same issuse since September.
My NVTs are 26 days old, SCAP and CERT 42 days old and can’t update them.

Still getting:

rsync: failed to connect to feed.openvas.org (89.146.224.58): Connection refused (111)
rsync: failed to connect to feed.openvas.org (2a01:130:2000:127::d1): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]

Tried two different VMs in two different envs and it’s the same error.

If I try to download manually from
dl. greenbone. net / community-nvt-feed-current.tar.bz2
getting “Connection refused” error also.

I’m using:
OpenVAS Scanner 6.0.0
Greenbone Security Assistant 8.0.0
Greenbone Vulnerability Manager 8.0.0
on Ubuntu 18

Hi PioTrek,

please take a look at this:

Greetings

2 Likes

Hi @_OR

I am upgrading from gvm 11 to the latest gvm 20.08 , after building the openvas 20.08 and setting up the redis-server , I executed “greenbone-nvt-sync” .
I get the following error .
greenbone-nvt-sync
rsync: failed to connect to feed.openvas.org (89.146.224.58): Connection timed out (110)
rsync: failed to connect to feed.openvas.org (2a01:130:2000:127::d1): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]

Why is it trying to connect to the old server ?
How can this be solved ?

Thanks
Gangambika

Maybe there are left-over from your old system. I would suggest to format your system and do a blank re-installation if you can´t debug this via shell.

2 Likes

Thanks a lot @Lukas
There was indeed a nvt-sync routine which had the old URL in /sbin path, just modified the URL with new one there ,solved my issue .
Thanks again .

3 Likes

Hi can you help me , i have the same error !
im using GVM 11 on ubuntu 20.04

sync: failed to connect to feed.community.greenbone.net (45.135.106.142): Connection refused (111)
rsync: failed to connect to feed.community.greenbone.net (2a0e:6b40:20:106:20c:29ff:fe67:cbb5): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]

Check that no active TCP session exists between your internet address and the back end.

rsync: failed to connect to feed.community.greenbone.net (2a0e:6b40:20:106:20c:29ff:fe67:cbb5): Network is unreachable (101)

Fix your routing first … Network is unreachable shows your are not connected to the whole (IPv6) Internet.

Then check with netcat on the RSYNC port, if this is not working your device is messing the connection up.
is should look like:

# nc feed.community.greenbone.net 873
@RSYNCD: 31.0
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.

1 Like

hi lukas
this is output
gvm@openvas:~$ netcat -v feed.community.greenbone.net 873
-netcat: connect to feed.community.greenbone.net port 873 (tcp) failed: Connection refused

Do you have any devices between your GVM installation and the internet ?

If so please remove them. It looks like a messed up connectivity at the moment.

1 Like

Itried ’ $ netcat -v feed.community.greenbone.net 873’
on another server ubuntu connected to the intenet and i got thse same output :
netcat: connect to feed.community.greenbone.net port 873 (tcp) failed: Connection time out
netcat: connect to feed.community.greenbone.net port 873 (tcp) failed: Network is unreachable

And how do you connect the Internet? That might be your problem if you cant commect to the feed service

I did a GVM update to newer version and it worked. What version are you using?

1 Like

GVM 11
ubuntu 20.04

Try the following:

sudo apt-get update
sudo apt-get install gvm
sudo gvm-feed-update

1 Like

I had the same issue at another network and the troubleshooting tells me that maybe the firewall is blocking the RSYNC port TCP 873. I will ask for the port to be open and let you know if that fixes the problem. Maybe you can try that too.

1 Like