maprcli returns error "ERROR (10009) could not connect to CLDB" in healthy cluster

Document created by wade on Feb 27, 2016
Version 1Show Document
  • View in full screen mode

Author: Nabeel Moidu

Original Publication Date: July 10, 2015

 

Environment

All environments below with WLS security enabled on the cluster:

  • 3.1.x
  • 4.0.1
  • 4.0.2
  • 4.1.0

 

Symptom
With security enabled in the cluster :

cat /opt/mapr/conf/mapr-clusters.conf 
nmkc secure=true nmkc1:7222 nmkc2:7222

A typical command response that looks like :

[root@nmk-centos-65-2 logs]# maprcli node list -columns svc,csvc 
ERROR (10009) -  Couldn't connect to the CLDB service. Check if at least one CLDB is running.

 

while in the CLDB logs, everything looks fine :

 

INFO AllowUpdatesThread [AllowUpdatesThread]: Allow updates on all volumes now

Testing the maprlogin password command at the time,

[root@nmk-centos-65-2 logs]# maprlogin authtest 
Attempting to pick up default credentials for cluster nmkc
Unable to authenticate as ticket is not available
[root@nmk-centos-65-2 logs]#

Root Cause
This is because the maprlogin command has not been run to obtain the security credentials on the node.

Solution
Obtain the maprlogin credentials on the node.

 

[root@nmk-centos-65-2 logs]# maprlogin end
[root@nmk-centos-65-2 logs]# maprlogin authtest
Attempting to pick up default credentials for cluster nmkc
Unable to authenticate as ticket is not available
[root@nmk-centos-65-2 logs]# maprlogin password
[Password for user 'root' at cluster 'nmkc': ]
MapR credentials of user 'root' for cluster 'nmkc' are written to '/tmp/maprticket_0'
[root@nmk-centos-65-2 logs]# maprlogin authtest
Attempting to pick up default credentials for cluster nmkc
Successfully obtained credentials.
[root@nmk-centos-65-2 logs]#

Attachments

    Outcomes