Skip to main content

SSh Error during vertica 7 upgrade

  • September 3, 2014
  • 2 replies
  • 13 views

Sunny_1
Forum|alt.badge.img
Upgrade fails with Failed to Import SSH keys. 
Failed on hosts: 10.10.18.50, 10.10.18.48, 10.10.18.49Error: SSH key generation or distribution failed.
Installation FAILED with errors.

Password less SSH is confiugrd between all of the hosts for ROOT and the DBADMIN user. We installed the 6.0 without any errors but the 7.0 keep erroing out on SSH.

2 replies

Forum|alt.badge.img+2
  • Participating Frequently
  • September 3, 2014

Hello Sunny,

 

I found a similar error and a solution below.  Please check if it helps.

 

Problem:
Failed to upgrade v7.0.0 - Failed to import SSH key

Solution:


It is related to SSH issue between nodes.

ppal1:/home/dbadmin $ pwd
/home/dbadmin/.ssh
ppal1:/home/dbadmin $ls -lrt
-rw-r--r-- 1 dbadmin dbadmin 392 Oct 10 17:32 authorized_keys
-rw-r--r-- 1 dbadmin dbadmin 5489 Nov 21 15:54 known_hosts

Check the file authorized_key file had a permission of 400, that prevented the installer from overwriting this file. Once changed it to 600, the upgrade should work for this issue.

Regards,

Han

 

 

 


Nimmi_gupta
Forum|alt.badge.img
  • Participating Frequently
  • October 10, 2014
If this still an issue, you can try following instructions :

Before installing vertica make sure Server must have password-less and prompt-less login with “ssh 127.0.0.1”.Password-less login. To establish password-less login to a server
1.cd $HOME/.ssh

2. Generate ssh key on the server
ssh-keygen -t rsa

3. Add the generated ssh key to server's authorized keys file.
cat .ssh/id_rsa.pub >> .ssh/authorized_keys

4. For multiple-machine mode (Section 5), add ssh key of each server to file
$HOME/. ssh/authorized_keys of other servers in the cluster.

5. Set permission set of server's authorized keys file
chmod 600 .ssh/authorized_keys
Prompt-less login. When ssh is issued to an unknown hosts, it must automatically be added to the
list of known hosts ( $HOME/.ssh/known_hosts ) of the Server. It must not prompt for any user input
like Are you sure you want to continue connecting (yes/no)?

This can be achieved by one of the following ways:
1. Set StrictHostKeyChecking option in $HOME/.ssh/config file to 'no' instead of'ask' .
2. Make Server remember an unknown hosts by issuing a ssh.
User can provide input to the ssh prompt as required. Hosts will now be added to Server's
known hosts ( $HOME/.ssh/known_hosts ) and ssh will not make any prompt.