Feed Status stuck in Update in progress

Building from Source and Advanced Topics
1

After issuing command ‘sudo /usr/local/bin/greenbone-feed-sync’, the gvmd.log file seems to be stuck in a loop.

md manage:   INFO:2025-01-27 18h42.14 UTC:2378: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2023.xml
md   main:MESSAGE:2025-01-27 18h44.42 utc:4031:    Greenbone Vulnerability Manager version 23.2.0 (DB revision 255)
md manage:   INFO:2025-01-27 18h44.54 UTC:4056: update_scap: Updating data from feed
md manage:   INFO:2025-01-27 18h44.54 UTC:4056: Updating CPEs
md manage:   INFO:2025-01-27 18h48.04 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2024.xml
md manage:   INFO:2025-01-27 18h51.47 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2010.xml
md manage:   INFO:2025-01-27 18h52.03 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage:   INFO:2025-01-27 18h52.08 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2022.xml
md manage:   INFO:2025-01-27 18h55.26 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2003.xml
md manage:   INFO:2025-01-27 18h55.29 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2014.xml
md manage:   INFO:2025-01-27 18h56.08 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage:   INFO:2025-01-27 18h56.11 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2016.xml
md manage:   INFO:2025-01-27 18h57.04 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2020.xml
md manage:   INFO:2025-01-27 18h58.45 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2013.xml
md manage:   INFO:2025-01-27 18h59.20 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2009.xml
md manage:   INFO:2025-01-27 18h59.28 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2025.xml
md manage:   INFO:2025-01-27 18h59.32 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2012.xml
md manage:   INFO:2025-01-27 18h59.55 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2018.xml
md manage:   INFO:2025-01-27 19h01.12 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2015.xml
md manage:   INFO:2025-01-27 19h01.57 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2011.xml
md manage:   INFO:2025-01-27 19h02.27 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2004.xml
md manage:   INFO:2025-01-27 19h02.29 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2017.xml
md manage:   INFO:2025-01-27 19h03.37 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2007.xml
md manage:   INFO:2025-01-27 19h03.46 UTC:4056: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2023.xml
md   main:MESSAGE:2025-01-27 19h04.52 utc:4672:    Greenbone Vulnerability Manager version 23.2.0 (DB revision 255)
md manage:   INFO:2025-01-27 19h05.02 UTC:4700: update_scap: Updating data from feed
md manage:   INFO:2025-01-27 19h05.02 UTC:4700: Updating CPEs
md manage:   INFO:2025-01-27 19h08.12 UTC:4700: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2024.xml
2

Nevermind.
My problem was fixed when I upgraded.

1 Like
3

This mentioned fix could be relevant / have been included in the update:

1 Like