hibari/clus — Issue #3: ssh-copy-id fail (?)
Author: dewd
Created: 2012-01-07 20:48:46+00:00
State: open

Probably a user or docs issue...

context:
setting up a three node cluster on Centos 5.7
have "admin" / root accounts configured for password-less SSH to each node from an admin node (admin-vm)
node names are simple (vm1 vm2 vm3).
network connectivity verified between all four nodes

attempting to set up the runtime user ("hibari") with ./clus/priv.clus.sh

running clus.sh from "admin" account on a the admin node, successfully completes the init functions using SSH with the "admin" account:
- killing current procs (verified)
- deleting the old user / group (verified)
- adding new group / user (verified)
- generating the passwd (verified)
- setting the password (verified)
- unlocking the account (verified)

I can verify each of the above steps on the target node.
It then it appears to complete the ssh-copy-id, after which it successfully locks the account (using the "admin" creds)

but fails on the test (where it does SSH $USER_NODE@$HOST_NODE echo $USER_NODE@$HOST_NODE)

I suspect that I have missed a step in the setup relating to configuration of the runtime user ("hibari"), but having re-read the dev guide (setting up a cluster) & the readme, I'm stumped as to what it is (ssh-agent or .ssh/config ?)