Re: SSH error deploying agent in OEM

Check /var/log/messages and /var/log/secure - it should tell you the problem after a failed ssh authentication.

Often its going to be the permissions are too open on either/all:

Check:

$HOME
$HOME/.ssh
$HOME/.ssh/authorized_keys  $HOME/.ssh/id_rsa

$HOME/.ssh = drwx------ (owner= full , none othter)
$HOME/.ssh/authorized_keys = -rw------  (owner read-write only)
$HOME/.ssh/id_rsa  = -rw------ (owner read-write only)

> This one is kind of strange. I have tested ssh from the oem server to the
> particular database server in question logged in as oracle, and it works
> fine.
>
> However, whenever I try to deploy an agent onto the new database server, I
> get this error:
> Connection to the SSH daemon (sshd) on the target host failed with the
> following error : Too many authentication failures Connection to the SSH
> daemon (sshd) on the target host failed with the following error : Too many
> authentication failures Connection to the SSH daemon (sshd) on the target
> host failed with the following error : Too many authentication failures
>
> Connection to the SSH daemon (sshd) on the target host failed with the
> following error : Too many authentication failures
> I have tested the credentials multiple times from oem and verified that
> they are valid. I cant figure out what the issue is. Has anyone run into
> this and have any ideas. My next step is probably to try the agent pull,
> but I would really like to understand what is going on here.
> Connection to the SSH daemon (sshd) on the target host failed with the
> following error : Too many authentication failures
>
> Connection to the SSH daemon (sshd) on the target host failed with the
> following error : Too many authentication failures
>
> --
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
>

--
http://www.freelists.org/webpage/oracle-l