You should use the machine's own ip address in the hostname property. /Patrik
On Tue, Apr 19, 2016 at 3:13 AM, Scalaian <[email protected]> wrote: > By following Akka documents, I can start two actors(front-end and > back-end) on the same machine, and they can talk to each other. However, > when I tried to deploy back-end actor to another machine(Linux), I hit > error of start remoting: > > ============ Multiple main classes detected, select one to run: > [1] com.goticks.BackendMain > [2] com.goticks.BackendRemoteDeployMain > [3] com.goticks.FrontendMain > [4] com.goticks.FrontendRemoteDeployMain > [5] com.goticks.FrontendRemoteDeployWatchMain > [6] com.goticks.SingleNodeMain > > > Enter number: 2 > > > [info] Running com.goticks.BackendRemoteDeployMain > [DEBUG] [04/18/2016 15:54:11.554] [run-main-0] [EventStream(akka://backend)] > logger log1-Logging$DefaultLogger started > [DEBUG] [04/18/2016 15:54:11.555] [run-main-0] [EventStream(akka://backend)] > Default Loggers started > [INFO] [04/18/2016 15:54:11.591] [run-main-0] [akka.remote.Remoting] Starting > remoting > [ERROR] [04/18/2016 15:54:11.748] > [backend-akka.remote.default-remote-dispatcher-5] > [NettyTransport(akka://backend)] failed to bind to /192.168.1.9:2551, > shutting down Netty transport > [ERROR] [04/18/2016 15:54:11.757] [run-main-0] [akka.remote.Remoting] > Remoting error: [Startup failed] [ > akka.remote.RemoteTransportException: Startup failed at > akka.remote.Remoting.akka$remote$Remoting$$notifyError(Remoting.scala:136) > at akka.remote.Remoting.start(Remoting.scala:201) > at > akka.remote.RemoteActorRefProvider.init(RemoteActorRefProvider.scala:184) > at akka.actor.ActorSystemImpl.liftedTree2$1(ActorSystem.scala:663) > at akka.actor.ActorSystemImpl._start$lzycompute(ActorSystem.scala:660) > at akka.actor.ActorSystemImpl._start(ActorSystem.scala:660) > at akka.actor.ActorSystemImpl.start(ActorSystem.scala:676) > at akka.actor.ActorSystem$.apply(ActorSystem.scala:143) > at akka.actor.ActorSystem$.apply(ActorSystem.scala:120) > at > com.goticks.BackendRemoteDeployMain$.delayedEndpoint$com$goticks$BackendRemoteDeployMain$1(BackendRemoteDeployMain.scala:9) > at > com.goticks.BackendRemoteDeployMain$delayedInit$body.apply(BackendRemoteDeployMain.scala:6) > at scala.Function0$class.apply$mcV$sp(Function0.scala:34) > at > scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12) > at scala.App$$anonfun$main$1.apply(App.scala:76) > at scala.App$$anonfun$main$1.apply(App.scala:76) > at scala.collection.immutable.List.foreach(List.scala:381) > at > scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35) > at scala.App$class.main(App.scala:76) > at > com.goticks.BackendRemoteDeployMain$.main(BackendRemoteDeployMain.scala:6) > at > com.goticks.BackendRemoteDeployMain.main(BackendRemoteDeployMain.scala) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at sbt.Run.invokeMain(Run.scala:67) > at sbt.Run.run0(Run.scala:61) > at sbt.Run.sbt$Run$$execute$1(Run.scala:51) > at sbt.Run$$anonfun$run$1.apply$mcV$sp(Run.scala:55) > at sbt.Run$$anonfun$run$1.apply(Run.scala:55) > at sbt.Run$$anonfun$run$1.apply(Run.scala:55) > at sbt.Logger$$anon$4.apply(Logger.scala:85) > at sbt.TrapExit$App.run(TrapExit.scala:248) > at java.lang.Thread.run(Unknown Source) > Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: > /192.168.1.9:2551 > at > org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272) > at > akka.remote.transport.netty.NettyTransport$$anonfun$listen$1.apply(NettyTransport.scala:410) > at > akka.remote.transport.netty.NettyTransport$$anonfun$listen$1.apply(NettyTransport.scala:406) > > > 192.168.1.9 is another machine. > > In backend.conf: > remote { > enabled-transports = ["akka.remote.netty.tcp"] > > netty.tcp { > #hostname = "0.0.0.0" > hostname = "192.168.1.9" > port = 2551 > } > } > > > I have one basic question, when deploy and start a remote actor on remote > JVM, do we need user login information to remote machine so that we can > remotely start actor/JVM? > > Thanks, > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: > http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Patrik Nordwall Akka Tech Lead Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
