NPM version: 2020.2.4
So, I have some 'legacy" Orion monitoring in SAM for monitoring Orion. One of the monitors is "SSL Listeners port Monitor" which checks TCP port 5671. Recently this isshowing as "down" because "the target machine actively refused it". The target machine is my primary Orion poller (set up in HA configuration)....
I go to the "Deployment Health" and both my primary and HA system are 'green'. I go to the "deployment health Checks" and some health checks are red and 'high' severity and I don't think were red before. I'm not sure if they're "always red" as I've heard some of these are not as... informative... as others. these checks are:
Connect to Messaging Service High
Last checked Jun 18, 2021 12:12:08 PM
### REDACTED HOSTNAME ###
Primary Orion Server
Ping Agent Management Service High
Last checked Jun 18, 2021 12:12:08 PM
### REDACTED HOSTNAME ###
Primary Orion Server
Ping Messaging Service Core High
Last checked Jun 18, 2021 12:12:08 PM
I can failover my HA cluster and it works.
Question:
- Are these "failing health checks" normal"or "ok"? The "remedy" next to the health check was to restart the 'Orion module Engine" and I did that and they did not go away. Port 5671 still was showing "connection refused".
- I'm seeing some forum posts indicating port 5671 is tied to RabbitMQ. ok, so what? My system shows "green" and everything looks good... except these failing health checks 
Should I bounce RabbitMQ or do something to make this port respond again? Normally i'd think the port is no longer used but it *was* responding before I applied the recent Windows OS patches for this month so I feel that Orion/RabbitMQ is using that port for something. I feel that if it were critical I'd see some other issues with the system.
