Re: [akka-user] Re: Akka EC2 remoting

[Patrik Nordwall]

To verify that it is running with the right configuration you can try
setting this config property:
akka.log-config-on-start = on

http://doc.akka.io/docs/akka/2.3.9/scala/logging.html#Auxiliary_logging_options

/Patrik

On Fri, Apr 10, 2015 at 5:59 AM, Stefan Schmidt  wrote:

> Hi Jim,
>
> I am already running the instances on an EC2 cluster which gets its
> sibling IP addresses dynamically assigned. I run only one JVM per machine,
> so the cluster communicates on port 2551 througout. They are all within the
> same VPN and have no problems finding each other and connecting. So the
> akka cluster works just fine.
>
> However I still see these messages where the instances attempt to connect
> to the loopback address. Not sure why that is. I agree this has probably
> nothing to do specifically with EC2 but is more of a config issue.
>
> Stefan
>
>
>
> On Friday, April 10, 2015 at 5:12:23 AM UTC+10, Jim Hazen wrote:
>>
>> Try setting JVM system params.  For example, an early demo that I hacked
>> up looked like this.  It isn't on EC2, but I don't think that EC2 is really
>> your problem.  Hack out the stuff you don't care about and omit the -J if
>> not using sbt.
>>
>> Instance 1:
>> sbt -J-Dakka.remote.netty.tcp.hostname=localhost
>> -J-Dakka.cluster.seed-nodes.0=akka.tcp://CloudObjects-core@localhost:2552
>> -J-Dcom.sun.management.jmxremote.port= 
>> -J-Dcom.sun.management.jmxremote.authenticate=false
>> -J-Dcom.sun.management.jmxremote.ssl=false -J-Dcloudobjects.
>> journalLocation=akka.tcp://CloudObjects-core@localhost:2552/user/journal
>> run
>>
>> Instance 2:
>> sbt -J-Dakka.remote.netty.tcp.hostname=localhost
>> -J-Dakka.remote.netty.tcp.port=2553 -J-Dakka.cluster.seed-nodes.0=
>> akka.tcp://CloudObjects-core@localhost:2552 -J-Drole=backend
>> -J-Dcloudobjects.journalLocation=akka.tcp://CloudObjects-core@localhost:2552/user/journal
>> run
>>
>  --
> >> 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 akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Typesafe  -  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka EC2 remoting

[Jim Hazen]

Another thing that sometimes bites me on remote hosts that I'm not used to 
is a local software firewall.  Make sure the host itself isn't dropping 
traffic back to your listening ports.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka EC2 remoting

[Jim Hazen]

Try setting JVM system params.  For example, an early demo that I hacked up 
looked like this.  It isn't on EC2, but I don't think that EC2 is really 
your problem.  Hack out the stuff you don't care about and omit the -J if 
not using sbt.

Instance 1:
sbt -J-Dakka.remote.netty.tcp.hostname=localhost 
-J-Dakka.cluster.seed-nodes.0=akka.tcp://CloudObjects-core@localhost:2552 
-J-Dcom.sun.management.jmxremote.port= 
-J-Dcom.sun.management.jmxremote.authenticate=false 
-J-Dcom.sun.management.jmxremote.ssl=false 
-J-Dcloudobjects.journalLocation=akka.tcp://CloudObjects-core@localhost:2552/user/journal
 
run

Instance 2:
sbt -J-Dakka.remote.netty.tcp.hostname=localhost 
-J-Dakka.remote.netty.tcp.port=2553 
-J-Dakka.cluster.seed-nodes.0=akka.tcp://CloudObjects-core@localhost:2552 
-J-Drole=backend 
-J-Dcloudobjects.journalLocation=akka.tcp://CloudObjects-core@localhost:2552/user/journal
 
run

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka EC2 remoting

[Stefan Schmidt]

Hi Jim,

Thanks for your reply. 

Unfortunately the netty settings make no difference. I have set them to the 
same parameters as the initial akka cluster address but still see the 
issue. In fact the netty host address/port/sibling addresses are set 
dynamically when akka is started first (as described in the referenced 
article). All of that seems to work but for some reason akka keeps trying 
to connect to the loopback address.

Has anyone else seen this happening?

Cheers,
Stefan

On Monday, April 6, 2015 at 5:01:52 PM UTC+10, Jim Hazen wrote:
>
> Looks like you're trying to connect to a seed that isn't available. Be 
> sure that your remote.netty.tcp host and port settings match your seed node 
> setting.  They don't seem to here.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.