Security

IOError: [Errno 37] No locks available

stephenbaker
Engager

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

Tags (1)

gkanapathy
Splunk Employee
Splunk Employee

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
Engager

Nope, ulimit -x was already set to unlimited.

0 Karma
Get Updates on the Splunk Community!

Splunk APM: New Product Features + Community Office Hours Recap!

Howdy Splunk Community! Over the past few months, we’ve had a lot going on in the world of Splunk Application ...

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

A Guide To Cloud Migration Success

As enterprises’ rapid expansion to the cloud continues, IT leaders are continuously looking for ways to focus ...