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 Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...