Deployment Architecture

LicenseMaster Connection issue

dbturner18
Loves-to-Learn Lots

Greetings,

I am having issues connecting to my LM.  The systems are in two different networks and I have confirmed via nmap and curl that I am able to connect to the remote LM box from the LS box.  I have also confirmed via netstat that the LS box is listening on  :8089

I am receiving this error when attempting to connected to the LM via splunk web:


Splunkd daemon is not responding: ('Error connecting to /services/licenser/localslave/license: The read operation timed out',)

Yes the LM system is online.  Yes the License is Enterprise.

The only think I see in splunkd.log on the LM is the following:

WARN HttpListener - Socket error from LS.ip:46822 while idling: Read Timeout

I have checked the pass4SymKey as well and they match between the LM and LS.

Is it possible that the ciphers are not the same between the two and the LM is not properly decrypting the password for auth?  Or would I see ssl/auth errors in the logs?

 

Thanks

 

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...