Skip to main content

Glassfish Error trying to start instance on ssh node

2 replies [Last post]
betox
Offline
Joined: 2013-11-26
Points: 0

Hi all.
I followed the steps posted here http://docs.oracle.com/cd/E18930_01/html/821-2432/gkybx.html to configure a glassfish cluster using ssh under CentOS 6.4 x86_64.
But when I try to start the cluster this is the result

---------------------------------------------------------------------------------------------------------------------
remote failure: i2: Timed out waiting for i2 to start.

The command start-instance failed for: i2
Command start-cluster failed.
---------------------------------------------------------------------------------------------------------------------

If I try to start the cluster again this is what I get

---------------------------------------------------------------------------------------------------------------------
asadmin> start-cluster
Enter admin user name> admin
Enter admin password for user "admin">
Enter the value for the clusterName operand> c1
remote failure: i2: Could not start instance i2 on node n2 (node2).

Command failed on node n2 (node2): CLI801 Instance is already synchronized
There is a process already using the admin port 24848 -- it probably is another instance of a GlassFish server.
Command start-local-instance failed.

To complete this operation run the following command locally on host node2 from the GlassFish install location /srv/glassfish3:

bin/asadmin start-local-instance --node n2 --sync normal i2

The command start-instance failed for: i2
Command start-cluster failed.
---------------------------------------------------------------------------------------------------------------------

I checked the ports used by programs (netstat -tulnp | grep tcp) and this was the result

---------------------------------------------------------------------------------------------------------------------
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:49217 0.0.0.0:* LISTEN -
tcp 0 0 :::39947 :::* LISTEN -
tcp 0 0 :::28686 :::* LISTEN 3604/java
tcp 0 0 :::111 :::* LISTEN -
tcp 0 0 :::24848 :::* LISTEN 3604/java
tcp 0 0 :::28080 :::* LISTEN 3604/java
tcp 0 0 :::28181 :::* LISTEN 3604/java
tcp 0 0 :::22 :::* LISTEN -
tcp 0 0 ::1:631 :::* LISTEN -
tcp 0 0 :::27676 :::* LISTEN 3604/java
tcp 0 0 :::9122 :::* LISTEN 3604/java
----------------------------------------------------------------------------------------------------------------------

What could be the problem that I can't start instances on ssh nodes?

Any Help will be apreciated.

Thanks!

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
boernd
Offline
Joined: 2011-11-08
Points: 0

Hi,

maybe some kind of network issue (firewall)? As far as I know the DAS triggers the start-local-instance via SSH and the remote host reports back to the DAS (default port 4848).

Regards

betox
Offline
Joined: 2013-11-26
Points: 0

Thanks! It's working now. :D