Re: IOError: [Errno 37] No locks available

stephenbaker · ‎08-24-2010

I am trying to migrate from 3.4.14 to 4.0.11 on Linux. It all goes smoothly, and it starts without error. However, when I go to look at splunkweb, it hangs for a while, then says:

500 Internal Server Error IOError: [Errno 37] No locks available

Can anyone rent me a clue as to what might be going on here?

Steve

gkanapathy · ‎08-24-2010

Probably your file locks (ulimit -x) is set too low. You should increase it (e.g., ulimit -x unlimited) for the Splunk process before starting Splunk, and preferably set it high permanently for the Splunk process user.

stephenbaker · ‎08-26-2010

Nope, ulimit -x was already set to unlimited.

IOError: [Errno 37] No locks available

Thanks for the Memories! Splunk University, .conf25, and our Community

Data Persistence in the OpenTelemetry Collector

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Are you a member of the Splunk Community?

IOError: [Errno 37] No locks available

Thanks for the Memories! Splunk University, .conf25, and our Community

Data Persistence in the OpenTelemetry Collector

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever