AnsweredAssumed Answered

Couldn't connect to the CLDB service

Question asked by fredrik_emilsson on Jun 18, 2012
Latest reply on Jun 19, 2012 by fredrik_emilsson
Hello,

  I'm trying to setup a small mapr cluster on three ubuntu servers (following instructions on http://www.mapr.com/doc/display/MapR/M3+-+Ubuntu).

  When I do deployment step 11 (/opt/mapr/bin/maprcli acl edit -type cluster -user mu:fc) it failes. I have tried many times and have waited for more than an hour. I took a look in the /opt/mapr/logs/maprcli-root-0.log file and it says:

Header: hostName: rackable11.cblan.mblox.com, Time Zone: Central European Time, processName: MapRCLI, processId: 27225, MapR Build Version: 1.2.7.14133.GA
2012-06-19 09:47:43,708 INFO  com.mapr.cliframework.driver.CLIMainDriver [main]: [acl, edit, -type, cluster, -user, mu:fc]
2012-06-19 09:47:43,737 INFO  com.mapr.baseutils.cldbutils.CLDBRpcCommonUtils [main]: init
2012-06-19 09:47:43,750 ERROR com.mapr.baseutils.cldbutils.CLDBRpcCommonUtils getDataForParticularCLDB [main]: CLDB Host: 192.168.0.188, CLDB IP: 7222 is READ_ONLY CLDB. Trying another one
2012-06-19 09:47:43,752 INFO  com.mapr.baseutils.cldbutils.CLDBRpcCommonUtils [main]: Bad CLDB credentials removed: CLDB Host: 192.168.0.188, CLDB IP: 7222
2012-06-19 09:47:43,753 INFO  com.mapr.cliframework.driver.CLIMainDriver [main]: ERROR (10009) -  Couldn't connect to the CLDB service

I have a CLDB service active:

root@rackable11:/home/mu# ps -ef | grep CLDB
root      8111     1  0 08:59 ?        00:00:07 java -server -Xmx639m -XX:ErrorFile=/opt/cores/hs_err_pid%p.log -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/cores -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ThreadStackSize=128 -Dlog4j.configuration=file:/opt/mapr/conf/log4j.cldb.properties -Dlog.file=/opt/mapr/logs/cldb.log -Dcldb.role.balancer.log.file=/opt/mapr/logs/cldbrolebalancer.log -Dcldb.disk.balancer.log.file=/opt/mapr/logs/cldbdiskbalancer.log -Dcldb.time.skew.log.file=/opt/mapr/logs/timeskew.log -Djava.library.path=/opt/mapr/lib -classpath /opt/mapr:/opt/mapr/conf:/opt/mapr/lib/adminuiapp-0.1.jar:/opt/mapr/lib/ant-1.7.1.jar:/opt/mapr/lib/baseutils-0.1.jar:/opt/mapr/lib/cldb-0.1.jar:/opt/mapr/lib/cliframework-0.1.jar:/opt/mapr/lib/commons-codec-1.4.jar:/opt/mapr/lib/commons-el-1.0.jar:/opt/mapr/lib/commons-email-1.2.jar:/opt/mapr/lib/commons-logging-1.0.4.jar:/opt/mapr/lib/commons-logging-api-1.0.4.jar:/opt/mapr/lib/eval-0.5.jar:/opt/mapr/lib/globalfsck-0.1.jar:/opt/mapr/lib/google-collect-1.0.jar:/opt/mapr/lib/hadoop-metrics-0.20.2-dev.jar:/opt/mapr/lib/jasper-compiler-5.5.12.jar:/opt/mapr/lib/jasper-runtime-5.5.12.jar:/opt/mapr/lib/jetty-6.1.14.jar:/opt/mapr/lib/jetty-plus-6.1.14.jar:/opt/mapr/lib/jetty-util-6.1.14.jar:/opt/mapr/lib/JPam-1.1.jar:/opt/mapr/lib/json-20080701.jar:/opt/mapr/lib/jsp-2.1.jar:/opt/mapr/lib/jsp-api-2.1.jar:/opt/mapr/lib/junit-3.8.1.jar:/opt/mapr/lib/junit-4.5.jar:/opt/mapr/lib/kvstore-0.1.jar:/opt/mapr/lib/libprotodefs.jar:/opt/mapr/lib/log4j-1.2.14.jar:/opt/mapr/lib/log4j-1.2.15.jar:/opt/mapr/lib/logging-0.1.jar:/opt/mapr/lib/mail.jar:/opt/mapr/lib/maprbuildversion.jar:/opt/mapr/lib/maprcli-0.1.jar:/opt/mapr/lib/maprsecurity-0.1.jar:/opt/mapr/lib/maprutil-0.1.jar:/opt/mapr/lib/protobuf-java-2.3.0-lite.jar:/opt/mapr/lib/servlet-api-2.5-6.1.14.jar:/opt/mapr/lib/volumemirror-0.1.jar:/opt/mapr/lib/warden-0.1.jar:/opt/mapr/lib/zookeeper-3.3.2.jar:/opt/mapr/hadoop/hadoop-0.20.2/lib/hadoop-0.20.2-dev-core.jar:/opt/mapr/hadoop/hadoop-0.20.2/lib/maprfs-0.1.jar -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7220 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dpid=8018 -Dpname=cldb -Dmapr.home.dir=/opt/mapr com.mapr.fs.cldb.CLDB /opt/mapr/conf/cldb.conf

Any idea about what the problem could be?

  Regards,
    Fredrik

Outcomes