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!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...