Getting Data In

Splunk forwarder input.conf interval issue

jotase
Observer

I have an issue with my splunk forwarder.  Inside the inputs.conf, the interval is set to run at 5 9 * * * .

So 09:05 daily if I did it correctly.  I restart splunk service as splunk.  The job will run ONE time at 09:05.

The only way I can get it to run as scheduled is if I put the interval in as seconds 86400.  Does anyone else have that problem?

Labels (1)
0 Karma

tshah-splunk
Splunk Employee
Splunk Employee

Was trying to understand if the schedule was defined within double quotes or not

---
If you find the answer helpful, an upvote/karma is appreciated
0 Karma

tshah-splunk
Splunk Employee
Splunk Employee

Hey @jotase ,

Can you confirm that the cron schedule was defined in proper format as mentioned in the inputs.conf doc:

https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Scripted_Input: 

To specify a cron schedule, use the following format:
  * "<minute> <hour> <day of month> <month> <day of week>"
  * Cron special characters are acceptable. You can use combinations of "*",
  ",", "/", and "-" to specify wildcards, separate values, specify ranges
  of values, and step values.


 

---
If you find the answer helpful, an upvote/karma is appreciated
0 Karma

jotase
Observer

yes it is in the body of my question "Inside the inputs.conf, the interval is set to run at 5 9 * * * " 

 

5 9 * * * 

0 Karma
Get Updates on the Splunk Community!

Splunkers, Pack Your Bags: Why Cisco Live EMEA is Your Next Big Destination

The Power of Two: Splunk &#43; Cisco at "Ludicrous Scale"   You know Splunk. You know Cisco. But have you seen ...

Data Management Digest – January 2026

Welcome to the January 2026 edition of Data Management Digest! Welcome to the January 2026 edition of Data ...

Splunk SOAR Now Available on Google Cloud Platform

We’re excited to announce that Splunk SOAR is now natively available as a SaaS solution on Google Cloud ...