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
Super Champion

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
Super Champion

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

Get Updates on the Splunk Community!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...