Well, the message says it clearly :-P Some basic Unix knowledge that might help:
-) Permissions in unix are (r)ead/(w)rite/e(x)ecute for the user (owner)/group/world. -) for historic reasons, permissions are often given as octal numbers as in this case. 0644 means rw for owner, r for group and world. -) ssh does not like the fact that the private key file is readable by anyone but the owner. As I don't use the EC2 scripts, I cannot tell you for sure, BUT somewhere that 'private_key_file_path_and_name' is, and you need to run chmod 600 private_key_file_path_and_name on it. Andreas On Friday 06 June 2008 08:45:48 Xuan Dzung Doan wrote: > Hi, > > I'm new to Hadoop and Linux. I hope my question is basic. > > I just downloaded Hadoop 0.16.4 to my Fedora 8 workstation to use the > scripts to launch EC2 instances of Hadoop 0.16.1 on Amazon. I completed the > configuration step and issued the command to launch the instances: > > % bin/hadoop-ec2 run > > The instances were launched successfully and I was also done with DNS > setting. But when the script tried to log me into the master node, an issue > occured with a message like this: > > -------------------- > WARNING: UNPROTECTED PRIVATE KEY FILE > > Permissions 0644 for 'private_key_file_path_and_name' are too open. > It is recommended that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: private_key_file_path_and_name > -------------------- > > then I was asked for the password to log into the master node as root. Of > course I was not able to go further. > > Any idea how I can resolve this private key issue? > > Thanks, > David.
signature.asc
Description: This is a digitally signed message part.
