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!

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...

New Year. New Skills. New Course Releases from Splunk Education

A new year often inspires reflection—and reinvention. Whether your goals include strengthening your security ...

Splunk and TLS: It doesn't have to be too hard

Overview Creating a TLS cert for Splunk usage is pretty much standard openssl.  To make life better, use an ...