home | list info | list archive | date index | thread index

Re: [OCLUG-Tech] Rsnapshot Issues

On April 3, 2016 12:00:01 PM linux-request [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca wrote:
> Send Linux mailing list submissions to
> 	linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://oclug.on.ca/mailman/listinfo/linux
> or, via email, send a message with subject or body 'help' to
> 	linux-request [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca
> 
> You can reach the person managing the list at
> 	linux-owner [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linux digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Rsnapshot Issues (Nicholas Savage)
>    2. Re: Warning: think before you boost your car battery
>       (Jason Butler)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 2 Apr 2016 22:16:09 -0400
> From: Nicholas Savage <nicholas [ dot ] b [ dot ] savage [ at ] gmail [ dot ] com>
> To: linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca
> Subject: Re: [OCLUG-Tech] Rsnapshot Issues
> Message-ID:
> 	<CA+wbT7Wu9kLS3rOBSVO7bpw9RgRdqGbE3LMTZHqs062+_kqgdw [ at ] mail [ dot ] gmail [ dot ] com>
> Content-Type: text/plain; charset=UTF-8
> 
> On Mon, Mar 7, 2016 at 7:31 PM, Bruce wrote:
> > On March 6, 2016 08:19:35 PM Alex Pilon wrote:
> >> On Sun, Mar 06, 2016 at 05:24:53PM -0500, Bruce wrote:
> >> > I'm having trouble with the ssh login.
> >> > 
> >> > debug3: hostkeys_foreach: reading file "/root/.ssh/known_hosts"
> >> 
> >> Don't expect `ssh -vvv` to tell you everything. For security reasons,
> >> the SSH daemon *won't* tell you many of the issues you may have.
> >> 
> >> Have you checked the SSH daemon logs? You have a good chance of finding
> >> your answer there. `ssh -vvv` is usually more for SSH *protocol*
> >> debugging.
> >> 
> >> Regards,
> >> 
> >> Alex Pilon
> > 
> > Thanks for the suggestion.  I found the problem and I'm now able to login
> > into either computer with ssh.
> > 
> > I now have a new error when running Rsnapshot.
> > 
> > # rsnapshot -VD alpha
> > require Lchown
> > Lchown module loaded successfully
> > Setting locale to POSIX "C"
> > echo 3395 > /var/run/rsnapshot.pid
> > /bin/rm -rf /backups/rsync-bbox/.snapshots/alpha.5/
> > mv /backups/rsync-bbox/.snapshots/alpha.4/ \
> > 
> >     /backups/rsync-bbox/.snapshots/alpha.5/
> > 
> > mv /backups/rsync-bbox/.snapshots/alpha.3/ \
> > 
> >     /backups/rsync-bbox/.snapshots/alpha.4/
> > 
> > mv /backups/rsync-bbox/.snapshots/alpha.2/ \
> > 
> >     /backups/rsync-bbox/.snapshots/alpha.3/
> > 
> > mv /backups/rsync-bbox/.snapshots/alpha.1/ \
> > 
> >     /backups/rsync-bbox/.snapshots/alpha.2/
> > 
> > /bin/cp -al /backups/rsync-bbox/.snapshots/alpha.0 \
> > 
> >     /backups/rsync-bbox/.snapshots/alpha.1
> > 
> > /usr/bin/rsync -av --delete --numeric-ids --relative --delete-excluded \
> > 
> >     --include=/home/bruce2/ --rsh=/usr/bin/ssh -l root at 192.168.1.129:/
> >     \
> >     /backups/rsync-bbox/.snapshots/alpha.0/root at 192.168.1.147:/
> > 
> > ssh: Could not resolve hostname root: Name or service not known
> > rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
> > rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.2]
> > --------------------------------------------------------------------------
> > -- rsnapshot encountered an error! The program was invoked with these
> > options: /usr/bin/rsnapshot -VD alpha
> > --------------------------------------------------------------------------
> > -- ERROR: /usr/bin/rsync returned 0.99609375 while processing
> > root at 192.168.1.129:/
> > /usr/bin/logger -p user.err -t rsnapshot[3395] /usr/bin/rsnapshot -VD \
> > 
> >     alpha: ERROR: /usr/bin/rsync returned 0.99609375 while processing \
> >     root at 192.168.1.129:/
> > 
> > touch /backups/rsync-bbox/.snapshots/alpha.0/
> > rm -f /var/run/rsnapshot.pid
> > /usr/bin/logger -p user.err -t rsnapshot[3395] /usr/bin/rsnapshot -VD \
> > 
> >     alpha: ERROR: /usr/bin/rsnapshot -VD alpha: completed, but with some \
> >     errors
> > 
> > What I don't understand is why ssh work on it's own, but will not work
> > within rsnapshot.  Any ideas?
> > 
> > 
> > ====
> > Bruce
> 
> I hope this doesn't reach you too late. Could you post your rsnapshot
> config? The one thing that really sticks out is the error message says
> "root at 192.168.1.129". I feel like it should say
> "root@192.168.1.129" normally. Are you sure that you have it written
> properly in your config file?
> 
> Regards,
> Nick Savage
> 

Nick,

Not too late.  Still stuck at this stage.  Below is my config.

====================================

#################################################
# rsnapshot.conf - rsnapshot configuration file #
#################################################
#                                               #
# PLEASE BE AWARE OF THE FOLLOWING RULE:        #
#                                               #
# This file requires tabs between elements      #
#                                               #
#################################################

#######################
# CONFIG FILE VERSION #
#######################

config_version	1.2

###########################
# SNAPSHOT ROOT DIRECTORY #
###########################

# All snapshots will be stored under this root directory.
#
snapshot_root	/backups/rsync-bbox/.snapshots/

# If no_create_root is enabled, rsnapshot will not automatically create the
# snapshot_root directory. This is particularly useful if you are backing
# up to removable media, such as a FireWire or USB drive.
#
#no_create_root	1

#################################
# EXTERNAL PROGRAM DEPENDENCIES #
#################################

# LINUX USERS:   Be sure to uncomment "cmd_cp". This gives you extra features.
# EVERYONE ELSE: Leave "cmd_cp" commented out for compatibility.
#
# See the README file or the man page for more details.
#
cmd_cp		/bin/cp

# uncomment this to use the rm program instead of the built-in perl routine.
#
cmd_rm		/bin/rm

# rsync must be enabled for anything to work. This is the only command that
# must be enabled.
#
cmd_rsync	/usr/bin/rsync

# Uncomment this to enable remote ssh backups over rsync.
#
cmd_ssh	/usr/bin/ssh

# Comment this out to disable syslog support.
#
cmd_logger	/usr/bin/logger

# Uncomment this to specify the path to "du" for disk usage checks.
# If you have an older version of "du", you may also want to check the
# "du_args" parameter below.
#
cmd_du		/usr/bin/du

# Uncomment this to specify the path to rsnapshot-diff.
#
#cmd_rsnapshot_diff	/usr/local/bin/rsnapshot-diff

# Specify the path to a script (and any optional arguments) to run right
# before rsnapshot syncs files
#
#cmd_preexec	/path/to/preexec/script

# Specify the path to a script (and any optional arguments) to run right
# after rsnapshot syncs files
#
#cmd_postexec	/path/to/postexec/script

# Paths to lvcreate, lvremove, mount and umount commands, for use with
# Linux LVMs.
#
#linux_lvm_cmd_lvcreate	/path/to/lvcreate
#linux_lvm_cmd_lvremove	/path/to/lvremove
#linux_lvm_cmd_mount	/bin/mount
#linux_lvm_cmd_umount	/bin/umount

#########################################
#     BACKUP LEVELS / INTERVALS         #
# Must be unique and in ascending order #
# e.g. alpha, beta, gamma, etc.         #
#########################################

retain	alpha	6
retain	beta	7
retain	gamma	4
#retain	delta	3

############################################
#              GLOBAL OPTIONS              #
# All are optional, with sensible defaults #
############################################

# Verbose level, 1 through 5.
# 1     Quiet           Print fatal errors only
# 2     Default         Print errors and warnings only
# 3     Verbose         Show equivalent shell commands being executed
# 4     Extra Verbose   Show extra verbose information
# 5	Debug mode      Everything

verbose		5

# Same as "verbose" above, but controls the amount of data sent to the
# logfile, if one is being used. The default is 3.
#
loglevel	3

# If you enable this, data will be written to the file you specify. The
# amount of data written is controlled by the "loglevel" parameter.
#
logfile	/var/log/rsnapshot

# If enabled, rsnapshot will write a lockfile to prevent two instances
# from running simultaneously (and messing up the snapshot_root).
# If you enable this, make sure the lockfile directory is not world
# writable. Otherwise anyone can prevent the program from running.
#
lockfile	/var/run/rsnapshot.pid

# Default rsync args. All rsync commands have at least these options set.
#
#rsync_short_args	-a
#rsync_long_args	--delete --numeric-ids --relative --delete-excluded

# ssh has no args passed by default, but you can specify some here.
#
ssh_args	-l	/root/.ssh/rsync-key	-p	8569

# Default arguments for the "du" program (for disk space reporting).
# The GNU version of "du" is preferred. See the man page for more details.
# If your version of "du" doesn't support the -h flag, try -k flag instead.
#
#du_args	-csh

# If this is enabled, rsync won't span filesystem partitions within a
# backup point. This essentially passes the -x option to rsync.
# The default is 0 (off).
#
#one_fs		0

# The include and exclude parameters, if enabled, simply get passed directly
# to rsync. If you have multiple include/exclude patterns, put each one on a
# separate line. Please look up the --include and --exclude options in the
# rsync man page for more details on how to specify file name patterns. 
# 
bruceinclude	/home/2/
#include	???
#exclude	???
#exclude	???

# The include_file and exclude_file parameters, if enabled, simply get
# passed directly to rsync. Please look up the --include-from and
# --exclude-from options in the rsync man page for more details.
#
#include_file	/path/to/include/file
bruce#exclude_file	/home/2/exclude.txt

# If your version of rsync supports --link-dest, consider enabling this.
# This is the best way to support special files (FIFOs, etc) cross-platform.
# The default is 0 (off).
#
#link_dest	0

# When sync_first is enabled, it changes the default behaviour of rsnapshot.
# Normally, when rsnapshot is called with its lowest interval
# (i.e.: "rsnapshot alpha"), it will sync files AND rotate the lowest
# intervals. With sync_first enabled, "rsnapshot sync" handles the file sync,
# and all interval calls simply rotate files. See the man page for more
# details. The default is 0 (off).
#
#sync_first	0

# If enabled, rsnapshot will move the oldest directory for each interval
# to [interval_name].delete, then it will remove the lockfile and delete
# that directory just before it exits. The default is 0 (off).
#
#use_lazy_deletes	0

# Number of rsync re-tries. If you experience any network problems or
# network card issues that tend to cause ssh to fail with errors like
# "Corrupted MAC on input", for example, set this to a non-zero value
# to have the rsync operation re-tried.
#
#rsync_numtries 0

# LVM parameters. Used to backup with creating lvm snapshot before backup
# and removing it after. This should ensure consistency of data in some 
special
# cases
#
# LVM snapshot(s) size (lvcreate --size option).
#
#linux_lvm_snapshotsize	100M

# Name to be used when creating the LVM logical volume snapshot(s).
#
#linux_lvm_snapshotname	rsnapshot

# Path to the LVM Volume Groups.
#
#linux_lvm_vgpath	/dev

# Mount point to use to temporarily mount the snapshot(s).
#
#linux_lvm_mountpath	/path/to/mount/lvm/snapshot/during/backup

###############################
### BACKUP POINTS / SCRIPTS ###
###############################

# LOCALHOST
#backup	/home/		localhost/
#backup	/etc/		localhost/
#backup	/usr/local/	localhost/
#backup	/var/log/rsnapshot		localhost/
#backup	/etc/passwd	localhost/
#backup	/home/foo/My Documents/		localhost/
#backup	/foo/bar/	localhost/	one_fs=1, rsync_short_args=-urltvpog
#backup_script	/usr/local/bin/backup_pgsql.sh	localhost/postgres/
# You must set linux_lvm_* parameters below before using lvm snapshots
#backup	lvm://vg0/xen-home/	lvm-vg0/xen-home/

# EXAMPLE.COM
#backup_exec	/bin/date "+ backup of example.com started at %c"
#backup	root [ at ] example [ dot ] com:/home/	example.com/	+rsync_long_args=--
bwlimit=16,exclude=core
#backup	root [ at ] example [ dot ] com:/etc/	example.com/	exclude=mtab,exclude=core
#backup_exec	ssh root [ at ] example [ dot ] com "mysqldump -A > /var/db/dump/mysql.sql"
#backup	root [ at ] example [ dot ] com:/var/db/dump/	example.com/
#backup_exec	/bin/date "+ backup of example.com ended at %c"

# CVS.SOURCEFORGE.NET
#backup_script	/usr/local/bin/backup_rsnapshot_cvsroot.sh	
rsnapshot.cvs.sourceforge.net/

# RSYNC.SAMBA.ORG
#backup	rsync://rsync.samba.org/rsyncftp/	rsync.samba.org/rsyncftp/

# Rsync BBOX
backup	root@192.168.1.129:/	root [ at ] faintfuzzies [ dot ] ca:/


-- 
bruce

replies