How to upgrade checkmk version from 2.3 to 2.5 version

We are currently using Checkmk Raw Edition 2.3.0p8 and need to upgrade to version 2.5. Can we upgrade directly from 2.3 to 2.5, or do we need to follow the upgrade path 2.3 → 2.4 → 2.5?

Also, regarding the Checkmk agent, can we upgrade the agent directly from version 2.3 to 2.5, or do we need to upgrade it through version 2.4 first?

Hi ragav,

i would recommend the following path:

2.3.0p8 → 2.3.latest → 2.4.latest → 2.5

The agent will be compatible in most cases, if you are using the agent updater i would update all agents in between the update steps.

If you are not using the agent updater you can update the site to 2.5 and then upgrade the agents.

… Just realised the RAW Edition does not have the automatic agent updater, so the answer only applies to the other editions.

The most problems will arise due to extension packages, so make shure that these are compatible with the different checkmk versions.

Hi **aeckstein,
**
I upgraded Checkmk from 2.3 to the latest 2.3 version and then to the latest 2.4 version. However, after upgrading to the latest 2.5 version, all server agent controllers are showing as “Not Registered.”

Could you please advise on how to resolve this issue? Do we also need to upgrade the Checkmk agent version on all servers from 2.3 to 2.5?

Hi ragav,

did you register all checkmk agents as described here ?

What versions do the checkmk agents have ?

For RAW Edition this looks like a bug. I also had this on one instance.

Inside “~/var/agent-receiver/” you have a folder “received-outputs” in 2.4 this is the only existing folder here. With 2.5 you get an extra folder “uuid-lookup”. But not inside the RAW edition automatically. I think the migration steps are missing to do this.
Inside the “received-outputs” you have links like this
GUID → ../../../tmp/check_mk/data_source_cache/push-agent/inactive/HOSTNAME
in the folder “uuid-lookup” you should have links like this
HOSTNAME → GUID

If you now list all your GUIDs from the first folder and create the links in the second one all your registered agents should work again.

@ragav did you activate changes after the update to 2.5?

It looks like this bug happens on RAW/Community Editions only.
The activate changes after the update changes nothing.
In my case the only solution was manually creating the links.

I can reproduce it now and created an internal ticket.
Reference: CMK-40151
Thank you all for reporting!