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
Get Updates on the Splunk Community!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...