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!

Built-in Service Level Objectives Management to Bridge the Gap Between Service & ...

Wednesday, May 29, 2024  |  11AM PST / 2PM ESTRegister now and join us to learn more about how you can ...

Get Your Exclusive Splunk Certified Cybersecurity Defense Engineer Certification at ...

We’re excited to announce a new Splunk certification exam being released at .conf24! If you’re headed to Vegas ...

Share Your Ideas & Meet the Lantern team at .Conf! Plus All of This Month’s New ...

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