Can't download SCAP files (nvdcve-2.0-2019.xml)

GVM versions

gsad: 21.4.4
gvmd: 21.4.5
openvas-scanner: 21.4.4
gvm-libs: 21.4.4

Environment

Operating system: RockyLinux 8.5
Kernel: 4.18.0-372.19.1.el8_6.x86_64
Installation method / source: Both native and via docker

Hello all, I have tried installing OpenVAS both via docker and via the RockyLinux packages. Both install and run fine, however I can’t seem to update SCAP files.

Specifically nvdcve-2.0-2019.xml fails at 70% every single time with the following errors.

nvdcve-2.0-2019.xml
              0   0%    0.00kB/s    0:00:00  
rsync: read error: Connection reset by peer (104)
rsync error: error in socket IO (code 10) at io.c(785) [receiver=3.1.3]
rsync: connection unexpectedly closed (1313 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [generator=3.1.3]

Exactly the same happens on both docker and via package manager.

I have not been able to find this file manually, I can only find JSON files.

Please let me know if I can provide more information, and thanks in advance!

@ivohulsman sounds like a network problem.

Anyway, my github contains some of these files

Just download them and unpack to correct location.

Eero

Hello, thank you for your reply!

It downloads any other file just fine up until the 2019 file. I have copied your files over mine but they get downloaded and overwritten anyway.

What network setting could cause just one file not to download?

@ivohulsman rsync only copies modifed files.

it sounds like your network is broken. maybe broken router or something…

Eero

Or any firewall or IPS system that is resetting that connection due to a matching signature. Try to avoid all this security tools between your installation and the internet.

@Lukas maybe workaround is spin low end virtual machine on cloud and rsync via ssh…

Eero

I have connected to a different network and now it is working, so both of you are right, it is a network issue.

Thank you both very much, I would not have known this could be caused by a network issue on my end.