On 6/15/12, root on baron <root@xxxxxxxxxxxxxxxxxx> wrote: ######################################################################## > # Rotated Off-Site Backups > ######################################################################## > > *** Starting Backup for etc ... > -rw-r--r-- 1 root root 1.4M Jun 15 06:33 > /var/tmp/2012-06-15.06-33-02.tbz.gpg > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ 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 a host key has just been changed. > The fingerprint for the RSA key sent by the remote host is > cd:82:7f:e5:ce:b3:63:30:ed:b5:47:19:a1:f1:02:a0. > Please contact your system administrator. > Add correct host key in /root/.ssh/known_hosts to get rid of this message. > Offending RSA key in /root/.ssh/known_hosts:13 > You can use following command to remove all keys for this IP: > ssh-keygen -R mmadia.dyndns.org -f /root/.ssh/known_hosts > RSA host key for mmadia.dyndns.org has changed and you have requested strict > checking. > Host key verification failed. > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: unexplained error (code 255) at io.c(601) [sender=3.0.7] Hi there, The system upgrade is still tinkering along. The nighty-images script and Buildbot are back up. IIRC, the ssh related files have been restored, so the host identification errors should go away on the next cycle. However, the storage slice/partition is still offline. This weekend, I'm going to try recreate the RAID1 mirror using ZFS -- which will be a learning experience. Until that's done, the user accounts will be disabled (as I don't want to chance any accidents) and the remote backups to mmadia.dyndns.org will continue to fail. --mmadia