IOError: [Errno 37] No locks available

[tektsu]

I am trying to install Splunk 4.2.1 on a CentOS 5 (64-bit) box. It starts with no problem, but when I try to connect to SplunkWeb at port 8000, I get this error:

IOError: [Errno 37] No locks available

My limits are set as follows (note that file locks are unlimited):

cm@cmadmin-v04/cm/admin/tools/splunk-4.2.1/bin ) ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16384
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 65536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16384
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited


What do I need to change to make this work?

Thanks

[tektsu]

It is NFS. We have Splunk 3 running on NFS with no problems... I suppose Splunk 4 handles things differently. I'll see if I can move to a local filesystem.
Thanks

[jbsplunk]

http://splunk-base.splunk.com/answers/250/can-splunk-read-data-to-index-off-an-nfs-mount-can-splunk-...

Splunk generally does not recommend utilizing an NFS file system for indexing data, as there are significant chances of data corruption due to the inherent unreliability of NFS.

[dwaddle]

I would be curious what type of filesystem Splunk is installed on. Most ENOLCK errors seem to come from NFS filesystems and not having rpc.lockd running.

If you are running Splunk on a "normal" RHEL/Centos filesystem (ext2/ext3) I would recommend a support case.