Update feed of Greenbone OS 22.04.20

Getting Started
1

H,

I am running a Greenbone OS 22.04.20 which I installed from an ISO. I did not compile anything and took a readily available image (community). I did not install any key.

I am trying to update the feeds of same.

From the OS perspective, I can see

“No system operation is running currently”

And tried running the update from OS side

“The system operation “update feed” was successfully started in background

From the webinterface, I can see either “Too old (X days) Please check the automatic synchronisation of your system’ or “update in progress”

When I do trigger the update from the OS, I can see traffic from firewall perspective, but the feeds seem to never update.

I read that the Greenbone OS 22.04.20 reached EOL but cannot find any information if the community update feeds should still work.

As I don’t have access to ssh (this is a readily available image) I cannot run the different commands I saw on the forum.

I don’t know what else I could do from my side.

Thanks for reading my post and your replies

2

@Malik974 Update in progress’ means that data is being transferred from disk to the database. This process can take several hours. Please wait patiently.

Eero

3

Hi Eero,

Thanks for your reply. I did wait a few hours. Its been a day now.

From webinteface:I see,

a) Too old (XXX days) Please check the automatic synchronisation of your system for NVT

b) Update in progress… for the 3 other feeds.

From Firewall perspective, no traffic during the last hours exepct a client-rst on a TCP-873 this morning at 09:06

Thanks

4

@Malik974

I’m not familiar with the commercial Greenbone image, as I use the open source version. However, the data transfer from the internet stops once the download is complete, and after that, the transfer to the database begins. You do have the latest image in use, right?

Eero

5

Eero

Thanks so much for your insights on this issue. I had installed the image some times back. At the time, it was the latest. When checking help//about, I can see it is a Greenbone OS 22.04.20.

From os perspective:

a) I tried again triggering an update feed from OS.

b) In feed synchonisation, I can see system is currently busy

I could see traffic from Firewall perspective.

I then rebooted appliance from OS perspective.

In webinterface, at some point , I could see

a) the NVTs to be current

b) the other feeds to be update in progress

After refreshing

a) NvT feeds are again **Too old (Xdays)**Please check the automatic synchronization of your system.

b) The other three are still update in progress….

Checking from OS side, in about “No system operation is running currently“

I read that the Greenbone OS 22.04.20 reached EOL but cannot find any information if the community update feeds should still work.

6

@Malik974 There are two versions of Greenbone: open source and commercial. It seems you’re currently testing the commercial trial version? Maybe try the open source version first, and then purchase the commercial one?

Instructions for opensource version: Kali Linux Install Guide - Greenbone Community Documentation

Eero

7

This is likely due to the disk size of GOS 22.04.20 being insufficient for the size of the feed nowadays. We increased the disk size with GOS 22.04.23. Please note that the current patch-level for GOS 22.04 is 22.04.29.

If you are an existing customer, please contact our support team at Technical Support - Greenbone for help. If you are interested in evaluating our commercial products, please contact our sales team at OPENVAS SCAN | Vulnerability Management for Enterprises & Public Sector Organizations - Greenbone.

If neither applies, I also recommend to use the community edition.

2 Likes
8

Hello Martin,

Thanks for your insights on this issue.

May I please ask if the 22.04.X branch is still supported ? As regards to Roadmap and Lifecycle - Greenbone, I can read that 22.04 is End of Life.

Thanks beforehand for your help & support,

Thanks & regards,

9

The “end of life” phase in our case means that it is on life support: Only critical issues will be fixed. For more information see Description Lifecycle System. Please note that we require the latest patch-level for official support however, alternatively our support team will assist with the upgrade to the latest patch-level.

GOS 22.04 as a whole is also currently scheduled to be retired on 2026-02-01.

2 Likes
10

Thanks so much Martin. I will go trought same.

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.