Error "No CLDB found to register with" printed repeatedly in NFS server log

Document created by jbubier Employee on Feb 7, 2016
Version 1Show Document
  • View in full screen mode

Author: Jonathan Bubier

 

Original Publication Date: February 12, 2015

 

The paths exported by MapR's NFS server are defined in /opt/mapr/conf/exports on each host running the NFS server.  In MapR v3.1 and earlier after modifying the exports definition the following errors may be seen in the NFS server log /opt/mapr/logs/nfsserver.log:

 

2014-03-14 21:18:45,2451 INFO nfsserver[16586] fs/nfsd/main.cc:590 NFS server

started ... pid=16586, uid=2000

2014-03-14 21:18:49,8268 INFO nfsserver[16586] fs/nfsd/nfsha.cc:750 No CLDB

found to register with: retry in 5000ms

2014-03-14 21:18:54,8279 INFO nfsserver[16586] fs/nfsd/nfsha.cc:750 No CLDB

found to register with: retry in 5000ms

2014-03-14 21:18:59,8291 INFO nfsserver[16586] fs/nfsd/nfsha.cc:750 No CLDB

found to register with: retry in 5000ms

2014-03-14 21:19:04,8302 INFO nfsserver[16586] fs/nfsd/nfsha.cc:750 No CLDB

found to register with: retry in 5000ms

2014-03-14 21:19:09,8314 INFO nfsserver[16586] fs/nfsd/nfsha.cc:750 No CLDB

found to register with: retry in 5000ms

This occurs even though the NFS server identifies the CLDB information for the cluster earlier in the NFS server log.  Ex:

 

2014-03-14 21:18:44,7478 INFO nfsserver[16586] fs/nfsd/main.cc:482 ***** NFS

server starting: pid=16586, mapr-version: 3.1.0.23338.GA *****

2014-03-14 21:18:44,7481 INFO nfsserver[16586] fs/nfsd/main.cc:496 ******* NFS

server MAPR_HOME=/opt/mapr, NFS_PORT=2049, NFS_MGMT_PORT=9998, NFSMON_PORT=9997

2014-03-14 21:18:44,7666 INFO nfsserver[16586] fs/nfsd/mount.cc:2074 Export

info: /mapr/my.cluster.com 127.0.0.1(rw)

2014-03-14 21:18:44,7684 INFO nfsserver[16586] fs/nfsd/mount.cc:1737 CLDB info:

192.168.1.1:7222 192.168.1.2:7222 192.168.1.3:7222

This issue is caused when a new export definition is added to the /opt/mapr/conf/exports file and the default export for '/mapr' is removed or commented out.  Ex:

 

# special path to export clusters in mapr-clusters.conf. To disable exporting,

# comment it out. to restrict access use the exports_control

#

#/mapr (rw)

 

#to export only certain clusters, comment out the /mapr & uncomment.

/mapr/my.cluster.com 127.0.0.1(rw)

As a workaround this issue can be resolved by exporting the '/mapr' path in addition to the existing exports and either restarting the NFS server or running maprcli nfsmgmt refreshexports.  This issue is addressed in MapR v3.1.1 and later.  If a fix is required for your MapR v3.1 deployment contact MapR Support and reference defect ID 13515. 

Attachments

    Outcomes