On Wed, 31 Jul 2013 04:51:48 PM Xiao Peng Wang wrote:

> You last sentence meant the ssh keys were not set up on MIC node? The
> genimage command for MIC image does it.

They are in the overlay, but I am not able to login:

[root@barcoo-m ~]# ssh barcoo061-mic0
root@barcoo061-mic0's password: 

[root@barcoo-m ~]# find /install/mpss3-2.1.6720-15/ -name authorized_keys       
                                                                                
                                                                             
/install/mpss3-2.1.6720-15/opt/intel/mic/filesystem/overlay/system/root/.ssh/authorized_keys
 

The authorized_keys are identical to the MN (and they work to localhost):

[root@barcoo-m ~]# md5sum ~/.ssh/authorized_keys 
/install/mpss3-2.1.6720-15/opt/intel/mic/filesystem/overlay/system/root/.ssh/authorized_keys
                                                                                
                
10b75abebb122b6bbe557f0353c1b261  /root/.ssh/authorized_keys                    
                                                                                
                                                                             
10b75abebb122b6bbe557f0353c1b261  
/install/mpss3-2.1.6720-15/opt/intel/mic/filesystem/overlay/system/root/.ssh/authorized_keys
 

and they seem to be correctly processed on the node:

[root@barcoo061 ~]# find /opt/intel/ -name authorized_keys | xargs md5sum
10b75abebb122b6bbe557f0353c1b261  
/opt/intel/mic/mnt/opt/intel/mic/filesystem/overlay/system/root/.ssh/authorized_keys
10b75abebb122b6bbe557f0353c1b261  
/opt/intel/mic/filesystem/mic1/root/.ssh/authorized_keys
10b75abebb122b6bbe557f0353c1b261  
/opt/intel/mic/filesystem/mic0/root/.ssh/authorized_keys


I've noticed that our authorized_keys file had a leading blank line for
some reason, so perhaps that was confusing the SSH implementation
on the MIC?   I've removed that and will rebuild the image and try again.

cheers,
Chris
-- 
   Christopher Samuel - Senior Systems Administrator
 VLSCI - Victorian Life Sciences Computation Initiative
 Email: [email protected] Phone: +61 (0)3 903 55545
         http://www.vlsci.unimelb.edu.au/


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to