All Apps and Add-ons

DSDL App - Cannot establish test connection due to Python exception.

berrybob
Explorer

As title says, I'm having trouble to establish a connection with my Openshift namespace. Whenever I enter the details and hit Save and Test, an error pops up:

Setup Failed

An exception was thrown while dispatching the python script handler. .

 

I've been searching the python logs and it seems to be related to OpenSSL:

grep -B 5 -A 5 "mltk" .../var/log/splunk/python.log

->

ERROR You are linking against OpenSSL 1.0.2, which is no longer supported by the OpenSSL project. To use this version of cryptography you need to upgrade to a newer version of OpenSSL. For this version only you can also set the environment variable CRYPTOGRAPHY_ALLOW_OPENSSL_102 to allow OpenSSL 1.0.2.

As the error suggests, I tried to set a variable via command line, as well as through /splunk/etc/splunk-launch.conf but without success. Has anyone had this error before and knows how to solve?

 

Labels (2)
0 Karma
1 Solution

livehybrid
SplunkTrust
SplunkTrust

Hi @berrybob 

Just to confirm - you did CRYPTOGRAPHY_ALLOW_OPENSSL_102=1 in your /opt/splunk/etc/splunk-launch.conf? Did you then restart Splunk?

Once this is done this should allow OpenSSL 1.0.2. 

After this do you still get the exact same error - or is it different? 

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

View solution in original post

random
Engager

We had the same issue after an update, but the solution resolved it. Thank you!

0 Karma

berrybob
Explorer

Hi @livehybrid 

Could have sworn I did but now its working. Thanks for your help.

 

KR

0 Karma

livehybrid
SplunkTrust
SplunkTrust

Hi @berrybob 

Just to confirm - you did CRYPTOGRAPHY_ALLOW_OPENSSL_102=1 in your /opt/splunk/etc/splunk-launch.conf? Did you then restart Splunk?

Once this is done this should allow OpenSSL 1.0.2. 

After this do you still get the exact same error - or is it different? 

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...