Splunk Enterprise

Splunk2Nagios Add-on - request URL too long issue

maverick
Splunk Employee
Splunk Employee

After downloading the Splunk2Nagios add-on and testing the check_splunk script, I'm receiving the following url, which the script produces and no results are returned when I run this at the command-line:


./check_splunk search "sshd failed" -u admin -p changeme -c 2 -w 1


which produces this URL:

https://maverick.splunk.com:8000/en-US/app/launcher/home:8000/?q=sshd%20failed%20-u%20admin%20-p%20c...

When I paste this into the web browser, I'm getting the following error:


Secure Connection Failed
An error occurred during a connection to maverick.splunk.com:9000.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)


I am thinking that since the check_splunk script was created for Splunk v3.x and not for v4.x, the request url being generated is incorrect and needs to be updated to work with Splunk v4.x.

Can someone verify that this is a correct assessment, and/or let me know if they've figured out how to get this to work with v4.x?

the_wolverine
Champion

Are you actually running SplunkWeb over SSL?

What happens when you change https:// to http:// ?

skojt
Engager

ssl_error_rx_record_too_long is the response I get when I use https on a port that doesn't use SSL.

0 Karma

maverick
Splunk Employee
Splunk Employee

I get "Invalid view name requested: "home:8000". View names may only contain alphanumeric characters."

0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...