Getting Data In

Cisco estreamer encore addon upgrade issue- Logs are no longer being received

dm1
Contributor
I recently upgraded the estreamer addon from version 3.0.0 to the 5.1.0 on our Splunk Heavy Forwarder. Since there were no specific upgrade steps mentioned to upgrade from old version to latest, I installed the addon over the existing one. 
 
However, after installing the new addon, we stopped receiving logs from IPS and got the below error when I ran following cmd 
/opt/splunk/etc/apps/TA-eStreamer/bin/splencore.sh test
ERROR below

Traceback (most recent call last):
  File "./estreamer/preflight.py", line 34, in <module>
    import estreamer.crossprocesslogging
  File "/opt/splunk/etc/apps/TA-eStreamer/bin/encore/estreamer/__init__.py", line 28, in <module>
    from estreamer.connection import Connection
  File "/opt/splunk/etc/apps/TA-eStreamer/bin/encore/estreamer/connection.py", line 23, in <module>
    import ssl
  File "/opt/splunk/lib/python3.7/ssl.py", line 98, in <module>
    import _ssl # if we can't import it, let the error propagate
ImportError: /opt/splunk/lib/python3.7/lib-dynload/_ssl.cpython-37m-x86_64-linux-gnu.so: undefined symbol: SSL_CTX_get0_param
Labels (1)
0 Karma

Qaddoumi
Loves-to-Learn Everything

i have same issue..

0 Karma

Tom_Lundie
Contributor

This error is interesting because it seems that Splunk's own Python environment is unable to initialise Splunk's own OpenSSL instance. What version of Splunk are you running?

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...