Getting Data In

estreamer stopped getting streams

richkappler
Path Finder

We are running estreamer 2.2.2 (by latest entry in changelog) on our ad-hoc search head, v. 6.54 with Defense Center v. 5.4.

estreamer had been running fine since installation, there have been no config or setting changes made to the app, but on Jan 11 we restarted splunk on the ad-hoc sh to implement some config changes (timeout settings) unrelated to estreamer. The app has stopped receiving from that point. I have verified that it is running, taking to the DC:

ss -tanp | grep XXXXX (pid of estreamer)
ESTAB 0 0 XXX.XXX.XXX.XXX:XXXXX XXX (correct ip and port of DC) users:(("estreamer_clien",pid=XXXXX,fd=3))

There have been no config or setting changes to the Defense Center, the only thing that has been done is Splunk restarted.

I've read Douglas Hurd's responses to many estreamer questions regarding upgrading the app if using Firepower 6.X but we are not.

0 Karma
1 Solution

richkappler
Path Finder

SOLVED - Reinstalled pkcs certificate, reentered password, now receiving IDS data

View solution in original post

0 Karma

richkappler
Path Finder

SOLVED - Reinstalled pkcs certificate, reentered password, now receiving IDS data

0 Karma

richkappler
Path Finder

Additional information I forgot to add in the main body:

I have disabled and re-enabled the app, I have run eStreamer/bin/estreamer_client.pl and it returns no errors, we had a maintenance window last night during which I restarted Splunk for other config changes again.

0 Karma
Get Updates on the Splunk Community!

Admin Your Splunk Cloud, Your Way

Join us to maximize different techniques to best tune Splunk Cloud. In this Tech Enablement, you will get ...

Cloud Platform | Discontinuing support for TLS version 1.0 and 1.1

Overview Transport Layer Security (TLS) is a security communications protocol that lets two computers, ...

New Customer Testimonials

Enterprises of all sizes and across different industries are accelerating cloud adoption by migrating ...