All Apps and Add-ons

Error on NetApp Ontap App | Data Collection Node|hydra_gateway error

leesiangfong
New Member

Hi All,
I am installing NetApp Ontap App and facing the error below on Data Collection Node
OS: Centos 6.5 2.6.32-358.11.1.el6.x86_64 #

I found that port 8008 is unable to start on DCN.

Here is the error on /var/splunk/splunkd.log
04-08-2016 01:36:13.730 +0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py" Traceback (most recent call last):
04-08-2016 01:36:13.730 +0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py" File "/opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py", line 29, in
04-08-2016 01:36:13.730 +0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py" server = bootstrap_web_service(port, service_log_level, access_log_level)
04-08-2016 01:36:13.730 +0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py" File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_gateway.py", line 899, in bootstrap_web_service
04-08-2016 01:36:13.731 +0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py" from ssl import PROTOCOL_SSLv2, PROTOCOL_SSLv3, PROTOCOL_SSLv23, PROTOCOL_TLSv1
04-08-2016 01:36:13.731 +0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SA-Hydra/bin/bootstrap_hydra_gateway.py" ImportError: cannot import name PROTOCOL_SSLv2

Here is the error I found in index=_internal source=hydra error

2016-04-08 09:26:11,753 ERROR [ta_ontap_collection_scheduler://nidhogg] Problem with hydra scheduler ta_ontap_collection_scheduler://nidhogg:
'job_aggregate_execution_info'
Traceback (most recent call last):
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_scheduler.py", line 2136, in run
collection_manifest.sprayReadyJobs(self.node_manifest)
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_scheduler.py", line 735, in sprayReadyJobs
available_work_load, balanced_load = self._calculateLoadDistribution(active_workers, ready_jobs, node_job_infos)
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_scheduler.py", line 535, in _calculateLoadDistribution
self._update_execution_time(node_job_info["job_aggregate_execution_info"])
KeyError: 'job_aggregate_execution_info'

Any idea will be very much appreciated.

Thanks
Lee

0 Karma
1 Solution

trapti_splunk
Splunk Employee
Splunk Employee

Hi Lee,

This is again the SSL issue which we have with Splunk 6.4.

This required a change in Hydra. We have a fix for this in our new release.

View solution in original post

0 Karma

trapti_splunk
Splunk Employee
Splunk Employee

Hi Lee,

This is again the SSL issue which we have with Splunk 6.4.

This required a change in Hydra. We have a fix for this in our new release.

0 Karma

mhlesourd
New Member

Hi,

Any idea when the release is scheduled? Is there a workaround ?

Kind regards,

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...