[BackupPC-users] protocol version mismatch -- is your shell clean?quot
Does anyone here know how to correct this? yes, simply not do it. What on earth are you trying to do? You have no apparent problem, except that you don't speak the rsync protocol (which is not really a problem - you don't have to). lol. But there is too an issue. This is the command backuppc is trying to tun to do the backup. /usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator [DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times . /cygdrive/g/ptree/ My ubuntu server won't run the command while a CentOS server backing up the same device will. The error log shows only this: aborted by signal=PIPE Sorry for not being more clear. +-- |This was sent by spamcatc...@safe-mail.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] protocol version mismatch -- is your shell clean?quot
On Fri, Oct 24, 2014 at 12:35 PM, HAL9000 backuppc-fo...@backupcentral.com wrote: Does anyone here know how to correct this? yes, simply not do it. What on earth are you trying to do? You have no apparent problem, except that you don't speak the rsync protocol (which is not really a problem - you don't have to). lol. But there is too an issue. This is the command backuppc is trying to tun to do the backup. If your backuppc xfer logs say something about protocol version mismatch, it is almost always because something else ran first at the remote end and sent some output. The normal rsync binary can deal with that, but the perl implementation in backuppc can't. However if you only saw that error when you started rsync at one end only with your own ssh command it is probably what you should expect. /usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator [DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times . /cygdrive/g/ptree/ I don't understand why you are passing the --rsh comand option to the remote while you are already remotely running it. My ubuntu server won't run the command while a CentOS server backing up the same device will. That sounds more like an error in ssh key setup. -- Les Mikesell lesmikes...@gmail.com -- ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] protocol version mismatch -- is your shell clean?quot
Okay so here is the full error log. full backup started for directory /cygdrive/g/ptree (baseline backup #46) Running: /usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator [DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times . /cygdrive/g/ptree/ Xfer PIDs are now 29452 Got remote protocol 30 Negotiated protocol version 28 Checksum caching enabled (checksumSeed = 32761) Remote[1]: rsync: change_dir /cygdrive/g/ptree failed: No such file or directory (2) Xfer PIDs are now 29452,29462 Read EOF: Tried again: got 0 bytes Can't write 4 bytes to socket Child is aborting Done: 0 files, 0 bytes Got fatal error during xfer (aborted by signal=PIPE) Backup aborted by user signal Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0) As far as the command goes I'm not sure why the -rsh is there. That's just what backuppc is doing on the localhost and was set that way prior to me even getting here and working on this server. It had been working for a long time that way. Even so I removed that option and still got the same error as the one above. The logs say nothing about a protocol version mismatch. It's also not a key issue problem as I'm able to log right in as root from the backuppc user without any problems. --- On Fri, Oct 24, 2014 at 12:35 PM, HAL9000 backuppc-forum at backupcentral.com wrote: Does anyone here know how to correct this? yes, simply not do it. What on earth are you trying to do? You have no apparent problem, except that you don't speak the rsync protocol (which is not really a problem - you don't have to). lol. But there is too an issue. This is the command backuppc is trying to tun to do the backup. If your backuppc xfer logs say something about protocol version mismatch, it is almost always because something else ran first at the remote end and sent some output. The normal rsync binary can deal with that, but the perl implementation in backuppc can't. However if you only saw that error when you started rsync at one end only with your own ssh command it is probably what you should expect. /usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator [DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times . /cygdrive/g/ptree/ I don't understand why you are passing the --rsh comand option to the remote while you are already remotely running it. My ubuntu server won't run the command while a CentOS server backing up the same device will. That sounds more like an error in ssh key setup. +-- |This was sent by spamcatc...@safe-mail.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] protocol version mismatch -- is your shell clean?quot
On Fri, Oct 24, 2014 at 4:02 PM, HAL9000 backuppc-fo...@backupcentral.com wrote: Okay so here is the full error log. Remote[1]: rsync: change_dir /cygdrive/g/ptree failed: No such file or directory (2) That doesn't look very promising. Does the path really exist, and does the other host succeed in backing it up as you said before? It's also not a key issue problem as I'm able to log right in as root from the backuppc user without any problems. Agreed - the log shows you clearly are getting as far as starting rsync on the other end. -- Les Mikesell lesmikes...@gmail.com -- ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] protocol version mismatch -- is your shell clean?
Hi, HAL9000 wrote on 2014-10-08 08:48:56 -0700 [[BackupPC-users] protocol version mismatch -- is your shell clean?]: [...] Does anyone here know how to correct this? yes, simply not do it. What on earth are you trying to do? You have no apparent problem, except that you don't speak the rsync protocol (which is not really a problem - you don't have to). |This was sent by spamcatc...@safe-mail.net via Backup Central. No comment. Regards, Holger -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] protocol version mismatch -- is your shell clean?
Here is the command backuppc is running and when is returned if I run it in the
shell as the backuppc user.
/usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator
[DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group
-D --links --hard-links --times --block-size=2048 --recursive
--checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times .
/cygdrive/g/ptree/
The character returned is apparently a question mark according to starpage.com
and even though it is included in the about output, is not showng up here. This
is occurring on Ubuntu 14.04 server and everything is uptodate. Cygwin on the
remote machine is also up to date. We also have a CentOS 6.5 machine running
the exact same command without any problems whatsoever.
Just now after pressing enter a few time I managed to get another error message
to come out after the strange question mark glyph:
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at
/home/lapo/package/rsync-3.0.9-1/src/rsync-3.0.9/compat.c(174) [sender=3.0.9]
I've gone ahead and tried to check and see if my shell is clean myself and it
appears to be so. The following command returns nothing in the text file.
rsh remotehost /bin/true out.dat
Neither does this one:
ssh Administrator@r{DOMAIN] -p222 false
And rsync is indeed on the other end.
ssh Administrator@[DOMAIN] -p222 rsync --version
rsync version 3.0.9 protocol version 30
Copyright (C) 1996-2011 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
no socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes
rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. See the GNU
General Public Licence for details.
Does anyone here know how to correct this?
+--
|This was sent by spamcatc...@safe-mail.net via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
