I will give it a try now and get back to you with more feedback. On Wed, Jan 4, 2012 at 2:22 AM, David Dundas <[email protected]> wrote:
> Also just added whir as the cluster-user, and it looks like I'm still > getting the same errors. > > > On Tue, Jan 3, 2012 at 7:21 PM, David Dundas <[email protected]> wrote: > >> Oh I understand now. I definitely misread your post. Ok then what is the >> difference between >> whirr.cluster-user and whirr.login-user? >> >> Do I need to create ssh key for the cluster user as well? >> >> Should I run the command as the cluster user or the command user? >> >> Can the login-user and cluster-user be the same? >> >> Thanks! >> >> On Tue, Jan 3, 2012 at 7:04 PM, Andrei Savu <[email protected]>wrote: >> >>> >>> On Wed, Jan 4, 2012 at 1:57 AM, David Dundas <[email protected]>wrote: >>> >>>> * have you added something like whirr.cluster-user=whirr to >>>> hadoop.properties? >>>> >>> No I havent - should I be? >>>> >>> >>> Yes!! Whirr is trying to create the ec2-user on the remote machine and >>> it fails because that user already exists. >>> >>> I have created the following two related JIRA issues: >>> * https://issues.apache.org/jira/browse/WHIRR-463 >>> * https://issues.apache.org/jira/browse/WHIRR-464 >>> >>> As I said already in a comment my advice is to add: >>> >>> whirr.cluster-user=whirr (to hadoop.properties) >>> >>> and you should be able to login using something like: >>> >>> ssh -i ~/.ssh/id_rsa_whirr whirr@remote-host-ip >>> >>> -- Andrei >>> >>> >> >> >>
