Mixing Windows and Unix server instances is not supported. You may be able to
get it to work, but having a DAS running on Windows and instances on Unix
systems is not something we test and I can imagine some issues that might pop
up.
But your current problem seems to be related to just getting SSH key
authentication working.
Recent builds of 3.1 have a new command, setup-ssh, that helps configure your
ssh keys. You may want to try and run that while on the DAS system:
asadmin setup-ssh instance.us.oracle.com
This detects if you have a key generated already, generates a new one if you
don't, copies it to the remote system and verifies the SSH connection using
the key. It will prompt you for your SSH password if it needs to copy the
key to the remote system. It will then report if it could make a connection
using key authentication.
If it fails to authenticate the first thing to check is your filesystem
permissions on the remote (instance) system for the SSH user you are using.
Make sure the user's home directory, .ssh directory, and .ssh/authorized_keys
file are writeable only by the user. If they are writeable by others then
typically sshd will not trust the authorized_keys file and reject key
authentication.
You can run setup-ssh as many times as you like to test the connection.
Here is an example of a run when key authentication is already
configured and working:
$ asadmin setup-ssh foo.us.oracle.com
Successfully connected to dipol_at_foo.us.oracle.com using keyfile
/export/home/dipol/.ssh/id_dsa
SSH public key authentication is already configured for
dipol_at_foo.us.oracle.com
Command setup-ssh executed successfully.
FYI, if you can't get key authentication working there is a way to use SSH
password authentication to set up your cluster. There is some info here (it
is Unix oriented though):
http://wikis.sun.com/display/GlassFish/3.1SSHAuthentication
--
[Message sent by forum member 'jfdipol']
View Post: http://forums.java.net/node/709394