All Apps and Add-ons

Database Output works manually, but scheduling it does not work

sheltomt
Path Finder

To clarify, we have scheduled Outputs that are working, to the same database but different tables.

We have a problem one, however. You can run the search manually, verify that it works. You can then pipe it to the dbxoutput command, specifying the name of the output, and that works fine.

As soon as you go into the Output and put a cron schedule in there, it fails. The only entry in the logs is "org.easybatch.core.job.BatchJob - Job 'xxx' finished with status: FAILED ". It fails immediately, with that error message occuring in .3 seconds.

Anyone seen this?

Tags (2)
Get Updates on the Splunk Community!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...