we have many scheduled jobs that terminate unexpectly, after adding
fetch_remote_search_log = disabled
in the limits.conf.
Hi community,
we are running splunk 6.4.4 with an index-cluster.
After we add the config fetch_remote_search_log = disabled at limits.conf many of our scheduled searches crashes with mostly with the message="The search job terminated unexpectedly.". No actions executed in the scheduler.log
sometimes the message is "Unable to read the job status.". No actions executed
It affects mostly a search that is partitioned in 8 jobs that are started parallel but we never had any issues with it for the last 5 years until we added this configuration.
After rolling back the errors vanished immediately and all seems fine again but this is a little bit unsatisfactory.
Does anybody have an idea what happens here?
best regards
