-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can not load page: MasterNotRunningException #19
Comments
my logs/log4j.log is empty, how can I turn on the debug log? |
you can try to change the loglevel from "WARN" to "INFO" in the file "conf/log4j.xml" (line 22) I recently received a E-Mail with a similar problem. I gave the following suggestions, but did never receive an answer if anything helped:
|
Hi Nils, I am seeing a similar issue. -Guru Medasani On Tue, May 7, 2013 at 7:58 AM, NiKu notifications@github.com wrote:
|
2013-05-07 16:12:10,228 INFO [application-akka.actor.default-dispatcher-1] ZooKeeper - Session: 0x23e564781076263 closed |
@meniku BTW, does hannibal support Kerberos authentication? |
Chris, Which HBase version are you using? Best Regards, On Tue, May 7, 2013 at 11:15 AM, Chris Huang notifications@git.luolix.topwrote:
|
@gdtm86 From the exception trace I can see that Hannibal is compiled for HBase 0.90 I wonder whether setting the hbase.master in conf/hbase-site.xml could help?
|
I tied this and still no luck. Seeing the same errors. -Guru On Wed, May 8, 2013 at 7:58 AM, NiKu notifications@github.com wrote:
|
@chenhsiu your stacktrace indicates that you compile Hannibal for HBase 0.90, for the packaged version, please use the following command to create the package
I actually don't know whether Hannibal supports Kerberos authentication since I never used it. From a quick look in the HBase Documentation it seams that you need to setup your hbase-site.xml properly. |
I just had a similiar issue when I built Hannibal for the wrong version. It did not work directly after I changed the version with HANNIBAL_HBASE_VERSION. I had to do a clean prior to rebuild Hannibal. The following made it work for me:
Does this help? |
Hi, I test it on HBase 0.94 without security and HANNIBAL work fine. Could you give me some idea ? Below is the information: TEST CASE 1: hbase-site.xml :
[hbase@ci-test-1 hannibal]$ ./start
HBase Master log:
TEST CASE 2: [root@ci-test-1 ~]# cat hannibal/conf/hbase-site.xml
[hbase@tmh6-ci-test-1 hannibal]$ ./start
|
Was there every an answer about Hannibal supporting Kerberos? |
@tzzhc4 @keyboardfann My ideas: case 1The log message:
Could indicate that the used hadoop version
to
and then rebuild the project? I think this is the solution to your first problem and this ticket. Thank you for providing the log-messages. case 2I really don't know why the class Instead of
it is documented like
Are you sure that your configuration is correct? |
The problem with the resolution of SecureRpcEngine seems to be that HBase 0.94 has a security profile. Seems as though the SecureRpcEngine is defined only when the security profile is defined. I tried to add the 0.94.14-security to the project/Build.scala, where it couldn't find it. But changing back to the 0.94.14 worked - and if I replace the hbase-0.94.14.jar with my hbase-0.94.14-security.jar - SecureRpcEngine is resolved. I also had to upgrade the hadoop-core, which I did to 1.0.4 prior to seeing your message. Looks like I'm still getting errors, but not sure if it is with my JAAS config or something else. |
Dear @meniku , Case 1
HMaster log:
About case 2 ,
|
Case 1Weird, I thought Hadoop 0.22 should have IPC version 4 already. Maybe you should try 0.23.9, the latest Hadoop 1 version I found . Case 2Sorry, all I can tell is that those class you reference |
Dear @meniku
|
I haven't attempted case 1, but regarding the case 2 I resolved the SecureRPC by the following:
I'm sure there are easier ways to do this, but I'm new to using ivy for the artifacts. My issue looks like it might stem from JAAS - it looks like the JAAS is authenticating with Kerberos, but then com.sun.security.jgss errors with a null principal. I did convert a test HBase cluster to use Kerberos, and Hannibal seems to be working with that test cluster, but not with my original cluster. Not sure if I didm't get everything converted to Kerberos on the test cluster. |
Dear @gshively ,
|
…er.info.port' for HBase >= 0.92 (defaulting to 60030) #19
60030 was hardcoded for HBase >= 0.92, I just pushed a commit to the If I am correct, there are two things left to fix to support Kerberos in Hannibal:
|
Dear @meniku ,
|
But..... I meet a new problem when i deploy hannibal to production cluster . We haver two namenode , two hbase master( it has active standby HA) and five zookeeper, when I start hannibal , I meet org.apache.hadoop.hbase.MasterNotRunningException again.......... Does hannibal support hbase HA?
HMaster log:
The keytab and auth is ok.
|
Does the problem still exist with Hannibal 0.10.1? https://github.com/sentric/hannibal/releases/tag/v.0.10.1 |
I am still facing issue with the kerberos and hannibal . Current HBASE version i am using is 1.2 with Cloudera CDH . Any help with steps to install hannibal with kerberos cluster is greatly appreciated. |
[ERROR] [04/02/2018 07:40:19.653] [application-akka.actor.default-dispatcher-3] [akka://application/user/updateMetricsActor] hconnection-0x362735ef518bf6c Unexpected KeeperException creating base node |
I have setup conf/hbase-site.xml properly, but get MasterNotRunningException as follows. Any clues?
! @6e7mlmi15 - Internal server error, for request [GET /] ->
play.core.ActionInvoker$$anonfun$receive$1$$anon$1: Execution exception [[MasterNotRunningException: Retried 10 times]]
at play.core.ActionInvoker$$anonfun$receive$1.apply(Invoker.scala:134) [play_2.9.1-2.0.4.jar:2.0.4]
at play.core.ActionInvoker$$anonfun$receive$1.apply(Invoker.scala:115) [play_2.9.1-2.0.4.jar:2.0.4]
at akka.actor.Actor$class.apply(Actor.scala:318) [akka-actor-2.0.2.jar:2.0.2] at play.core.ActionInvoker.apply(Invoker.scala:113) [play_2.9.1-2.0.4.jar:2.0.4]
at akka.actor.ActorCell.invoke(ActorCell.scala:626) [akka-actor-2.0.2.jar:2.0.2]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:197) [akka-actor-2.0.2.jar:2.0.2]
at akka.dispatch.Mailbox.run(Mailbox.scala:179) [akka-actor-2.0.2.jar:2.0.2]
at akka.dispatch.ForkJoinExecutorConfigurator$MailboxExecutionTask.exec(AbstractDispatcher.scala:516) [akka-actor-2.0.2.jar:2.0.2] at akka.jsr166y.ForkJoinTask.doExec(ForkJoinTask.java:259) [akka-actor-2.0.2.jar:2.0.2]
at akka.jsr166y.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:975) [akka-actor-2.0.2.jar:2.0.2]
at akka.jsr166y.ForkJoinPool.runWorker(ForkJoinPool.java:1479) [akka-actor-2.0.2.jar:2.0.2]
at akka.jsr166y.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104) [akka-actor-2.0.2.jar:2.0.2]
Caused by: org.apache.hadoop.hbase.MasterNotRunningException: Retried 10 times
at org.apache.hadoop.hbase.client.HBaseAdmin.(HBaseAdmin.java:120) ~[hbase-0.90.5.jar:0.90.5]
at models.HBase$class.withAdmin(HBase.scala:42) ~[hannibal_2.9.1-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
at models.hbase090.HBase090.withAdmin(HBase090.scala:9) ~[hannibal_2.9.1-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
at models.hbase090.HBase090.eachRegionServer(HBase090.scala:11) ~[hannibal_2.9.1-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
at models.Region$.all(Region.scala:71) ~[hannibal_2.9.1-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
at controllers.Application$$anonfun$index$1.apply(Application.scala:13) ~[hannibal_2.9.1-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
at controllers.Application$$anonfun$index$1.apply(Application.scala:12) ~[hannibal_2.9.1-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
at play.api.mvc.Action$$anon$1.apply(Action.scala:170) ~[play_2.9.1-2.0.4.jar:2.0.4]
at play.core.ActionInvoker$$anonfun$receive$1$$anonfun$6.apply(Invoker.scala:126) ~[play_2.9.1-2.0.4.jar:2.0.4]
at play.core.ActionInvoker$$anonfun$receive$1$$anonfun$6.apply(Invoker.scala:126) ~[play_2.9.1-2.0.4.jar:2.0.4]
at play.utils.Threads$.withContextClassLoader(Threads.scala:17) ~[play_2.9.1-2.0.4.jar:2.0.4]
at play.core.ActionInvoker$$anonfun$receive$1.apply(Invoker.scala:125) [play_2.9.1-2.0.4.jar:2.0.4]
... 11 common frames omitted
The text was updated successfully, but these errors were encountered: