All Apps and Add-ons

Splunk App for VMWare Hydra Worker Reporting Jobs Have Expired

dlofstrom
Path Finder

I am attempting to install a demo of the Splunk App for VMWare (3.0.1) according to the Installation and Configuration manual and am having some trouble getting the Data Collection Node to work as documented.

I've deployed the DCN OVF, enabled forwarding via the CLI and added the DCN into the Search Head's app configuration. I don't see any of the respective inv, perf or other indexes increasing in size over several minutes. When I inspect ../var/log/splunk/hydra_worker_ta_vmware_collection_worker_alpha.log, I see the following lines appearing every few minutes:

ERROR [ta_vmware_collection_worker://alpha:1816] [getJob] job=job_887582cfa85311e3ac7e0050569571f3 has expired and will not be run.

I've tried re-deploying the DCN, though it exhibits the same behavior. Any help would be greatly appreciated.

Tags (1)
1 Solution

dlofstrom
Path Finder

Thanks. In my case, I think it was a problem with the time not being synced across all my Splunk instances. Yep.

View solution in original post

dlofstrom
Path Finder

Thanks. In my case, I think it was a problem with the time not being synced across all my Splunk instances. Yep.

prakash007
Builder

In your case...even DataCollections Nodes are supposed to be in a time sync with rest of the Splunk Instances...??

0 Karma

raziasaduddin
Path Finder

You can increase the TTL in limits.conf and savedsearches.conf

0 Karma
Get Updates on the Splunk Community!

Build Your First SPL2 App!

Watch the recording now!.Do you want to SPL™, too? SPL2, Splunk's next-generation data search and preparation ...

Exporting Splunk Apps

Join us on Monday, October 21 at 11 am PT | 2 pm ET!With the app export functionality, app developers and ...

[Coming Soon] Splunk Observability Cloud - Enhanced navigation with a modern look and ...

We are excited to introduce our enhanced UI that brings together AppDynamics and Splunk Observability. This is ...