Update in progress... for most feeds

Linux Distribution and External Repo Discussion
1

I have 2 openVAS systems (home & work) where the feed status is for ever “Update in progress…”
I have plenty of ram 28GB & 32 GB, plenty of space ( >100GB free both on SSD) I tried to gvm-stop then update those feed using the various methods… rebooted … nothing. Any straight forward method ?

Kali Linux is up to date, gvmd is 22.4.2

the gvmd log is :

md manage:WARNING:2023-06-28 06h41.52 UTC:2892: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 06h41.58 UTC:5847: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 06h41.59 UTC:5847: update_scap: Updating data from feed
md manage: INFO:2023-06-28 06h41.59 UTC:5847: Updating CPEs
md manage:WARNING:2023-06-28 06h45.59 UTC:5847: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 06h46.01 UTC:9490: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 06h46.02 UTC:9490: update_scap: Updating data from feed
md manage: INFO:2023-06-28 06h46.02 UTC:9490: Updating CPEs
md manage:WARNING:2023-06-28 06h50.09 UTC:9490: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 06h50.18 UTC:13747: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 06h50.18 UTC:13747: update_scap: Updating data from feed
md manage: INFO:2023-06-28 06h50.18 UTC:13747: Updating CPEs
md manage:WARNING:2023-06-28 06h54.09 UTC:13747: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 06h54.20 UTC:16398: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 06h54.20 UTC:16398: update_scap: Updating data from feed
md manage: INFO:2023-06-28 06h54.20 UTC:16398: Updating CPEs
md main:MESSAGE:2023-06-28 06h55.22 utc:17231: Greenbone Vulnerability Manager version 22.4.2 (DB revision 250)
md manage: INFO:2023-06-28 06h55.22 utc:17231: Getting users.
md manage:MESSAGE:2023-06-28 06h55.22 utc:17231: No SCAP database found
md main:MESSAGE:2023-06-28 06h55.24 utc:17265: Greenbone Vulnerability Manager version 22.4.2 (DB revision 250)
md manage: INFO:2023-06-28 06h55.24 utc:17265: Getting users.
md manage:MESSAGE:2023-06-28 06h55.24 utc:17265: No SCAP database found
md manage:WARNING:2023-06-28 06h58.28 UTC:16398: update_scap_cpes_from_file: Failed to parse element
md manage: INFO:2023-06-28 06h58.34 UTC:19460: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:WARNING:2023-06-28 06h58.34 UTC:19459: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 06h58.35 UTC:19459: update_scap: Updating data from feed
md manage: INFO:2023-06-28 06h58.35 UTC:19459: Updating CPEs
md manage:WARNING:2023-06-28 07h02.33 UTC:19459: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h02.37 UTC:22410: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h02.37 UTC:22409: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-06-28 07h02.37 UTC:22410: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h02.37 UTC:22410: Updating CPEs
md manage:WARNING:2023-06-28 07h06.35 UTC:22410: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h06.39 UTC:25301: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h06.39 UTC:25301: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h06.39 UTC:25301: Updating CPEs
md manage: INFO:2023-06-28 07h06.39 UTC:25302: OSP service has different VT status (version 202306270601) from database (version 202306260553, 129407 VTs). Starting update …
md manage: INFO:2023-06-28 07h09.48 utc:25302: Updating VTs in database … 8 new VTs, 854 changed VTs
md manage: INFO:2023-06-28 07h09.52 utc:25302: Updating VTs in database … done (129415 VTs).
md manage:WARNING:2023-06-28 07h10.41 UTC:25301: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h10.43 UTC:27920: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h10.44 UTC:27920: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h10.44 UTC:27920: Updating CPEs
md manage:WARNING:2023-06-28 07h14.41 UTC:27920: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h14.45 UTC:30449: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h14.46 UTC:30449: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h14.46 UTC:30449: Updating CPEs
md manage:WARNING:2023-06-28 07h18.46 UTC:30449: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h18.48 UTC:32982: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h18.48 UTC:32982: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h18.48 UTC:32982: Updating CPEs
md manage:WARNING:2023-06-28 07h22.49 UTC:32982: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h22.50 UTC:35512: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h22.50 UTC:35512: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h22.50 UTC:35512: Updating CPEs
md manage:WARNING:2023-06-28 07h26.42 UTC:35512: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h26.52 UTC:38034: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h26.53 UTC:38034: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h26.53 UTC:38034: Updating CPEs
md manage:WARNING:2023-06-28 07h30.55 UTC:38034: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h31.04 UTC:40664: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h31.05 UTC:40664: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h31.05 UTC:40664: Updating CPEs
md manage:WARNING:2023-06-28 07h35.08 UTC:40664: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h35.17 UTC:43294: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h35.17 UTC:43294: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h35.17 UTC:43294: Updating CPEs
md manage:WARNING:2023-06-28 07h39.13 UTC:43294: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h39.19 UTC:45873: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h39.20 UTC:45873: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h39.20 UTC:45873: Updating CPEs
md manage:WARNING:2023-06-28 07h43.19 UTC:45873: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h43.21 UTC:48391: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h43.21 UTC:48391: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h43.21 UTC:48391: Updating CPEs
md manage:WARNING:2023-06-28 07h47.15 UTC:48391: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h47.24 UTC:50934: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h47.25 UTC:50934: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h47.25 UTC:50934: Updating CPEs
md manage:WARNING:2023-06-28 07h51.13 UTC:50934: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h51.16 UTC:53352: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h51.17 UTC:53352: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h51.17 UTC:53352: Updating CPEs
md manage:WARNING:2023-06-28 07h55.13 UTC:53352: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h55.18 UTC:55879: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h55.19 UTC:55879: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h55.19 UTC:55879: Updating CPEs
md manage:WARNING:2023-06-28 07h59.23 UTC:55879: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 07h59.30 UTC:58506: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 07h59.31 UTC:58506: update_scap: Updating data from feed
md manage: INFO:2023-06-28 07h59.31 UTC:58506: Updating CPEs
md manage:WARNING:2023-06-28 08h03.30 UTC:58506: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h03.32 UTC:61053: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h03.33 UTC:61053: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h03.33 UTC:61053: Updating CPEs
md manage:WARNING:2023-06-28 08h07.30 UTC:61053: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h07.35 UTC:63587: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h07.35 UTC:63587: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h07.35 UTC:63587: Updating CPEs
md manage:WARNING:2023-06-28 08h11.37 UTC:63587: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h11.48 UTC:66260: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h11.48 UTC:66260: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h11.48 UTC:66260: Updating CPEs
md manage:WARNING:2023-06-28 08h15.48 UTC:66260: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h15.50 UTC:68788: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h15.50 UTC:68788: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h15.50 UTC:68788: Updating CPEs
md manage:WARNING:2023-06-28 08h19.48 UTC:68788: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h19.52 UTC:71321: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h19.53 UTC:71321: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h19.53 UTC:71321: Updating CPEs
md manage:WARNING:2023-06-28 08h23.54 UTC:71321: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h23.54 UTC:73847: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h23.55 UTC:73847: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h23.55 UTC:73847: Updating CPEs
md manage:WARNING:2023-06-28 08h27.57 UTC:73847: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h28.06 UTC:76487: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h28.07 UTC:76487: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h28.07 UTC:76487: Updating CPEs
md manage:WARNING:2023-06-28 08h32.02 UTC:76487: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h32.09 UTC:79003: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h32.09 UTC:79003: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h32.09 UTC:79003: Updating CPEs
md manage:WARNING:2023-06-28 08h35.59 UTC:79003: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h36.01 UTC:81423: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h36.01 UTC:81423: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h36.01 UTC:81423: Updating CPEs
md manage:WARNING:2023-06-28 08h39.49 UTC:81423: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h39.52 UTC:83902: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h39.53 UTC:83902: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h39.53 UTC:83902: Updating CPEs
md manage:WARNING:2023-06-28 08h43.52 UTC:83902: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h43.55 UTC:86420: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h43.55 UTC:86420: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h43.55 UTC:86420: Updating CPEs
md manage:WARNING:2023-06-28 08h47.48 UTC:86420: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h47.57 UTC:88954: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h47.57 UTC:88954: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h47.57 UTC:88954: Updating CPEs
md manage:WARNING:2023-06-28 08h52.07 UTC:88954: update_scap_cpes_from_file: Failed to parse element
md manage:WARNING:2023-06-28 08h52.09 UTC:91702: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 08h52.10 UTC:91702: update_scap: Updating data from feed
md manage: INFO:2023-06-28 08h52.10 UTC:91702: Updating CPEs
md main:MESSAGE:2023-06-28 11h06.41 utc:962: Greenbone Vulnerability Manager version 22.4.2 (DB revision 250)
md manage:MESSAGE:2023-06-28 11h06.42 utc:985: No SCAP database found
md manage:WARNING:2023-06-28 11h06.56 UTC:1042: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-06-28 11h06.56 UTC:1043: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-06-28 11h06.56 UTC:1046: sync_cert: Updating data from feed
md manage: INFO:2023-06-28 11h06.56 UTC:1042: update_scap: Updating data from feed
md manage: INFO:2023-06-28 11h06.56 UTC:1042: Updating CPEs
md manage: INFO:2023-06-28 11h06.56 UTC:1046: update_dfn_xml: dfn-cert-2011.xml
md manage: INFO:2023-06-28 11h06.56 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2011.xml
md manage: INFO:2023-06-28 11h06.57 UTC:1046: update_dfn_xml: dfn-cert-2023.xml
md manage: INFO:2023-06-28 11h06.57 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2023.xml
md manage: INFO:2023-06-28 11h07.00 UTC:1046: update_dfn_xml: dfn-cert-2021.xml
md manage: INFO:2023-06-28 11h07.00 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2021.xml
md manage: INFO:2023-06-28 11h07.00 UTC:1046: update_dfn_xml: dfn-cert-2014.xml
md manage: INFO:2023-06-28 11h07.00 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2014.xml
md manage: INFO:2023-06-28 11h07.00 UTC:1046: update_dfn_xml: dfn-cert-2020.xml
md manage: INFO:2023-06-28 11h07.00 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2020.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: update_dfn_xml: dfn-cert-2013.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2013.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: update_dfn_xml: dfn-cert-2010.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2010.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: update_dfn_xml: dfn-cert-2015.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2015.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: update_dfn_xml: dfn-cert-2022.xml
md manage: INFO:2023-06-28 11h07.01 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2022.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: update_dfn_xml: dfn-cert-2016.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2016.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: update_dfn_xml: dfn-cert-2019.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2019.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: update_dfn_xml: dfn-cert-2008.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2008.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: update_dfn_xml: dfn-cert-2009.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2009.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: update_dfn_xml: dfn-cert-2018.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2018.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: update_dfn_xml: dfn-cert-2012.xml
md manage: INFO:2023-06-28 11h07.02 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2012.xml
md manage: INFO:2023-06-28 11h07.03 UTC:1046: update_dfn_xml: dfn-cert-2017.xml
md manage: INFO:2023-06-28 11h07.03 UTC:1046: Updating /var/lib/gvm/cert-data/dfn-cert-2017.xml
md manage: INFO:2023-06-28 11h07.04 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K18.xml
md manage: INFO:2023-06-28 11h07.05 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K19.xml
md manage: INFO:2023-06-28 11h07.05 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K20.xml
md manage: INFO:2023-06-28 11h07.05 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K16.xml
md manage: INFO:2023-06-28 11h07.06 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K22.xml
md manage: INFO:2023-06-28 11h07.08 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K15.xml
md manage: INFO:2023-06-28 11h07.08 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K21.xml
md manage: INFO:2023-06-28 11h07.08 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K17.xml
md manage: INFO:2023-06-28 11h07.09 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K13.xml
md manage: INFO:2023-06-28 11h07.09 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K14.xml
md manage: INFO:2023-06-28 11h07.09 UTC:1046: Updating /var/lib/gvm/cert-data/CB-K23.xml
md manage: INFO:2023-06-28 11h07.11 UTC:1046: SCAP database does not exist (yet), skipping CERT severity score update
md manage: INFO:2023-06-28 11h07.11 UTC:1046: sync_cert: Updating CERT info succeeded.

image
image1036×321 31.2 KB

Many thanks !

2

Same here man, I looked for the fix everywhere and nothing seems to work, I even reinstalled the whole client and it did not help.

3

It looks to have solve itself™®© … I just did manually the update once and :

image
image854×307 78.8 KB

Here’s my crontab :

1 1 * * * for optimize in vaccum analyse cleanup-report-formats cleanup-result-nvts cleanup-config-prefs cleanup-result-severities update-report-cache; do /usr/sbin/gvmd --optimize=$optimize; done
0 2 * * * sudo -u _gvm greenbone-scapdata-sync >/var/log/gvm-feed-update-SCAP.log
30 2 * * * sudo -u _gvm greenbone-feed-sync --type GVMD_DATA 2>/var/log/gvm-feed-update-GVMD.log
30 3 * * * sudo -u _gvm greenbone-certdata-sync >/var/log/gvm-feed-update-CERT.log
0 5 * * * sudo -u _gvm greenbone-nvt-sync 2>/var/log/gvm-feed-update-sync.log
0 6 * * * sudo -u _gvm openvas -u

This looks to me a bit complex for just rsync lists and integrate them into the database. On top there are several commands doing the same or at least pretending to.

4

Don’t add 0 6 * * * sudo -u _gvm openvas -u. I really don’t have a clue where people are getting this from. Don’t run any openvas command by yourself. The openvas scanner is controlled by ospd-openvas. It does all the necessary stuff internally.

3 Likes
5

Additionally I wrote a detailed description of the feed synchronization at our build from source guide. It contains an explanation what needs to be done and what’s going on in the background. Also it gives you hints when each data is “synced” and the “sync” is finished. Please take a look at

2 Likes
6

It’s in various pages on the web since there is no “simple” feed synchronisation service / way . And on top this command works :smiley:

# openvas -h
Usage:
  openvas [OPTION?] - Open Vulnerability Assessment Scanner

Help Options:
  -h, --help                       Show help options

Application Options:
  -V, --version                    Display version information
  -c, --config-file=<filename>     Configuration file
  -s, --cfg-specs                  Print configuration settings
  -y, --sysconfdir                 Print system configuration directory (set at compile time)
  -u, --update-vt-info             Updates VT info into redis store from VT files

I still fail to see/understand the concept of greenbone-feed-sync --type vs greenbone-nvt-sync/greenbone-certdata-sync/(and there’s no greenbone-gcmddata-sync :thinking:) vs gvm-feed-update

7

You SHOULD NOT use this command. Forget about calling openvas until some Greenbone developer like me says something else. It does not what you expect it to do and it will be run automatically via ospd-openvas anyway.

2 Likes
8

Let me try to give some insides. First of all gvm-feed-update.

gvm-feed-update is NOT maintained by Greenbone and is therefore not used anywhere in our docs or provided code by Greenbone. It’s maintained by the Kali/Debian packagers and as far as I know it just calls the standard greenbone-*-sync scripts provided by us in one go. Personally I think you should not use it.

greenbone-certdata-sync is just the same as greenbone-feed-sync --type CERT. It is/was just provided for backwards compatibility. It doesn’t get installed anymore (by default) since gvmd 22.5.0.

greenbone-scapdata-sync is just the same as greenbone-feed-sync --type SCAP. It is/was just provided for backwards compatibility. It doesn’t get installed anymore (by default) since gvmd 22.5.0.

greenbone-nvt-sync is the old sync script written in bash to download the vulnerability tests data (nasl and notus files). It is deprecated since openvas-scanner 22.6.0.

/usr/sbin/greenbone-feed-sync is the old sync script written in bash to download the CERT, SCAP and GVMD data. It doesn’t get installed anymore (by default) since gvmd 22.5.0.

There is a new greenbone-feed-sync script written in Python to replace all of the above scripts. See the announcement at New greenbone-feed-sync script This script hasn’t been picked up by the distributions yet but hopefully will arrive in the next months.
Even the gvm-feed-update use case is supported because by default when not passing any arguments --type all is run which downloads all types of feed data.

3 Likes
9

OK perfect thanks it’ll lighten up my crontab :slight_smile:

1 Like
10

I’ve added a section derived from this topic regarding the sync scripts to the Frequently Asked Questions (FAQ) - Greenbone Community Documentation

3 Likes
11

Just for clarity, here’s the contents of Kali’s gvm-feed-update. This may be where people are getting the openvas -u since it’s one of the commands run.

# Check if running as root
if [[ $EUID -ne 0 ]]; then
   echo -e "${RED}[-]${RESET} Error: $0 must be run as root" 1>&2
   exit 1
fi

echo -e "${GREEN}[>]${RESET} Updating GVM feeds"

gvm-# we can't run greenbone-nvt-sync as root. Use _gvm user
echo -e "${GREEN}[*]${RESET} Updating NVT (Network Vulnerability Tests feed from Greenbone Security Feed/Community Feed)"
runuser -u _gvm greenbone-nvt-sync

echo -e "${GREEN}[>]${RESET} Updating Vulnerability Tests info into Redis store from VT files"
#upload plugins in redis with openvas
systemctl start redis-server@openvas.service
runuser -u _gvm -- openvas -u

echo -e "${GREEN}[*]${RESET} Updating GVMD Data"
runuser -u _gvm -- greenbone-feed-sync --type GVMD_DATA

echo -e "${GREEN}[*]${RESET} Updating Scap Data"
runuser -u _gvm -- greenbone-feed-sync --type SCAP

# CERT feed sync must be done after the SCAP feed
# See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968500
echo -e "${GREEN}[*]${RESET} Updating Cert Data"
runuser -u _gvm -- greenbone-feed-sync --type CERT

echo -e "\n${GREEN}[+]${RESET} GVM feeds updated"

Hopefully Kali can just replace the gvm-feed-update tool with a symlink to the new Python greenbone-feed-sync command.

1 Like
12

However, now that I changed the crontab to only:
0 2 * * * /usr/bin/gvm-feed-update 2> /var/log/gvm-feed-update-all.log

Here’s the result several days later:

image
image870×314 29.9 KB

And content of the log ??:

/usr/bin/gvm-feed-update: line 16: runuser: command not found
/usr/bin/gvm-feed-update: line 21: runuser: command not found
/usr/bin/gvm-feed-update: line 24: runuser: command not found
/usr/bin/gvm-feed-update: line 27: runuser: command not found
/usr/bin/gvm-feed-update: line 32: runuser: command not found

Because runuser doesn’t seem to run in crontab and I don’t see how we can create crontab for _gvm user

13

Just run the cron job as _gvm user. Every user can run it’s own cron jobs. Otherwise just use sudo -u _gvm.

2 Likes
14

To create a crontab for the user, type crontab -u _gvm -e . This opens the crontab file for the _gvm user in the default text editor make some changes and save it.

2 Likes
15

Do I need to know how to script to get the feed status to update from “update in progress” or “2 days old?” It’s read “update in progress” since install. Also “Scan Configs” has been “0” ever since install.

16

“sudo /usr/local/bin/greenbone-feed-sync” returns “command not found.”

17

Hi white_chocolate, welcome to the Greenbone community forum.

Can you please post your issue in a new thread since it is a new issue? Also, in that thread, please provide your install method so we can understand why greenbone-feed-sync is not installed. Otherwise, you can simply install the new greenbone-feed-sync and run it.

2 Likes