Should a MID Server go Down during validation or remain Up?

[AvinashU]

Hi everyone,

I have a question regarding the expected behavior of MID Server validation.

When I click Validate on my MID Server, I expected the MID Server to briefly go Down while processing the restartService and Invalidate SystemCommands, and then come back Up after validation completes.

However, in my environment:

• The MID Server remains Up throughout the validation process.

• The MID Server stays in the Validating state for more than 12 hours.

• The ECC Queue shows:

  • SystemCommand → restartService → input → Ready

  • SystemCommand → restartService → output → Processed

• The ECC Queue Processed count continues to increase, indicating the MID Server is still processing other messages.

My questions are:

1. During MID Server validation, is it expected for the MID Server status to briefly change to Down, or should it remain Up?

2. Can a MID Server remain Up while still being stuck in the Validating state?

3. Has anyone experienced this behavior, and what was the root cause?

Any insights or suggestions would be appreciated.

[shubhamseth]

@AvinashU 

Staying in the Validating state for 12+ hours is not expected. Since restartService has completed and the ECC Queue is still being processed, the MID Server itself appears to be healthy.

Check the following:

• Verify whether the Validate transaction is waiting on another SystemCommand (such as Invalidate SystemCommands).
• Review the MID Server agent.log for any validation-related exceptions.
• Check for a backlog or stuck records in the ECC Queue related to the validation request.
• Confirm the MID Server can communicate with the instance after the restart (no proxy, SSL, or network issues).
• If everything looks healthy, try restarting the MID Server service manually and trigger validation again.

In this scenario, the issue is more likely that the validation workflow hasn't completed in the instance, rather than the MID Server itself being unhealthy.

[AvinashU]

I already performed above steps but same face same issue

[shubhamseth · Accepted solution]

@AvinashU Alright! In this case, can you restart the MID server service from host and check?