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!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...