On Mon, Mar 22, 2010 at 3:56 AM, Kenneth L. Owen
<tx836519 AT bellsouth DOT net> wrote:
Hi Luis,
I have reworked the archive server to use visudo and ran a tar backup of
the localhost /home directory. It worked but I got an error
on /home/ken/.gvfs file -- permission denied. I was logged on and I
believe that is what caused the error. Should I exclude this file to
prevent errors in the future? Otherwise, it seemed to work just fine.
Yes, that happens to me too. It's not a fatal error, but I exclude .gvfs dir. I think it has something to do with gnome fuse system (don't really know what it is).
But, when I tried to do a backup on a client machine, I get the
following error:
Contents of file /var/lib/backuppc/pc/<client1>/LOG.032010, modified
2010-03-21 20:41:30 # real machine_name for <client1>
2010-03-21 20:41:23 full backup started for directory /media/<share1>
# real sharename for <share1>
2010-03-21 20:41:25 Got fatal error during xfer (fileListReceive failed)
2010-03-21 20:41:30 Backup aborted (fileListReceive failed)
XferLog for the client reads:
Contents of file /var/lib/backuppc/pc/<client1>/XferLOG.bad, modified
2010-03-21 20:41:30
full backup started for directory /media/<share1>
Running: /usr/bin/ssh -q -x -l backuppc
<client1> /usr/bin/sudo /usr/bin/rsync --server --sender --numeric-ids
--perms --owner --group -D --links --hard-links --times
--block-size=2048 --recursive --ignore-times . /media/<share1>/
I use --times instead of --ignore-time. Everything seems fine.
Xfer PIDs are now 9262
Got remote protocol 1881173838
Fatal error (bad version): No protocol specified
Read EOF:
Tried again: got 0 bytes
fileListReceive() failed
Done: 0 files, 0 bytes
Got fatal error during xfer (fileListReceive failed)
Backup aborted (fileListReceive failed)
------------ end XferLog -------------
Are you trying to backup a CD? Just thinking if it may have something to do with the failure... Could you try a normal dir if so?
On the client machine:
# /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
#
Defaults env_reset
# Uncomment to allow members of group sudo to not need a password
# %sudo ALL=NOPASSWD: ALL
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification
root ALL=(ALL) ALL
# ---------------------backuppc user -----------------------
# To RESTORE, uncomment the Restore cmd and comment the Backup cmd.
# After the RESTORE, switch them back.
# backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender * # Restore
cmd
backuppc ALL=NOPASSWD: /usr/bin/rsync --server * # Backup cmd
# ----------------------------------------------------------
# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
* --------------- end sudoers ------------------------
On the server in backuppc settings for this client:
XferMethod: rsync
RsyncClientCmd: $sshPath -q -x -l backuppc
$host /usr/bin/sudo /usr/bin/rsync $argList+
RsyncClientRestoreCmd: $sshPath -q -x -l backuppc $host /usr/bin/sudo
$rsyncPath $argList+
Do you see anything that I goofed in setting up the client? -- ken
Everything looks just fine, except you switched the restore and backup cmds on visudo. --server --sender * is for backup, use only --server * (less restrictive) to restore. (I see I also made that mistake in my previous message).
That alone will not justify the backup error, so please try another share and get back to us.
I'll focus on the message:
Got remote protocol 1881173838
Fatal error (bad version): No protocol specified
I usually get something like
Got remote protocol 30
Negotiated protocol version 28
But I don't know what it can mean. Maybe someone else can help.
