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!

Devesh Logendran, Splunk, and the Singapore Cyber Conquest

At this year’s Splunk University, I had the privilege of chatting with Devesh Logendran, one of the winners in ...

There's No Place Like Chrome and the Splunk Platform

WATCH NOW!Malware. Risky Extensions. Data Exfiltration. End-users are increasingly reliant on browsers to ...

Customer Experience | Join the Customer Advisory Board!

Are you ready to take your Splunk journey to the next level? 🚀 We invite you to join our elite squad ...