avamingli commented on issue #746:
URL: https://github.com/apache/cloudberry/issues/746#issuecomment-2513953592

   > I actually believe the user does have an ssh key created and in the proper 
location. The error would be different if it didn't exist. I believe the issue 
is that the initial host verification has not taken place. One can use 
ssh-keyscan to help with this. Essentially run the following replacing HOSTNAME 
for all hosts in the cluster. This should fix your issue:
   > 
   > `ssh-keyscan HOSTNAME >> ~/.ssh/known_hosts`
   > 
   > TL;DR ssh-keyscan is a utility that helps gather the public SSH host keys 
of a number of hosts. How does it helps with the initial SSH connection to a 
system? By building .ssh/known_hosts: ssh-keyscan collects the public keys of 
remote hosts and adds them to the .ssh/known_hosts file. This file is used by 
SSH to verify the identity of the remote host, preventing man-in-the-middle 
attacks.
   
   +1, Hi, @paymanfu  have you done these steps as the official doc? 
   we have all steps including ssh in 
https://github.com/apache/cloudberry/blob/main/deploy/build/README.Linux.md
   
   >useradd gpadmin  # Creates gpadmin user
   su - gpadmin  # Uses the gpadmin user
   ssh-keygen  # Creates SSH key
   cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
   chmod 600 ~/.ssh/authorized_keys
   exit
   
   >  so that you can run ssh localhost without a password.
   
   In GPDB, the xxxxOS.README files are  listed under the src root dir, but 
CBDB moved those into deep dir `deploy/build/`.
   I don't know the reason, perhaps we should move them back to make it easy 
for new comers find them.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to