Deployment Architecture

script doesn't run. error Couldn't start command "" Resource temporarily unavailable

harry521
New Member

I have a few sh scripts scheduled to run every few min and those stop recently, and print this error in the log. To work around is simple as bouncing the forwarder instance, but it only works for a day or two and die again. Anyone has any thoughts?

Couldn't start command "/app/splunkforwarder/etc/apps/Splunk_TA_nix/bin/xxx.sh": Resource temporarily unavailable

Tags (1)
0 Karma

maciep
Champion

I am not a linux admin by any means, but I would look at your ulimits for the Splunk user that's running the forwarder. Maybe the scripts are finishing fast enough and your number of processes is growing until you hit those limits? Just a thought.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...