[Babase] Re: Fwd: Cron <root@papio> /usr/local/sbin/rsync_backup --single-link backup-server1 /etc/rsync.d/rsync_backup_password --exclude-here /var/lib/slocate/slocate.db / /boot --exclude-here '/disk/scratch/*' --exclude-here '/disk/swap_areas/*' /disk

Karl O. Pinc kop at meme.com
Wed Nov 11 10:35:54 EST 2009


On 11/11/2009 09:08:08 AM, Lacey Maryott Roerish wrote:
> I can't tell if this is an error or not, but it says rsync failed.. 
> is
> this
> still the clock error?

No.  (We haven't seen the clock error cause problems yet.)

Papio lost contact with dumbo at about 4:48 eastern time this morning.
So we didn't get the latest backup.

Most likely something's happened to Susan's Internet connection
but there are all sorts of other things that may have gone wrong.
If it's not the Internet then dumbo should be rebooted and I'll
take a look at the logs to see what happened.  Unless it's something
obvious like dumbo getting unplugged, but that's unlikely at 4:48AM.
A momentary power outage could cause problems too.  If that's
it then it would be good to put dumbo on a teeny weeny UPS.  Something
with enough smarts that the power does not drop voltage or turn off and
on again really quickly.

If it turns out to be the Internet, and we think it's a problem,
I'm working on some software that controls a power switch in order
to power cycle a dsl modem to reset it after the ISP does stuff
that makes the dsl modem hang.  (The usual solution when the
Internet goes out on a dsl or cable modem is to unplug and re-plug
in the modem.)

We probably won't discover the problem until somebody physically 
visits Susan's.

If dumbo loses power unexpectedly it takes it about an hour
after reboot to finish checking the disks and fully come
back up.

> 
> ---------- Forwarded message ----------
> From: Cron Daemon <root at papio.biology.duke.edu>
> Date: Wed, Nov 11, 2009 at 5:36 AM
> Subject: Cron <root at papio> /usr/local/sbin/rsync_backup --single-link
> backup-server1 /etc/rsync.d/rsync_backup_password --exclude-here
> /var/lib/slocate/slocate.db / /boot --exclude-here '/disk/scratch/*'
> --exclude-here '/disk/swap_areas/*' /disk
> To: papiobackupadmin at papio.biology.duke.edu
> 
> 
> ssh: connect to host backup-server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far)
> [sender]
> rsync error: error in rsync protocol data stream (code 12) at
> io.c(359)
> rsync_backup[25013]: 12: /: rsync to backup-server1 failed
> ssh: connect to host backup-server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far)
> [sender]
> rsync error: error in rsync protocol data stream (code 12) at
> io.c(359)
> rsync_backup[25013]: 12: /boot: rsync to backup-server1 failed
> ssh: connect to host backup-server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far)
> [sender]
> rsync error: error in rsync protocol data stream (code 12) at
> io.c(359)
> rsync_backup[25013]: 12: /disk: rsync to backup-server1 failed
> 
> 
> 
> -- 
> - -
> Lacey K. Maryott Roerish
> Alberts Lab
> Department of Biology
> Duke University
> ph: 919-660-7306
> fax: 919-660-7293
> Lacey.Maryott at duke.edu
> 




Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein




More information about the Babase mailing list