cancel
Showing results for 
Search instead for 
Did you mean: 

Data hub error - No root guardian

hka201181
Discoverer

Hi Experts,

I tested the new Data hub WAR "datahub-webapp-6.7.0.30-RC4.war" on my local environment and unfortunately I get the following error:

2020-07-03 14:22:28,025 [INFO] [a.r.a.t.ArteryTcpTransport] Remoting started with transport [Artery tcp]; listening on address [akka://DataHubActorSystem@127.0.0.1:2551] with UID [5686743047181104463] 2020-07-03 14:22:28,052 [INFO] [akka.cluster.Cluster] Cluster Node [akka://DataHubActorSystem@127.0.0.1:2551] - Starting up, Akka version [2.6.5] ... 2020-07-03 14:22:28,123 [INFO] [akka.cluster.Cluster] Cluster Node [akka://DataHubActorSystem@127.0.0.1:2551] - Registered cluster JMX MBean [akka:type=Cluster] 2020-07-03 14:22:28,123 [INFO] [akka.cluster.Cluster] Cluster Node [akka://DataHubActorSystem@127.0.0.1:2551] - Started up successfully 2020-07-03 14:22:28,171 [INFO] [akka.cluster.Cluster] Cluster Node [akka://DataHubActorSystem@127.0.0.1:2551] -No downing-provider-class configured, manual cluster downing required, see https://doc.akka.io/docs/akka/current/typed/cluster.html#downing 2020-07-03 14:22:28,221 [ERROR] [a.c.ClusterActorRefProvider] No root guardian at [akka.tcp://DataHubActorSystem@127.0.0.1:2551] java.lang.IllegalArgumentException: Wrong protocol of [akka.tcp://DataHubActorSystem@127.0.0.1:2551/], expected [akka] at akka.remote.RemoteActorRef.<init>(RemoteActorRefProvider.scala:668) at akka.remote.RemoteActorRefProvider.rootGuardianAt(RemoteActorRefProvider.scala:475) at akka.actor.ActorRefFactory.actorSelection(ActorRefProvider.scala:246) at akka.actor.ActorRefFactory.actorSelection$(ActorRefProvider.scala:240) at akka.actor.ActorCell.actorSelection(ActorCell.scala:410) at akka.cluster.SeedNodeProcess.$anonfun$receiveJoinSeedNode$1(SeedNodeProcess.scala:59) at akka.cluster.SeedNodeProcess.$anonfun$receiveJoinSeedNode$1$adapted(SeedNodeProcess.scala:58) at scala.collection.immutable.Set$Set1.foreach(Set.scala:95) at akka.cluster.SeedNodeProcess.receiveJoinSeedNode(SeedNodeProcess.scala:58) at akka.cluster.JoinSeedNodeProcess$anonfun$receive$2.applyOrElse(SeedNodeProcess.scala:270) at akka.actor.Actor.aroundReceive(Actor.scala:535) at akka.actor.Actor.aroundReceive$(Actor.scala:533) at akka.cluster.SeedNodeProcess.aroundReceive(SeedNodeProcess.scala:18) at akka.actor.ActorCell.receiveMessage(ActorCell.scala:575) at akka.actor.ActorCell.invoke(ActorCell.scala:545) at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:270) at akka.dispatch.Mailbox.run(Mailbox.scala:231) at akka.dispatch.Mailbox.exec(Mailbox.scala:243) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)

I'm using on my local environment:

- Toncat 8.5

- Java 1.8

Any idea about this error?

Thanks in advance,

Houssem

d_morelli
Explorer
0 Kudos

Hi,

did you find a solution for this problem?

We're facing the same issue with version 1811.

Thanks

Accepted Solutions (0)

Answers (6)

Answers (6)

hka201181
Discoverer

I added this property to fix the issue

akka.cluster.seed-nodes.0=akka://DataHubActorSystem@127.0.0.1:2551

roman_sz
Explorer
0 Kudos

FYI - issues is now fixed in patch 1811.24.
No need to use mentinoed workaround anymore.

roman_sz
Explorer
0 Kudos

I'm facing exactly same issue after patching DTH from 1811.13 to 1811.23 and I suspect that issue was backported from higher version, noticed by SAP but fix was NOT backported to 18x version.
We had reported that to SAP and waiting for answer as it's clearly a product issue -> https://cxjira.sap.com/browse/ECP-5123

d_morelli
Explorer
0 Kudos

Hi,

in our case to solve the issue we had to create a setenv.sh file in the tomcat bin folder with the following data:

export CATALINA_OPTS="$CATALINA_OPTS -Ddatahub.cluster.seed.hostname=127.0.0.1"
export CATALINA_OPTS="$CATALINA_OPTS -Ddatahub.cluster.node.akka-port=2552"
export CATALINA_OPTS="$CATALINA_OPTS -Ddatahub.cluster.seed.akka-port=2551"
export CATALINA_OPTS="$CATALINA_OPTS -Ddatahub.cluster.node.hostname=127.0.0.1"
export CATALINA_OPTS="$CATALINA_OPTS -Dconfig.resource=datahub_cluster_seed.conf"

Hope it help.

Daniele

sbsamuell
Explorer
0 Kudos

Hi Daniele,

This solution worked very well for us too.

Really thanks!

sbsamuell
Explorer
0 Kudos

Hi guys, some news about this topic?

I have the DH installed with version 1808.05 and when applying the patch 1808.25 I have the same error.

Thanks.

markholmniels
Explorer
0 Kudos

Hi,

Did you find a solution?

We are having the same issue.

Thanks

Mark