UAT and Dev Mid server down

Sed_F · ‎07-01-2025

My UAT and Dev Mid-server are down with the same issue : Login authentication failure for User cm_midserver_user associated with down MID Server: a96d5fad87591e507867113e3fbb350e. Check password on MID server.

I thought is was the certificate issue and the access was allow to the F5 but it remain down.

Last error in agent log but the user or password doesn't changed:

xxxxx_midserver_user cannot be authenticated. User does not exist, or missing the proper roles. If you have deleted or changed the MID server keystore, and config.xml mid.instance.password value is encrypted, you may need to change this value to plain text (during MID startup, password is re-encrypted using current keystore and written back to mid.instance.password).

GlideFather · ‎07-01-2025

Hi @Sed_F,

A quick idea: have not been scheduled any cloning or upgrading of that instance lately?

It happened to us that the TEST configurations for MID Server were overwritten by the information from PROD until we made it excluded...

Or was the User table updated anyhow? The account might have been deactivated.

———
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */

Sed_F · ‎07-01-2025

When these instances were, Upgrade to Yokohama version was done .....

GlideFather · ‎07-01-2025

Sorry, I didn't understand.

Was the upgrade made in last days?
Or was there any major implementation these days?
It isn't production, is it?

———
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */

Sed_F · ‎07-02-2025

Hi @GlideFather ,

allow me to clarify

Was the upgrade made in last days? ==> Unfortunately the upgrade couldn't happened because the Mid_servers (UAT and Dev) were down. They are down since 02 months already.
Or was there any major implementation these days?
It isn't production, is it? It's only the last weekend that the PROD was upgraded to Yokohama version.

Thanks.