Heads-up on Auto-Rollback Issue in Latest MID Server Update - Containerized MID Server

[BjörnB]

Hey folks,

I’m writing this in the hope that it might help others.

We're currently experiencing an issue with the brand-new auto-rollback feature in the auto-update process of the following version:

mid-linux-container-recipe.xanadu-07-02-2024__patch7-02-27-2025_03-06-2025_0935.linux.x86-64

The auto-rollback feature attempts to rename the bin folder to bin_old, but it fails with the following log entries:

INFO | jvm 1 | 2025/04/08 09:21:47.527 | WARNING: Renaming folder `/opt/snc_mid_server/agent/bin` failed
INFO | jvm 1 | 2025/04/08 09:23:47.500 | INFO: Renaming the folder `/opt/snc_mid_server/agent/bin` to `/opt/snc_mid_server/agent/bin_old`. File rename attempt (4/5).

As a result, the MID Server fails to start. We checked the permissions, and everything appears to be in order.

ServiceNow Support suggested a workaround: disable the auto-rollback feature by adding the following property under ecc_agent_property_list.do:

mid.upgrade.enable_rollback = false

After disabling the rollback feature, the MID Server is up and running again. Hopefully this helps others facing the same issue.

By the way – does anyone know how to automate the validation, re-key, and generate key actions? Every time the Docker container restarts, we have to trigger these manually. That can’t be the intended behavior in a containerized environment, right?

[mikeb]

Hey - for the validate, re-key and all that just make sure you put your config.xml and keystore files in persistent storage and mount them when you start. That will fix it.