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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...