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!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...