The new SCC Linux is on Github

Is the build procedure is same as explained in "HowtoBuildSCCLinux1.4.1.x.pdf"?

I have managed to build linux. After using this image to boot SCC when i try to ssh to core it askes for password. is there anything i am missing?

Hello Nil,

You could try and delete your ./shh/known_hosts file.

I tested on marc022 and was able to ssh root@rck00

You may also want to check your /etc/ssh/ssh_config file

What system are you using?

-augie

Sorry,  i should have said that i was using marc042. which has sccKit1.4.2.

Hello Nil,

I have been having problems with marc042.  I am not able to SIF train.  I have tried repeatedly.

I am going to replace the chip and see if it helps.  I am not sure if this is related to your ssh problem.

-augie

can you please let me know once chip has been replaced?

Thank you.

Very interesting SCC stopped SIF training.

Replaced both the RockyCreek chip and the Rockylake board.

marc042 is back online.

I can ssh from core to core.

-augie

when i tried ssh from default linux image it works (with warning) but when i use linux that i built it does not work and i get permission denied.

can it be because i used another machine(my laptop) to build the linux image? or something else?

ssh in default linux image working

nil@marc042:~$ ssh root@rck00
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!        @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for rck00 has changed,
and the key for the corresponding IP address 192.168.62.1
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!   @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
cd:0a:f3:6c:40:1d:91:47:dc:e0:e7:a3:6f:e4:c2:f2.
Please contact your system administrator.
Add correct host key in /home/nil/.ssh/known_hosts to get rid of this message.
Offending key in /home/nil/.ssh/known_hosts:1
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
rck00:/root #

ssh in my linux image not working

nil@marc042:~$ ssh root@rck00
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for rck00 has changed,
and the key for the corresponding IP address 192.168.62.1
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!   @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
cd:0a:f3:6c:40:1d:91:47:dc:e0:e7:a3:6f:e4:c2:f2.
Please contact your system administrator.
Add correct host key in /home/nil/.ssh/known_hosts to get rid of this message.
Offending key in /home/nil/.ssh/known_hosts:1
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
Permission denied (publickey,password,keyboard-interactive).
nil@marc042:~$

Hi Nil,

the ssh error can be solved with:

nil@marc042:rm~/.ssh/known_hosts

It seemed you had one core booted, I was able to ssh into rck00.

Using a different computer should not be a problem, since once you have logged into marc042, it will pull the keys from your home/.ssh directory.

Using a diffreent image has probably prompted the 'man in the middle' error.

Lastly, I have noticed some memory errors on the RockyLake board.  I will replace the memory and will post when it is back online.

-augie

marc042 is back online.  Had to replace the Chip.  MC2 0,2 (DIMM -- MCC3 Slot 0) was being reported as bad.  Memory and Slot are fine.  Replacing chip fixed the problem.

I tested a few custom linux images.  I was able to boot and ssh from core to core.

You can build your images on the MCPC, but you should also be able to build them on a different computer, and they should work.

-augie

thank you fixing memory problem.

as you suggested I removed known_hosts files but still it does not work as it asks for root password.

any suggestion?

Hi Nil,

The ssh problem is very interesting.  I build a new linux on marc042 yesterday and it worked fine.

I would like to test the same image you are using.

I opened a bug report:

http://marcbug.scc-dc.com/bugzilla3/show_bug.cgi?id=397

Let's follow this up on bugzilla until solved, then we can post a recap here.

-augie

Nil,

I too cannot build the new SCC linux on a 'buildPC' without having the cores prompt me for a for password when I try to ssh into a core.

Tested on marc006 and marc042.  The buildPC is a generic ubuntu box.  Copied the image from the buildPC to MCPCs.

If the new image is built on one of our MCPCs the image works fine.

I must not have something confiugred right on the 'buildPC'

Ref:

http://marcbug.scc-dc.com/bugzilla3/show_bug.cgi?id=397