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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

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

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...