Hi @all,
We have a Splunk environment with one indexer and two DCNs (heavy forwarder) with version 6.2 installed.
One DCN is used for collecting Netapp data, the other one for VMware.
On the search head, we have configured both apps (Netapp ONTAP, VMware and VMware Addon).
The Netapp scheduler is working fine, but the VMware scheduler can't collect data.
2016-08-25 16:25:41,263 WARNING [ta_vmware_collection_scheduler://puff] Exiting current run of hydra scheduler, expecting to restart based on duration or interval
2016-08-25 16:25:41,264 INFO [ta_vmware_collection_scheduler://puff] Updated check point file=hydra_avg_execution_time.json successfully
2016-08-25 16:25:50,469 INFO [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] [configureGateway] setting gateway configuration on node=https://172.29.209.72:8089 to bind to port=8008...
2016-08-25 16:25:50,497 INFO [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] [configureGateway] successfully configured gateway on node=https://172.29.209.72:8089
2016-08-25 16:25:50,497 INFO [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] [establishGateway] attempting to connect to gateway=https://172.29.209.72:8008 for node=https://172.29.209.72:8089 ...
2016-08-25 16:25:51,474 INFO [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] [establishGateway] successfully connected to gateway=https://172.29.209.72:8008 for node=https://172.29.209.72:8089
2016-08-25 16:25:51,543 INFO [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] Correct number of heads=4 on node=https://172.29.209.72:8089
2016-08-25 16:25:54,500 INFO [ta_vmware_collection_scheduler://puff] Start process to get initial offset for number of jobs 0
2016-08-25 16:25:54,501 INFO [ta_vmware_collection_scheduler://puff] Total jobs are less than threashold value of worker(s) load, hence no need to set auto job offset
2016-08-25 16:25:57,094 INFO [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] New meta data is distributed: Owner: admin, Namespace: Splunk_TA_vmware, Name: metadata, Id: /servicesNS/nobody/Splunk_TA_vmware/configs/conf-hydra_metadata/metadata.
2016-08-25 16:25:57,102 ERROR [ta_vmware_collection_scheduler://puff] Problem with hydra scheduler ta_vmware_collection_scheduler://puff:
[HydraCollectionManifest] could not establish the time to next job run, forcing a rebuild...
Traceback (most recent call last):
File "/vol1/app/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_scheduler.py", line 2119, in run
time_to_next_job = collection_manifest.getTimeToNextJob()
File "/vol1/app/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_scheduler.py", line 449, in getTimeToNextJob
"[HydraCollectionManifest] could not establish the time to next job run, forcing a rebuild...")
ForceHydraRebuild: [HydraCollectionManifest] could not establish the time to next job run, forcing a rebuild...
2016-08-25 16:25:57,104 WARNING [ta_vmware_collection_scheduler://puff] Exiting current run of hydra scheduler, expecting to restart based on duration or interval
I can't find any issue. The ports are open and the network traffic is assigned on host.
↧