Latest posts for the topic "can not monitor the JMX port 9520 while the terracotta run on CentOS"

can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi, I can not monitor the JMX port 9520 while the terracotta run on CentOS. I use terracotta-generic-2.4.0.tar,my web container is jetty-6.1.5.althought the terracotta and jetty can run on the CentOS,i can't monitor the terracotta's jmx by another terracotta which is run on window. what's the problem? Thanks in advances. Joy.Cai

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

zeeiyer — GMT

We don't officially certify on CentOS - but since it is based on RedHat - it should work - I suppose you just confirmed that as well. What Exception do you encounter when you run the Admin Console (Swing GUI) on your Windows desktop: 1. Are you sure that the "host" (where the Terracotta server runs) and port (9520) are correctly specified. Can you ping the "host" from your windows box ? 2. Do the Terracotta versions of the Admin Client and the Terracotta server match ? Thanks.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi zeeiyer, 1. I encounter this exception :unable to connect to 192.168.0.12:9520 when I run the Admin Console (Swing GUI) on my Windows desktop.but I can success to telnet to 192.168.0.12 on the port 9520. 2. my Terracotta versions of the Admin Client is 2.4.0,the same as the Terracotta server (which is run on CentOS). Thanks. Joy.Cai

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

zeeiyer — GMT

I take it that in the tc-config.xml one is not specifying a different port for JMX services (the default is 9520, but you can override it)... Also there is an irritating bug, where sometimes you have to click twice on the Admin-Console "Connect" Push-Button to connect (the first attempt throws a timeout though, and not a "unable to connect" as you are reporting). Just for completeness sake wrt triaging we are doing here - i just wanted to ensure that the default jmx-port has not been overridden and u try connecting twice. Thx

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

tgautier — GMT

Also if possible we should try to rule out any network issues. I know that you said telnet succeeds, but the actual protocol is JMX so there could be other issues causing JMX to not connect that telnet is not helping with. Would it be possible to run an admin console on the localhost to ensure it works properly from the same machine?

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

gkeim — GMT

Can you successfully connect using jconsole?

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi,zeeiyer

I take it that in the tc-config.xml one is not specifying a different port for JMX services (the default is 9520, but you can override it)...

why? aside,no matter how many times i try to connect ,what i got is the same message: unable to connect....... Thx Joy.Cai

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi tgautier, maybe we should rule out the network issues,maybe is the network protocol issues.But it is possible to run the admin console on the localhost and it works well. Thx. Joy.Cai

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi gkeim, i can't connect using jconsole.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

hhuynh — GMT

This could be the result of a bad entry in /etc/hosts (see this bug here: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6209663 Hung-

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

gkeim — GMT

There's something incorrect about your networking setup on that machine. Here's a link to a conversation about the same problem: http://forum.java.sun.com/thread.jspa?forumID=58&tstart=0&threadID=288759&trange=15 If you can't find anything wrong with your /etc/hosts, you can turn on some JMX RMI logging like so: % export JAVA_OPTS=-DServerConnectionManager.logLevel=ALL % $TC_HOME/bin/admin.sh That may shed a clue.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Thanks.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi gkeim, i can connect using jconsole now,and can connect using terracotta from centOS to another centOS. but can't from windows to CentOS.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

gkeim — GMT

Check the networking on your Windows machine. I've seen this problem occur when the machine was in the wrong domain or workgroup.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

i can connect using jconsole from windows to CentOS.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

The problem is solved. thanks.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

gkeim — GMT

Do you mind telling me how you solved the problem? I would like to be able to help out others that run into the same problem. Was it related to the network configurations?

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

jeg1972 — GMT

It appears I have a similar problem... what was the resolution? John

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

ari — GMT

I saw this sort of behavior in the middle of a presentation at JavaOne this year. We later fiddled with my firewall settings on my Mac and it immediately connected. Sadly, I later could not connect and my firewall was disabled so this was indeed not the problem. But, we suspected the RMI library inside the product that we use to do password authentication of the admin console to the L2. Right now, I suspect more the localhost port binding. Try running admin console on the same machine as Terracotta's server process and connecting to localhost. Next, screenshot the output of "netstat -a -n" for us, and send us your config files so we can see which port you expect JMX services to bind to and which port they are indeed bound to. Hopefully, we will all find that the interface on which we are listening for connections can sometimes be too restrictive (localhost instead of * -- all interfaces). Thanks for your patience, --Ari

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

dmangot — GMT

The RMI server will return the address of whatever your hostname(1) is set to for clients connecting remotely. An easy test (on Unix or Cygwin/CMD.exe): telnet `hostname` 9520 If the first line says Trying 127... then your machine thinks that hostname is bound to a loopback address and you will not be able to remotely use the Admin console to monitor your Terracotta server. (but it will work fine running the Admin console to localhost on the same machine) If you would like to resolve this, make sure that whatever name the hostname(1) command returns is resolvable to an external accessible IP address. Hope that helps.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

Hi gkeim, this is my solution: config the servers like this: Code:

 
    
      9510
      9520
      data/server-data
      logs/server-logs
      9530
      
        
          permanent-store
        
      
    
    
    
      networked-active-passive
      
        5

config the clients like this: Code:


    production
  
  
    
      data/server-data
      logs/server-logs

and then modify this file start.sh like this: Code:

TC_SERVER=192.168.0.12
TC_CONFIG_PATH="${TC_SERVER}:9510"
. "${TC_INSTALL_DIR}"/bin/dso-env.sh -q

but now I got into another problem that after I use the jdk6,my terracotta client can not success to connect to the terracotta server of 192.168.0.12 why? thanks. Joy

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

jeg1972 — GMT

OK, my problem seems the same, I'm running two Terracotta servers on two CentOS 4.5 servers. I'm using the Windows Administrator Console to connect remotely to the two Terracotta servers due to the fact that X is not installed on the two Linux boxes. The result of netstat -a -n is: tcp 0 0 :::9520 :::* LISTEN When I first tried to run: telnet `hostname` 9520 I got: Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Which obviously meant I needed to alter the hosts file, which I did and it now resolves to the IP address of the server. I'm going to reboot the servers and try again and i'll post back to see if that makes any change. Regards John

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

jeg1972 — GMT

Well, I rebooted the servers, explicitly added the following into both config files: 9520 Started everything up as normal, and now I can successfully connect the Administrator Console to the remote Terracotta servers. So, the only things that I have changed are: 1) Make sure the /etc/hosts entry isn't like the default CentOS installation which is: 127.0.0.1 hostname.domain.local hostname localhost.domain localhost I changed it to: 127.0.0.1 localhost.domain localhost 192.168.1.X hostname.domain.local hostname 2) Explicitly add 9520 to the tc-config.xml That should solve the problem. Thanks for the help everyone... now back to my original thread :-) John

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

tgautier — GMT

Well I am glad we know what the problem is and that you are moving forward. I've added the relevant information into http://jira.terracotta.org/jira/browse/CDV-354. We'll see if there is anything to be done to make the console work ok on CentOS, if not we'll just know that there is a known issue with CentOS with an easy workaround.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

gkeim — GMT

Hi Joy.Cai, Don't use the shell variable TC_SERVER because that is used to specify that a client should connect to a particular server regardless of what the configuration states, useful for running the samples on multiple nodes to prove that Terracotta works! http://www.terracotta.org/confluence/display/docs1/Multi-node+Setup Change it to something like TC_SERVER_HOST.

Re:can not monitor the JMX port 9520 while the terracotta run on CentOS

Joy.Cai — GMT

OK,thanks.