topic Can you tell us what, if in Software Archive

mic0 connection problem

YangHun_P_ — Fri, 31 Oct 2014 06:58:05 GMT

I would used mic0 through ssh, but suddenly doesnt it work.

[----@localhost ~]$ micctrl -s
mic0: online (mode: linux image: /usr/share/mpss/boot/bzImage-knightscorner)
[----@localhost ~]$ ssh mic0
ssh: connect to host mic0 port 22: Connection timed out

So, I restared mic0 using mpss command ( service mpss restart )

but same error happen. This error happend in the old day, at that time, I just resetting mic0 configuration.

It would be okay if resetting mic0, but I dont wanna do it becaused of many configurations.

I will really appriciate to anyone who help me.

Can you tell us what, if

Frances_R_Intel — Fri, 31 Oct 2014 17:27:30 GMT

Can you tell us what, if anything, changed between the time it was working and the time it stopped working? Did you install a new MPSS? Change the network configuration? Add or delete users? Rebuild the passwd file?

I don't know everything I've

YangHun_P_ — Sat, 01 Nov 2014 03:34:00 GMT

thanks for answer.

I don't know everything I've done, but I just used the machine for running benchmark program with cross-compiled binary from host.

I didn`t do anything you mentioned.

I thought it happen at the time after rebooting the xeon phi.

A few things to look at:

Frances_R_Intel — Wed, 05 Nov 2014 01:24:54 GMT

A few things to look at:

First run 'miccheck' and make sure all the tests pass.

Next run 'ping -c 5 mic0' and make sure there is no packet loss.

Then, if you are using the default RamFS setup for booting the coprocessor, check /var/mpss/mic0/home/USER_NAME/.ssh where USER_NAME is the name of the user performing the ssh (or check /var/mpss/mic0/root/.ssh if you are running as root). Make sure that:

the contents of this directory include at least id_rsa and id_rsa.pub (or id_dsa and id_dsa.pub),
the .ssh directory and id_rsa (or id_dsa) file have rwx access for the owner but no access for group or other,
the id_rsa.pub (or id_dsa.pub) file have rwx access for the owner and r access for group and other,
the contents of the files match the contents of the corresponding files in the .ssh directory in the user's home directory on the host machine.

My suspicion is that the ssh keys either don't exist, don't match or are invalid. If you are using the StaticRamFS, NFS or SplitNFS options to boot or if you are NFS mounting the user directories, you will need to check the cpio file or the location you are NFS mounting from rather than in /var/mpss/mic0.