Hello,
Over the holidays one of the two vMobility Masters I have in an Active-Passive cluster went down.
Upon return from holiday, I received reports from users that they could no longer use various casting services (AirPlay, etc.) on the network.
I looked into it and found that on my vMM01 Master, these services were stuck in intializing:
Results of show process monitor statistics | include Initializing
And the mDNS service was stuck in a PROCESS_NOT_RESPONDING_CRITICAL state:
Result of show process monitor statistics | include NOT
I logged into my slave, vMM02 and ran the same commands and all services are running properly.
I did a reload on vMM01 to try to reinit the database and get the services up and running. I monitored their status as the vMM01 completed booting, all services above stayed in initialziing for a while, then the mDNS returned to it's not responding state.
I presume this is because it cannot write temporary mDNS clients to the Mongo DB.
I've created a ticket with the TAC but am wondering what the best practice for promoting my MM02 to master for the time being until I can get the database issue resolved.
I presume it is #>halt but wanted to confirm this with the community before I fire it off.
Thanks for your time.