Hi everyone, I'm facing an issue with a MID Server that has been in the Validating state
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi everyone,
I'm facing an issue with a MID Server that has been in the Validating state for more than 12 hours.
Environment
- MID Server: mid_demo
- Used for AWS Cloud Discovery
Current observations
- MID Server process is running on the EC2 instance.
- ECC Queue Processed count continues to increase (e.g., 770 → 781 → 802).
- The MID Server is actively processing other ECC messages.
However, I also see the following ECC Queue records:
| TopicCommandQueueState | |||
| SystemCommand | restartService | input | Ready |
| SystemCommand | restartService | output | Processed |
I observed similar behavior for the Invalidate (delete_mid_keypair) SystemCommand as well:
- Input record remains Ready.
- Output record is Processed.
Questions
- Is it normal for a MID Server to remain in Validating for more than 12 hours?
- Is it expected that the SystemCommand input record (restartService or delete_mid_keypair) remains in Ready while the corresponding output record is Processed?
- Should the input record eventually change to Processed, or is this expected behavior for internal SystemCommands?
- Has anyone encountered this issue before, and what was the root cause or resolution?
Any guidance would be greatly appreciated.
0 REPLIES 0