Akibu,

It looks like the connection terminates immediately.  We need to figure out
why.

If you run the exact ssh command as the backuppc user, do you get an error
or any output?

su backuppcUser
/usr/bin/ssh -q -x -l root akibu-desktop /usr/bin/rsync --server --sender
-svvvlHogDtprce.iLsf


If you don't see any output, hit ^D and you should get an error like this:

rsync: on remote machine: (null): unknown option
rsync error: syntax or usage error (code 1) at main.c(1634) [server=3.1.1]
[server] _exit_cleanup(code=1, file=main.c, line=1634): about to call
exit(1)

Next, are you sure that the directory /mnt/j/Favorites on akibu-desktop
exists?

Craig


On Sun, Jun 11, 2017 at 3:17 PM, Akibu Flash <akibufl...@outlook.com> wrote:

> Thanks @Craig Barratt <cbarr...@users.sourceforge.net>  The XferLOG
> beginning of the XferLOG is below.  Please advise if you see anything
> therein.  Thanks again.
>
>
>
> (Thestrace is showing the dynamic linking during startup of ssh, which
> isn't particularly relevant.  It's not showing the files being backed up.
>
>
>
> What we are missing is the log output from XferLOG.  That has the more
> detailed information (eg, exact rsync / ssh args).  Can you send that
> please?  You'll find it in the per-PC backup directory, eg:
> /data/BackupPC/pc/clientName/XferLOG.bad.z.  Use BackupPC_zcat to
> uncompress it.
>
> Craig)
>
>
>
> XferLOG file /mnt/backup_disks/backuppc/pc/akibu-desktop/XferLOG.0.z
> created 2017-06-11 18:00:44
> Backup prep: type = full, case = 1, inPlace = 1, doDuplicate = 0,
> newBkupNum = 0, newBkupIdx = 0, lastBkupNum = , lastBkupIdx =  (FillCycle =
> 0, noFillCnt = )
> Running: /usr/local/bin/rsync_bpc --bpc-top-dir /mnt/backup_disks/backuppc
> --bpc-host-name akibu-desktop --bpc-share-name /mnt/j/Favorites
> --bpc-bkup-num 0 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1
> --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 1 --bpc-attrib-new --bpc-log-level
> 9 -e /usr/bin/ssh\ -q\ -x\ -l\ root -vvv --rsync-path=/usr/bin/rsync
> --super --recursive --protect-args --numeric-ids --perms --owner --group -D
> --times --links --hard-links --delete --partial --log-format=log:\ %o\ %i\
> %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --timeout=72000
> akibu-desktop:/mnt/j/Favorites/ /
> full backup started for directory /mnt/j/Favorites
> Xfer PIDs are now 3643
> This is the rsync child about to exec /usr/local/bin/rsync_bpc
> bpc_lib_conf_init: topDir = /mnt/backup_disks/backuppc, logLevel = 9
> bpc_path_create(/mnt/backup_disks/backuppc/pc/akibu-desktop/0)
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
> = 0
> opening connection using: /usr/bin/ssh -q -x -l root akibu-desktop
> /usr/bin/rsync --server --sender -svvvlHogDtprce.iLsf
> protected args: --timeout=72000 --numeric-ids . /mnt/j/Favorites/
> rsync_bpc: connection unexpectedly closed (0 bytes received so far)
> [Receiver]
> bpc_sysCall_cleanup: doneInit = 1
> RefCnt Deltas for new backup
> Uncompressed HT:
> Compressed HT:
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal,
> 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 1 inode
> Parsing done: nFilesTotal = 0
> rsync error: unexplained error (code 255) at io.c(629) [Receiver=3.0.9.6]
> [Receiver] _exit_cleanup(code=12, file=io.c, line=629): about to call
> exit(255)
> rsync_bpc exited with fatal status 255 (65280) (rsync error: unexplained
> error (code 255) at io.c(629) [Receiver=3.0.9.6])
> Xfer PIDs are now
> Got fatal error during xfer (rsync error: unexplained error (code 255) at
> io.c(629) [Receiver=3.0.9.6])
> Backup aborted (rsync error: unexplained error (code 255) at io.c(629)
> [Receiver=3.0.9.6])
> BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 1, inPlace =
> 1, lastBkupNum =
> Removing empty backup #0
> Xfer PIDs are now 3663
> BackupPC_backupDelete: removing #0
> BackupPC_backupDelete: No prior backup for merge
> Xfer PIDs are now 3664,3663
> BackupPC_refCountUpdate: computing totals for host akibu-desktop
> bpc_lib_conf_init: topDir = /mnt/backup_disks/backuppc, logLevel = 9
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
> = 0
> BackupPC_refCountUpdate: host akibu-desktop got 0 errors (took 0 secs)
> BackupPC_refCountUpdate total errors: 0
> Xfer PIDs are now 3663
> BackupPC_backupDelete: got 0 errors
> Xfer PIDs are now
> Finished BackupPC_backupDelete, status = 0 (running time: 0 sec)
> Xfer PIDs are now
> Running BackupPC_refCountUpdate -h akibu-desktop -f on akibu-desktop
> Xfer PIDs are now 3665
> BackupPC_refCountUpdate: computing totals for host akibu-desktop
> bpc_lib_conf_init: topDir = /mnt/backup_disks/backuppc, logLevel = 9
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
> = 0
> BackupPC_refCountUpdate: host akibu-desktop got 0 errors (took 0 secs)
> BackupPC_refCountUpdate total errors: 0
> Xfer PIDs are now
> Finished BackupPC_refCountUpdate (running time: 0 sec)
> Xfer PIDs are now
>
>
>
>
>
>
>
>
> ------------------------------
>
> *From:* Craig Barratt via BackupPC-users <backuppc-users@lists.
> sourceforge.net>
> *Sent:* Saturday, June 10, 2017 6:32 PM
> *To:* mst...@chicago.us.mensa.org; General list for user discussion,
> questions and support
> *Cc:* Craig Barratt
> *Subject:* Re: [BackupPC-users] Unexplained Error Code 255 - BackupPC
>
>
>
> The strace is showing the dynamic linking during startup of ssh, which
> isn't particularly relevant.  It's not showing the files being backed up.
>
>
>
> What we are missing is the log output from XferLOG.  That has the more
> detailed information (eg, exact rsync / ssh args).  Can you send that
> please?  You'll find it in the per-PC backup directory, eg:
> /data/BackupPC/pc/clientName/XferLOG.bad.z.  Use BackupPC_zcat to
> uncompress it.
>
> Craig
>
>
>
> On Fri, Jun 9, 2017 at 10:38 PM, Michael Stowe <
> mst...@chicago.us.mensa.org> wrote:
>
> On 2017-06-09 08:10, Akibu Flash wrote:
>
> Just bumping this again. Any thoughts on how to resolve the below? Thanks.
>
> FROM: Akibu Flash <akibufl...@outlook.com> SENT: Monday, June 5, 2017
> 7:27:34 AM TO: Holger Parplies; Holger Parplies (wb...@parplies.de) CC:
> General list for user discussion, questions and support SUBJECT: Re:
> [BackupPC-users] Unexplained Error Code 255 – BackupPC
>
> Thanks @Holger Parplies (wb...@parplies.de) for your reply. See below:
>
> -----Original Message----- From: Holger Parplies [wb...@parplies.de]
> Sent: Tuesday, May 30, 2017 3:31 PM To: Akibu Flash <
> akibufl...@outlook.com> Cc: General list for user discussion, questions
> and support <backuppc-users@lists.sourceforge.net> Subject: Re:
> [BackupPC-users] Unexplained Error Code 255 – BackupPC
>
> Hi,
>
> Akibu Flash wrote on 2017-05-29 05:27:04 +0000 [Re: [BackupPC-users]
> Unexplained Error Code 255 – BackupPC]:
>
> […] I am running backuppc version 4.41 on a Debian computer.
>
> wow … where did you get that version from?
>
> - I must have been asleep when I wrote version 4.4.1.  I meant
>
> version 4.1.1.
>
> When I start a backup, it appears to properly connect to my Windows
> computer and then gives me an error message. ?Got fatal error
>
> during
>
> xfer (rsync error: error in rsync protocol data stream (code 12) at
> io.c(629) [Receiver=3.0.9.6])? […] Please note that I am able to
>
> ssh
>
> and rsync into the Windows computer manually from the linux computer
>
> ^^^^^^^^
>
> without problem.
>
> Also without extraenous output? You seem to be using rsync over ssh, and
> rsync is quite fussy about messages that it does not expect. As a rule of
> thumb, to a *Linux* computer,
>
> % ssh clientcomputer true
>
> %
>
> should immediately display the next prompt as indicated above, i.e.
> nothing extra, not even blanks or newlines. For Windoze, your mileage may
> vary, but it probably won't. The actual invokation used by BackupPC (or
> rather rsync_bpc) might include extra options to ssh, e.g. -q -x -l
> someuser … include those when testing.
>
> - Correct, Holger.  I am using rsync over ssh and ssh seems to
>
> work without a problem. When I run the test you suggested: “$ssh
> targetcomputer true”, I merely get the prompt in response “$”. Strace seems
> to confirm that ssh is working correctly as when I ssh into the
> targetcomputer from the command line, and while running running strace on
> the targetcomputer, all seems to work as expected. In addition, when I
> rsync into the targetcomputer from the command line, rsync appears to work
> just fine.
>
> However, when I use the backuppc program to rsync into the very same
> targetcomputer, I get the Unexplained Error Code 255 message. Below shows
> the ssh strace when I started a manual backuppc backup of some files on the
> targetcomputer, if that helps. My log level is up to 9, but not much
> information is being generated. I am unclear of how to diagnose as I am not
> that versed in linux. Any help would be appreciated. Thanks. Akibu.
>
> Strace command used: $sudo strace -f -v -e open /etc/init.d/ssh restart
>
> strace: Process 11860 attached [pid 11860] open("/proc/self/oom_score_adj",
> O_WRONLY|O_CREAT|O_TRUNC, 0666) = 10 [pid 11860] open("/etc/ld.so.cache",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] 
> open("/lib/x86_64-linux-gnu/libcrypto.so.1.0.0",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] open("/lib/x86_64-linux-gnu/libutil.so.1",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] open("/lib/x86_64-linux-gnu/libz.so.1",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] 
> open("/lib/x86_64-linux-gnu/libcrypt.so.1",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] open("/lib/x86_64-linux-gnu/libc.so.6",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] open("/lib/x86_64-linux-gnu/libdl.so.2",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] open("/dev/null", O_RDWR) = 3 [pid
> 11860] open("/proc/11860/fd", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC)
> = 3 [pid 11860] open("/dev/urandom", O_RDONLY|O_NOCTTY|O_NONBLOCK) = 3 [pid
> 11860] open("/etc/gai.conf", O_RDONLY|O_CLOEXEC) = 3 [pid 11860]
> open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3 [pid 11860]
> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 [pid 11860]
> open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 3
> [pid 11860] open("/lib/x86_64-linux-gnu/libnsl.so.1", O_RDONLY|O_CLOEXEC)
> = 3 [pid 11860] open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 [pid
> 11860] open("/lib/x86_64-linux-gnu/libnss_nis.so.2", O_RDONLY|O_CLOEXEC)
> = 3 [pid 11860] open("/lib/x86_64-linux-gnu/libnss_files.so.2",
> O_RDONLY|O_CLOEXEC) = 3 [pid 11860] open("/etc/passwd", O_RDONLY|O_CLOEXEC)
> = 3 [pid 11860] open("/usr/local/etc/ssh_host_rsa_key", O_RDONLY) = 3
> [pid 11860] open("/usr/local/etc/ssh_host_rsa_key", O_RDONLY) = 3 [pid
> 11860] open("/usr/local/etc/ssh_host_rsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_rsa_key.pub", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_dsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_dsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_dsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_dsa_key.pub", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ecdsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ecdsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ecdsa_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ecdsa_key.pub", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ed25519_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ed25519_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ed25519_key", O_RDONLY) = 3 [pid 11860]
> open("/usr/local/etc/ssh_host_ed25519_key.pub", O_RDONLY) = 3 [pid 11860]
> open("/dev/tty", O_RDONLY|O_NOCTTY) = -1 ENOTTY (Inappropriate ioctl for
> device) [pid 11860] open("/dev/null", O_RDWR) = 4 strace: Process 11861
> attached [pid 11861] open("/dev/urandom", O_RDONLY|O_NOCTTY|O_NONBLOCK) = 6
> [pid 11861] +++ exited with 255 +++ [pid 11860] open("/etc/localtime",
> O_RDONLY|O_CLOEXEC) = 4 [pid 11860] +++ exited with 255 +++ --- SIGCHLD
> {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=11860, si_uid=0,
> si_status=255, si_utime=0, si_stime=0} ---
>
> Err.
>
> What, exactly, are you trying to resolve? I suspect you've gotten no
> answer because many people looked and said, well, that's obvious, don't
> back up the /dev directory, because it's dynamically created. While you're
> at it, don't back up /proc, /sys, or /tmp.
>
> [image:
> https://u2182357.ct.sendgrid.net/wf/open?upn=OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91C2l1P-2FoUmPYzy-2BphQ-2BNiQtvKH-2FYuxmNdP107-2F4ivZY931Pn-2BaNfBQgCnzehEPMPWmYlqXHcoF7LyIQvsH-2BAqF48iT8MrNZ4gIsXjI1Uo-2BHA06aOvnBPnilKUN9gSbMcB4HL977PZLEm9V4Eev5WKbIaby9rAW-2BNHV4lE1nlmB2d-2F8CkzYejxu4GZa6Njc4bdy]
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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/
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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/

Reply via email to