Monitoring Splunk

Is there a known bug in DB Connect causing scheduled jobs to run twice?

rajinovat
New Member

Is there known bug in DB Connect causing scheduled jobs to run twice.. We had an incident over the weekend and messed up the report showing doubled events

0 Karma

musskopf
Builder

Not that I know... but are you using DB Dump or DB Tail?

If you're using DB Tail, it stores the last value at $SPLUNK_HOME/var/lib/splunk/persistentstorage/dbx, where each DB Tail configuration has its own directory and it saves the value for the "tailing" process insice state.xml.

If the process failed in the middle or something happen where this file wasn't updated, the next run will insert duplicated entries.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...