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!

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...

State of Splunk Careers 2024: Maximizing Career Outcomes and the Continued Value of ...

For the past four years, Splunk has partnered with Enterprise Strategy Group to conduct a survey that gauges ...

Data-Driven Success: Splunk & Financial Services

Splunk streamlines the process of extracting insights from large volumes of data. In this fast-paced world, ...