Osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock

Environment:

  • Debian 11.4
  • Docker version 20.10.5
  • docker-compose version 1.29.2

using the latest guide from Greenbone Community Containers 22.4 - Greenbone Community Documentation gives me the following output.

gvmd_1                 | md manage:WARNING:2022-09-14 11h26.14 UTC:248: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 11h26.24 UTC:249: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 11h26.34 UTC:250: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 11h26.46 UTC:259: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 11h26.56 UTC:260: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock

Missing all NVTs, the others are there

Hi, can you please check the logs of the ospd-openvas container?

1 Like

Not sure if the issue is just a blocked connection, currently checking. All other feeds went fine.

<28>Sep 14 12:35:54 greenbone-nvt-sync: The log facility is not working as expected. All messages will be written to the standard error stream.
<29>Sep 14 12:35:54 greenbone-nvt-sync: No Greenbone Security Feed access key found, falling back to Greenbone Community Feed
<29>Sep 14 12:35:59 greenbone-nvt-sync: Configured NVT rsync feed: rsync://feed.community.greenbone.net:/community/vulnerability-feed/22.04/vt-data/nasl/
<29>Sep 14 12:35:59 greenbone-nvt-sync: Loading NASL data to /var/lib/openvas/plugins
rsync: [Receiver] failed to connect to feed.community.greenbone.net (45.135.106.143): Connection refused (111)
rsync: [Receiver] failed to connect to feed.community.greenbone.net (2a0e:6b40:20:106:20c:29ff:fe7f:d2ae): Cannot assign requested address (99)
rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]

Running the feed sync scripts with the containers should not be necessary anymore. Please use the latest compose file which provided container images for the feed data (as mentioned in Changelog - Greenbone Community Documentation)

1 Like

If I’m right i already use stable and latest with the compose file documented in https://greenbone.github.io/docs/latest/_static/docker-compose-22.4.yml

Is this correct to use?

In that case no it’s not. You shouldn’t run a sync script manually anymore. All feed data is provided via containers and updated during a docker pull.

1 Like

Interesting, it looks like the problem has been solved. There was no change on our side or any ressource contraints. Maybe we went into a rate limitation that blocked the NVT Feed. This wouldn’t be an issue if we could still start scanning but there was an error about an missing object (NVTs ?). But many thanks for your support!

gvmd_1                 | md manage:WARNING:2022-09-14 18h03.35 UTC:2059: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h03.50 UTC:2068: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h04.05 UTC:2077: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h04.20 UTC:2086: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h04.35 UTC:2095: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h04.51 UTC:2104: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h05.06 UTC:2113: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h05.21 UTC:2122: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h05.36 UTC:2131: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h05.51 UTC:2140: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h06.06 UTC:2149: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:WARNING:2022-09-14 18h06.21 UTC:2158: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
gvmd_1                 | md manage:   INFO:2022-09-14 18h06.36 UTC:2167: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd_1                 | md manage:   INFO:2022-09-14 18h06.51 UTC:2176: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd_1                 | md manage:   INFO:2022-09-14 18h07.06 UTC:2185: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd_1                 | md manage:   INFO:2022-09-14 18h07.21 UTC:2194: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd_1                 | md manage:   INFO:2022-09-14 18h07.36 UTC:2203: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd_1                 | md manage:   INFO:2022-09-14 18h07.51 UTC:2212: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd_1                 | md manage:   INFO:2022-09-14 18h08.07 UTC:2224: OSP service has different VT status (version 202209141058) from database (version (null), 0 VTs). Starting update ...
gvmd_1                 | md manage:   INFO:2022-09-14 18h14.40 UTC:2224: Updating VTs in database ... 105979 new VTs, 0 changed VTs
gvmd_1                 | md manage:   INFO:2022-09-14 18h14.44 UTC:2224: Updating VTs in database ... done (105979 VTs).
gvmd_1                 | md manage:MESSAGE:2022-09-14 18h14.56 UTC:2468: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.

Needed to set the restart policy of the following containers to “unless-stopped”. Afterwards, everything works even if the whole system has been restarted

  • notus_scanner
  • ospd-openvas