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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...