topic Re: Cluster Manager Not Reachable in Splunk Enterprise

Cluster Manager Not Reachable

SplunkNinja — Mon, 10 Aug 2026 16:26:19 GMT

From Splunk Monitoring Console (MC), I am seeing the Cluster Manager Not Reachable. I believe this was previously working. My servers are running Splunk Enterprise 10.0.9.

Re: Cluster Manager Not Reachable

richgalloway — Mon, 10 Aug 2026 16:47:54 GMT

Here are some things to try.

Verify the CM is still running.
Verify the CM is a search peer of the MC.
Confirm there are no pending changes waiting to be applied in the MC.
Confirm the MC is still allowed to connect to the CM (new firewall rule, perhaps).
Check the MC's logs to see if reports any messages when trying to contact the CM.
Restart the Splunk instance running the CM.
Restart the Splunk instance running the MC.

If you still can't figure it out, post a reply with more detail.

Re: Cluster Manager Not Reachable

SplunkNinja — Mon, 10 Aug 2026 21:41:28 GMT

Here are some more info:

Verify the CM is still running -> yes CM is running
Verify the CM is a search peer of the MC -> yes CM is search peer of the MC
Confirm there are no pending changes waiting to be applied in the MC -> I do not see any pending changes
Confirm the MC is still allowed to connect to the CM (new firewall rule, perhaps) -> I confirmed a curl from MC to CM is successful on tcp/8089
Check the MC's logs to see if reports any messages when trying to contact the CM. From the CM I am seeing these messages:

8-10-2026 20:33:25.292 +0000 ERROR HttpClientRequest [7217 LMTrackerExecutorWorker-0] - HTTP client error=Connection refused while accessing server=https://<LM>:8089 for request=https://<LM>:8089/services/masterlm/usage.
08-10-2026 20:33:25.292 +0000 WARN HttpClientRequest [7217 LMTrackerExecutorWorker-0] - Returning error HTTP/1.1 502 Connection refused
08-10-2026 20:33:25.292 +0000 ERROR LMTracker [7217 LMTrackerExecutorWorker-0] - failed to send rows, reason='Unable to connect to license manager=https://<LM>:8089 Connection refused

Restart the Splunk instance running the CM -> I restarted and even deleted the CM on the LM and re-added
Restart the Splunk instance running the MC -> I restarted the MC

Re: Cluster Manager Not Reachable

PickleRick — Tue, 11 Aug 2026 11:11:01 GMT

Obviously you have some connectivity problems with your LM or simply your LM is down. I haven't had this kind of problems lately but I suppose if you restarted your CM _and_ it wasn't able to contact LM to confirm that your installation is actually licensed for cluster operations it _might_ refuse to work.

Re: Cluster Manager Not Reachable

SplunkNinja — Tue, 11 Aug 2026 14:34:49 GMT

My LM and MC are on the same server. The MC shows all instances have Status Up including the CM server. But from the MC Indexer Clustering Status, the Cluster Manager Not Reachable message is seen.

We have Splunk Enteprise licensing that allows for Clustering.

Re: Cluster Manager Not Reachable

PickleRick — Tue, 11 Aug 2026 16:10:33 GMT

Yes, but if CM cannot contact LM, it might not be aware of the fact that your license supports clustering.

Re: Cluster Manager Not Reachable

isoutamo — Mon, 17 Aug 2026 07:42:22 GMT

You said that you LM and MC are on same server. Are those actually same instance or different (based on log I suppose that those are different splunkd instances). Then you should check that those ports are ok and not same for both server. Now it try to connect to port 8089 and if this is it itself it obviously cannot access LM which could be on some other port.

Re: Cluster Manager Not Reachable

SplunkNinja — Mon, 17 Aug 2026 21:10:51 GMT

My LM and MC are on the same server instance. The CM is on another server instance. I opened a Splunk Support ticket, and the connectivity is good using CLI commands.

We have escalated to a Splunk Dashboard SME for further troubleshooting. Thanks @isoutamo , @PickleRick , and @richgalloway