How to troubleshoot an “Rsync over SSH” connection using public key authentication. (4275671)

How to troubleshoot an “Rsync over SSH” connection using public key authentication.

For details on how to create a backup policy using Rsync over SSH please see the relevant section in the Admin Guide.

https://support.oneidentity.com/technical-documents/one-identity-safeguard-for-privileged-sessions/administration-guide/24#TOPIC-1789650

To troubleshoot the ssh connection with public key authentication

1. Login to the SPS core-shell via ssh.
2. Open /opt/scb/var/db/scb.xml
3. Search for the keyword rsync to find the rsync backup configuration.
4. Copy the private key, including
          -----BEGIN RSA PRIVATE KEY-----
          -----END RSA PRIVATE KEY-----
5. Close the ssb.xml
6. Create a new file eg.: /root/rsync_private_key and paste the private key into that.
7. Change the permissions of the private key: chmod 600 /root/rsync_private_key
8. Run the following command where "user" is the "Username" from the backup policy and "host" is the "Target server" specified in the same policy.

# ssh -vvv user@host -i rsync_private_key 2>&1 | tee /tmp/ssh_debug.log

1. Once testing is complete delete the file /root/rsync_private_key

If the user was prompted to enter a password or if the connection was not made successfully using public key authentication, then examine the debug for messages indicating a problem.

For example, “debug3: receive packet: type 51” means “SSH_MSG_USERAUTH_FAILURE” and possibly indicates that the public key has not been imported to the users authorized_keys file on the remote server.