Installing ssh addon - caused big problems

For the Pro 2 do

ssh-keygen -R ip.address.of.nas

Then try SSHing in again

Have you tried rebooting the Ultra 2?

Many thanks -
Yes - I had tried rebooting.

For the Pro 2 do Code: Select all ssh-keygen -R ip.address.of.nas

That worked for the Pro - great!

For the Ultra ... it didn't work (I know you didn't suggest it)

David

Download your Logs (Status > Logs > Download all logs)

What's the output of disk_usage.log?

Any clues in the bottom of the output in auth.log?

disk_usage.log:

Filesystem Size Used Avail Use% Mounted on /dev/md0 4.0G 928M 2.9G 24% / tmpfs 16K 0 16K 0% /USB /dev/c/c 455G 116G 339G 26% /c /dev/sdd1 466G 445G 22G 96% /USB/FreeAgent_500

Is there a way to upload the auth.log?

this was the last few entries:

Jan 14 11:13:31 NAS1 pwauth: (pam_unix) authentication failure; logname= uid=98 euid=0 tty= ruser= rhost= user=david Jan 14 11:13:44 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/ethtool eth0 Jan 14 11:13:45 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdconfig -t Jan 14 11:13:45 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/ethtool eth0 Jan 14 11:14:09 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/ethtool eth0 Jan 14 11:14:10 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdconfig -t Jan 14 11:14:10 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -HAil error /dev/sdb Jan 14 11:14:12 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -HAil error /dev/sda Jan 14 11:14:14 NAS1 sudo: admin : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/frontview/bin/empty_spool

Try re-installing the EnableRootSSH add-on if you haven't already.

Hi mgdm

Have successfully re-installed EnableRootSSH to the Ultra.

ssh now works on both - thank you. I'll find out tomorrow if it survives automatic shutdown / restart.

May I ask, to learn, why you suggested key generation for the pro - isn't that automatic with installing EnableRootSSH?

And what you think corrupted the ssh access to the Ultra? Didn't the log entries point to a corrupt file? (Which I would have thought would be on the nas - not on the PC?

I'd really appreciate knowing your thinking / helping me learn.

Many thanks,

David

davidr wrote:
May I ask, to learn, why you suggested key generation for the pro - isn't that automatic with installing EnableRootSSH?

You must have had another device at some point using the same I.P. as the Pro 2 which you connected to via SSH. As the key for the Pro 2 was different to that device your computer suspected that there might be someone doing some hacking and gave this message as a precaution. Since the Pro 2 is on your LAN and you put it there you could remove the key for the old device that used the Pro 2's I.P. from your list of known_hosts. Then there would no longer be any conflict.

davidr wrote:
And what you think corrupted the ssh access to the Ultra? Didn't the log entries point to a corrupt file? (Which I would have thought would be on the nas - not on the PC?

Not sure what caused the problem there.

Thanks.
I had a printer on that router port and IP address until I got the Pro last week.

Hence sh-keygen -R ip.address.of.nas generated the correct key for the Pro and updated the file?

David

The -R removed the key from the list of known hosts on your Mac. Then when you connected to the Pro 2 via SSH, you accepted a new key from the Pro 2.