Our issue was triggered by the mongodb crashing on the Conductor which had a knock on effect to the mDNS process, among others.
It was resolved by removing a corrupted file in the backend database. In the meantime we failed over to our standby Conductor, TAC removed the file on the primary Conductor and we waited 24hrs for the Conductors to properly sync and then failed back. By then all of the process were back running and the Airgroup tables repopulated.
Original Message:
Sent: Oct 13, 2023 11:23 AM
From: Dan Prante
Subject: Airgroup stats not populating on controller
Hi Adam. We are experiencing the same symptoms since upgrading to 8.10.0.8. As of now TAC is stumped. Has this been resolved for you? If so, do you have a case number that we can reference?
Thanks,
Dan
Original Message:
Sent: Jun 28, 2023 03:54 PM
From: AdamNewsonCU
Subject: Airgroup stats not populating on controller
After reloading the Conductor and the mDNS process multiple times the process will not run properly:
/mswitch/bin/mdns PROCESS_NOT_RESPONDING_CRITICAL
I've created a TAC case - but please let me know if there are any other suggestions.
Original Message:
Sent: Jun 28, 2023 11:18 AM
From: AdamNewsonCU
Subject: Airgroup stats not populating on controller
Running commands such as:
show airgroupservice
show airgroup servers/ users/ status
+more and producing the following output:
Module Multicast DNS Listener is busy. Please try later
I've noticed the mDNS process didn't restart properly post an upgrade to 8.10.0.7:
/mswitch/bin/mdns PROCESS_NOT_RESPONDING_CRITICAL - 0 240 3 Mon Jun 19 08:14:07 2023
Restarted and now is running as normal:
/mswitch/bin/mdns PROCESS_RUNNING - 1 240 3 Wed Jun 28 15:58:12 2023
However still no statistics are generating on the controller 30mins later, with the same output of 'Module Multicast DNS Listener is busy. Please try later'.
We have a test cluster and a secondary live cluster all running 8.10.0.7 and this is not impacting them. They are producing output and statistics as normal. The only difference being controller models in the other two clusters. TAC case?
Cluster with the issue:
2x Conductors - MM-HW-10K
14x MCs spread over 2 sites - all 7240XM