|
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: When I paste this into the web browser, I'm getting the following error: Secure Connection Failed 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? |
|
Are you actually running SplunkWeb over SSL? What happens when you change https:// to http:// ? I get "Invalid view name requested: "home:8000". View names may only contain alphanumeric characters."
(22 Jul '10, 21:04)
maverick ♦
ssl_error_rx_record_too_long is the response I get when I use https on a port that doesn't use SSL.
(11 Jan, 05:37)
skojt
|
