Why there are "java.io.IOException: No locks available" error messages with nfs mount ?

Solution In Progress - Updated -

Issue

Why after executing "/usr/bin/java -cp / Test" receives "java.io.IOException: No locks available" error message with nfs mount ?

# cat /var/log/messages |grep "lockd"
Jul  7 09:47:09 client01 kernel: lockd: cannot monitor server01       <<------- Cannot monitor lockd for server01 on client01
Jul  7 09:47:15 client01 kernel: lockd: cannot monitor server01
# cat /var/log/messages |grep "rpc.statd"
Jul  7 09:40:32 client01 rpc.statd[30409]: Version 1.2.3 starting
Jul  7 09:40:32 client01 rpc.statd[30409]: Initializing NSM state
Jul  7 09:40:32 client01 rpc.statd[30409]: Could not make a socket: (97) Address family not supported by protocol       <<--------
Jul  7 09:40:32 client01 rpc.statd[30409]: Could not make a socket: (97) Address family not supported by protocol
Jul  7 09:40:36 client01 rpc.statd[30409]: Caught signal 15, un-registering and exiting
Jul  7 09:40:36 client01 rpc.statd[31438]: Version 1.2.3 starting
Jul  7 09:40:36 client01 rpc.statd[31438]: Could not bind socket: (98) Address already in use     <<---------

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • NFSV4 & NFSV3
  • nfs-utils 1.2.3-39.el6.x86_64
  • Kernel 2.6.32-431.17.1.el6.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In