All Apps and Add-ons

Issue while executing client_check.py

sivakumarispec
New Member

Configured the eStreamer app in Splunk with no issues. Cert is copied over to the splunk. Verified port 8302 is open.

But when i run the scriot clieni_check.py seeing the below error
Setting up auth certificate

SFPkcs12 : Processing /home/splunk/bin/scripts/10.0.0.201.pkcs12
SFPkcs12 : Writing ./server.crt
SFPkcs12 : Writing ./server.key
Retrieving metadata from file
Starting bookmark is 1398245642
Connecting to 10.0.0.136 port 8302
Can't connect to 10.0.0.136 port 8302: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)

0 Karma

cgrady_sf
Path Finder

This sounds like it may be an issue with the Defense Center not accepting the connection; most likely due to the Splunk system IP not matching that of the client certificate when it was generated. When you generated the certificate, did you use a hostname? If so, can the DC match the hostname to that of the Splunk system the eStreamer client is running on? Keep in mind any NATs that may be in there as well.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...