Splunk Enterprise

ERROR LMTracker - failed to send rows, reason='Unable to connect to license master=https://XXXXX:8089

arielpconsolaci
Path Finder

Hi Splunk Community.

Good day. I am trying to add an AWS EC2 created instance with Splunk installed to it (standalone) as a slave to an on-prem Splunk License server. However, I am getting the error below.

ERROR LMTracker - failed to send rows, reason='Unable to connect to license master=https://XXXXXXX:8089 Error connecting: Connection reset by peer'

From checking, both Splunk are up in the master and slave. I can see a connection from a curl test in the slave to the master.

* Rebuilt URL to: telnet://XXXXXXX:8089/
* Trying 10.XX.XXX.XX...
* TCP_NODELAY set
* Connected to XXXXXXX (10.XX.XXX.XX) port 8089 (#0)

 

Please help advise.

Thanks All.

Cheers!

Labels (1)
0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...