Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

I have setup an instance of Terracotta running in ec2, I can start it and it runs, but I cannot connect to it using the developer console. I am pretty sure I have all the firewall issues taken care of, I have port 9520 open for that server from my local ip. Anybody have any ideas?

we are aware of this issue. Don't have a solution yet. Sorry for the inconvenience. You might consider posting a JIRA. I don't think anyone has yet.

--Ari

Hello Ari,

I am having the same problem with Developer Console and some TC servers running on EC2. I am able to connect to one of the TC servers on EC2.. but I get "Timed-out" for the other one..

I am using Terracotta 3.0.1. Java on EC2 machine with TC server is the following version
Code:

 
  java -version
  java version "1.6.0_14"
  Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
  Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)

and it is m1.large instance. JMX port 9520 is open.

Thanks

Actually, this will work. In your tc-config.xml set the "host" parameter to be the public DNS name of your Terracotta server. (you need to have 9520 open to your developer console obviously). This way, that is what will be returned from the L2 to the developer console.

One caveat is that we usually recommend that your L1s (clients) pull their config from the L2 but if you did that in this situation you would have to pay for all traffic going in and out of the L2. Instead, copy the tc-config.xml to all the clients and set the "host" parameter to be the internal EC2 hostname of the Terracotta Server. It will be listening on all interfaces anyway. You will need to make sure your config files are all in sync of course.

With a low latency, decent bandwidth connection, it should work fine.

Cheers,

-Dave

Yes, I have internal DNS name for the host. That must be it.

Thank you a lot.

dmangot wrote:

Actually, this will work. In your tc-config.xml set the "host" parameter to be the public DNS name of your Terracotta server. (you need to have 9520 open to your developer console obviously). This way, that is what will be returned from the L2 to the developer console.

One caveat is that we usually recommend that your L1s (clients) pull their config from the L2 but if you did that in this situation you would have to pay for all traffic going in and out of the L2. Instead, copy the tc-config.xml to all the clients and set the "host" parameter to be the internal EC2 hostname of the Terracotta Server. It will be listening on all interfaces anyway. You will need to make sure your config files are all in sync of course.

With a low latency, decent bandwidth connection, it should work fine.

Cheers,

-Dave

I'm having a similar problem with the developer console. I'm having one TC server and one client (both running and working on EC2).

I used your advice and am now able to connect with the dev console by using the public DNS name.

However the dashboard shows:
"Cluster is not yet ready for action. Are all the minor groups active?"

Topology > Server Array > Minor group (tcserver) > tcserver shows:
Unknown host: ip-NumbersOfMyIP.ec2.internal

I have the same issue while connecting to the server array using developer console.

my tc_config.xml
---------------------
Code:

<server host="server1.xxx.com" name="server1">
 <data>/opt/terracotta/server-data</data>
 <l2-group-port>9530</l2-group-port>
 <dso>
 <persistence>
 <mode>permanent-store</mode>
 </persistence>
 </dso>
 </server>
 <server host="server2.xxx.com" name="server2">
 <data>/opt/terracotta/server-data</data>
 <l2-group-port>9530</l2-group-port>
 <dso>
 <persistence>
 <mode>permanent-store</mode>
 </persistence>
 </dso>
 </server>

while trying to start the server error shows as:
Code:

 [root@domU-12-31-38-00-8C-A3 terracotta]# ./bin/start-tc-server.sh -f tc-config.xml -n server1.fastlab.com
 2009-09-07 06:19:30,523 INFO - Terracotta 3.1.0-nightly, as of 20090812-150850 (Revision 13403 by cruise@su10mo5 from 3.1)
 2009-09-07 06:19:31,722 INFO - Configuration loaded from the file at '/opt/terracotta/tc-config.xml'.
 2009-09-07 06:19:32,138 INFO - Log file: '/opt/terracotta/logs/terracotta-server.log'.
 2009-09-07 06:19:35,744 INFO - Available Max Runtime Memory: 499MB
 2009-09-07 06:19:35.594::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
 2009-09-07 06:19:35.639::INFO:  jetty-6.1.8
 2009-09-07 06:19:36.764::INFO:  Started TerracottaConnector@0.0.0.0:0
 2009-09-07 06:19:36,256 ERROR - Unable to find local network interface for server1.fastlab.com
 [root@domU-12-31-38-00-8C-A3 terracotta]# ./bin/start-tc-server.sh -f tc-config.xml -n server1.fastlab.com
 2009-09-07 06:23:38,861 INFO - Terracotta 3.1.0-nightly, as of 20090812-150850 (Revision 13403 by cruise@su10mo5 from 3.1)
 2009-09-07 06:23:39,991 INFO - Configuration loaded from the file at '/opt/terracotta/tc-config.xml'.
 2009-09-07 06:23:40,374 INFO - Log file: '/opt/terracotta/logs/terracotta-server.log'.
 2009-09-07 06:23:43,779 INFO - Available Max Runtime Memory: 499MB
 2009-09-07 06:23:44.944::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
 2009-09-07 06:23:44.064::INFO:  jetty-6.1.8
 2009-09-07 06:23:44.167::INFO:  Started TerracottaConnector@0.0.0.0:0
 2009-09-07 06:23:44,476 ERROR - Unable to find local network interface for server1.xxx.com

when we using the internal ip 10.56.xx.86 as host the server starts without any problem but developer console can't show the connected servers.

we couldn't use the external ip 172.68.xx.82 also same error shows.

Any idea about this issue?

I encountered the same issue.

It seems that the TC Dev console actually tries to connect to the servers based on the host names listed in the remote tc-config.xml. So a config using internal IP/DNS addresses could not be connected to from outside. And on EC2 the public DNS is not bound to the local interface. You CAN connect from an EC2 instance to it's public address, though this will route the packets outside the local network, then back in, which might be feasible just for testing but certainly not for production.

One possibility would be for the TC dev console to rely on the TC server to tunnel data to/from other servers or aggregate it somehow.

Another would be to fire up the dev console on the EC2 instance with X forwarding set up. I did this but for some reason the console was extremely laggy (order of 30+ seconds), far more than the network lag or even other apps running over X. Also the dev console was pretty responsive before I connected, it only became lagged after connecting. So I think there is some kind of problem with the dev console in that environment, not sure exactly why.

Need associate Elastic IP with Terracotta Server and use Public DNS Name (ec2-75-101-XXX-XXX.compute-1.amazonaws.com) in tc-config.xml and Developer Console.

Details here:
http://alestic.com/2009/06/ec2-elastic-ip-internal