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!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...