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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...