David Wynn via BackupPC-users wrote at about 15:53:25 -0600 on Friday, June 7, 2019: > -----Original Message----- > From: G.W. Haywood via BackupPC-users > Looks like you might have installed BackupPC from more than one, er, source. > In the interests of their own sanity, package maintainers for the likes of > Debian, Ubuntu and derivative distributions do (shall we say) interesting > things with the files and directories used 'upstream' by the authors of the > packages (....) > > DW>> Since this was a brand new, clean system I don't think I messed up the > install process ... very careful in doing the system install followed by the > few other programs we use (Calibre, etc). And the BackupPC was directly > from the UBUNTU software app. I don't think it is a problem either, just > curious I guess .... <<< > Pretty sure that BackupPC is *not* from Ubuntu. Indeed Ubuntu, like Debian uses the all lowercase 'backuppc' I have seen BackupPC used by Fedora.
> Your rsync problem _probably_ isn't related to this issue. I've seen a few > problems when newer rsyncs wouldn't talk to older ones because of the lack > of (default) shared encryption mechanisms. This happens especially when you > work with more than one system or distribution or release of same, and some > of them aren't as up to date as the others for perhaps perfectly good > reasons. Same thing happened with SSH too. > > DW>>> That's my biggest concern too -- the versioning and differences > between the systems. And yet the debug info shows the two talking back and > forth, exchanging keys, etc and then finally being "connected". It is only > when the rsync-bpc code tries to hand over the next "command" that it is > somehow being started with the IP address ....... <<<<< Well having two different versions of BackupPC installed could definitely create confusion in terms of non-compatible versions of rsync (particularly the Perl version). > > Best I can suggest is crank up the debugging levels and log everything you > can until you find something, maybe try using Wireshark too, and don't be > afraid to dig into the code and put some 'print' statements in to add to > what sometimes might be less than informative logging. > > DW>>> I have upped the debug level but it only affects the SSH info, not the > rsync-bpc process ... I'm still trying to uncover where the "command" gets > built that ssh is passing over the pipe to the client. Somehow it is using > either the $host info or the ping info that is associated with the client > and passing it as part of the command. I tried to look at what is happening > on the older 3.1 backup system with the RSYNC clients but can't get the same > level of debug info -- and of course they are all working just fine. Would > be great if someone could post their RSYNC log showing the debug level 1 > info and what is being passed in the command line ... any takers??? <<<<< > > Just my 2 * $currency_units, HTH. I've glossed over a few things. :/ > > DW>>>> Appreciate your info and help ... you mentioned using Wireshark .. > have had no experience with it at all -- is it very hard to use and what > would it show me? And about putting "print" statements into the code -- > wouldn't I need to recompile/rebuild the code after that ?? or can I just > put them in the existing code pieces? <<<<< > Solution seems pretty simple. You somehow managed to install 2 potentially conflicting versions of BackupPC. If you managed to install 2 different versions without even realizing it, you most likely also messed up a bunch of other things... Suggest you completely remove them both and then reinstall fresh from Debian using "apt get install backuppc. This will be much easier than troubleshooting all the places you may have messed up due to the above... _______________________________________________ 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/
