[BackupPC-users] List of All Files Being Backed Up
I've tried to search using some different keywords and combinations but have had no luck in finding an answer. Here's my situation . I am backing up around 150 different files from a NAS but using multiple hosts to do so in order to keep the file transfer size down to <20GB at a time. This is across the 'internet' so bandwidth is not under my control and I want to make sure the jobs don't crap out at bad times. I've found that <20GB at a time usually works great. But, in order to manage the sizes I first created the individual lists based on the size of the files/directories and input them manually into my config files for each host. For example, HOST1 may have 40 smaller files to get to the 20GB limit whereas HOST10 may only have 1 file/directory to get to the limit. Now I have the problem of trying to find an individual file/directory from around 18 different HOSTx setups. Is there an easy way to get/create a listing that would should the HOSTx and the files/directories that are being backed up under it? I have thought of trying to write a 'script' to traverse the individual HOSTx.pl files and extract the info - but my scripting is purely of a W10 nature and even at that is poor and wordy. (Oh for the days of COBOL and PL/1.) Just wondering if there is something I have missed in the documentation or in trying to search the forums. Someone must have had this problem before me. Thanks for your help DW ___ 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] BACKUPPC V4 - rsync-bpc error connecting to client
Thanks Adam . but thru trial and error I have been successful!
EUREKA!! Hallelujah!! And all that jazz ..
I removed using the ssh.conf, changed the ClientNameAlias to the IP address
and put the RsyncSshArgs back to "$sshPath -o
KexAlgorithms=diffie-hellman-group14-sha1 -o HostKeyAlgorithms=+ssh-dss -l
root".
And as you suggested, it was a USER (me) config problem things that
worked on V3.3 didn't do the same here ... but with the help/suggestions of
others I managed to get the right combination of info in the right fields
.
Thanks again .
Dave W
-Original Message-
From: Adam Goryachev [mailto:mailingli...@websitemanagers.com.au]
Sent: June 10, 2019 5:54 PM
To: backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to
client
Apologies, the last email was truncated...
Hi David,
On 9/6/19 5:19 am, David Wynn via BackupPC-users wrote:
> Well ... I checked on the NETSTORE box via PUTTY and it says that
> 'rsync is a tracked alias for /usr/sbin/rsync' which is why I guess
> that this works on the old version of BackupPC (V3.3.1) ... that's all
> I have in the RsyncClientPath field as an override. Anyways, I changed
> the V4 override to be the /usr/sbin/rsync field and tested . SAME
> result - it prepends the command with the IP address of the client and
> of course dies on the 'not found error' I have attached a picture
> of that part of the log file to show it is still happening
>
> The only place the IP address shows up is in the very last field that
> is passed to the rsync_bpc command (192.168.1.6:/nfs/Public). It is
> also in the ssh config file as the HostName field but without it, ssh
> will not run.
> So whatever/whoever is generating the commands to be passed BY ssh is
> somehow using the IP address as part of the info -- but danged if I
> can find out which module/program/subroutine is performing that
> function.
>
> At this point I seem to have two options --- either keep my old system
> up and running since RSYNC works fine there, or change all my backups
> for the NETSTORE back to SMB and run the new system. I would have
> thought that this would have been an easy thing for the developers to
> determine the cause of but it seems they don't follow this forum.
>
> Thanks for the help and suggestions.
I think you might be rather frustrated at this point, and this just might
aggravate you further, but you do seem like an experience and knowledgeable
person, so hopefully you will recognise it as intended.
Your issue seems rather simple, and almost certainly is not a developer
issue, so I doubt it would attract the attention of a developer. Given that
BackupPC 4.x is successfully used by a large number of other people (myself
included), it's pretty unlikely to have such a significant problem (not
backing up hosts via rsync). So, I would suggest to go back and take another
look at your config files, and perhaps throw them away (move them out of the
way), and start from the original distribution samples, and then customise
towards your required config.
One significant issue is to try to migrate your old v3 config file to the
new v4, but there are a lot of changes to the config, and while it might
mostly work, there are going to be some surprises that can get you.
So, it looks like somewhere, you are building the ssh and rsync commands
(which are done from multiple places), and ending up with adding the $host
twice, and/or missing the definition of the rsync variable.
You might have posted the complete config file before (I haven't been paying
too much attention to this thread, sorry), but could you post the sections
of your config file the define:
$Conf{SshPath}
$Conf{RsyncArgs}
$Conf{RsyncArgsExtra}
$Conf{RsyncFullArgsExtra}
$Conf{RsyncSshArgs}
$Conf{RsyncClientPath}
Also, a full copy of the client config file (feel free to adjust/remove any
username/password, though there shouldn't be for this file.
Finally, the one single command I've found to be the *most* helpful in
debugging any such issues is this:
/usr/lib/backuppc/bin/BackupPC_dump -f -vvv hostname
Which will just try to do a full backup, but show you on the console what it
is doing through each step. You should make sure there is no scheduled
backup for this host, and no in-progress backup for this host when you run
this command. Under normal operation, you shouldn't use this command.
Hope that helps.
Regards,
Adam
--
--
Adam Goryachev Website Managers www.websitemanagers.com.au
--
The information in this e-mail is confidential and may be legally
privileged.
It is intended solely for the addressee. Access to this e-mail by anyone
else is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be
Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client
EUREKA!! Hallelujah!! And all that jazz .. I removed using the ssh.conf, changed the ClientNameAlias to the IP address and put the RsyncSshArgs back to "$sshPath -o KexAlgorithms=diffie-hellman-group14-sha1 -o HostKeyAlgorithms=+ssh-dss -l root". And that combo seems to work fine . will try another host setup with same configuration to make sure . Just some combo of those two areas and thank god it was a "user" config error -Original Message- From: Joyce, Stephen [mailto:step...@email.unc.edu] Sent: June 10, 2019 3:58 PM To: David Wynn Subject: RE: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client Hi, David. Try commenting out "HostName 192.168.1.6" from your ssh.conf, AND adding "192.168.1.6" (without "" marks, when done via the gui) to the ClientNameAlias for the host nbox, and trying the backup again. Cheers, Stephen On Mon, 10 Jun 2019, David Wynn wrote: > > > -Original Message- > From: Joyce, Stephen [mailto:step...@email.unc.edu] > Sent: June 10, 2019 12:49 PM > To: David Wynn > Subject: RE: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting > to client > > On Mon, 10 Jun 2019, David Wynn wrote: > > > If you want the relevant code, take a look at > $topdir/lib/BackupPC/Xfer/Rsync.pm. Interesting bits start around line > 430 and continue on to about 465. > >> THANKS ... have looked at the code but will spend a little more >> time > trying to understand it and see if there is anything that might help. > Not a PERL coder so it sometimes takes a while to see what is happening. > COBOL/PL1 and RPG were what I grew up with ... < > > > But it really smells like a config issue on your server. >> My thinking too but danged if I can see the mistake/error. And >> yet I > have it working fine on my old system (UBUNTU 16 and BackupPC 3.3) << > > What happens if, wherever you have the "root@192..." line (probably > RsyncSshArgs, but possibly one of RsyncBackupPCPath, RsyncClientPath, > RsyncArgs, RsyncArgsExtra, RsyncFullArgsExtra) you remove the IP > address leaving just "root" for the username? > >> As I mentioned I moved all options to the SSH.CONF file to remove >> them > from the equation ... here is what the file looks like . > Host nbox > KexAlgorithms=+diffie-hellman-group14-sha1 > HostKeyAlgorithms=+ssh-dss > User root > HostName 192.168.1.6 > LogLevel DEBUG2 > > So there is no @ left in the string. I just commented out the User in > ssh.conf, reloaded and then changed RsyncSshArgs to /usr/bin/ssh nbox -l > root and I get the same error. And withouth HostName in the conf file it > errors out right away in SSH because it can't resolve nbox port 22 > . and if I change the args to include root@IP then it still errors > on the RSYNC line . > > It is very frustrating .. old works, new doesn't ... RSYNCD works > RSYNC doesn't aaa! > > Thanks again Stephen Dave > > ___ 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] BACKUPPC V4 - rsync-bpc error connecting to client
Updates added below .. and latest copy of error log (abbreviated to save
space .)
Xfer PIDs are now 30009
This is the rsync child about to exec /usr/local/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles =
0
debug2: resolving "192.168.1.6" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.1.6 [192.168.1.6] port 22.
debug1: Connection established.
passing requests back and forth <
debug1: Authenticating to 192.168.1.6:22 as 'root'
passing and requesting keys, etc >
debug1: Host '192.168.1.6' is known and matches the DSA host key.
more talking blah, blah, blah
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.1.6 ([192.168.1.6]:22).
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug1: Sending command: 192.168.1.6 /usr/sbin/rsync --server --sender
-slHogDtprcxe.iLsfxC <<< ERROR LINE HERE
debug2: channel 0: request exec confirm 1
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug2: channel 0: rcvd ext data 4
sh: debug2: channel 0: written 4 to efd 6
debug2: channel 0: rcvd ext data 22
192.168.1.6: not founddebug2: channel 0: written 22 to efd 6 <<<
OF COURSE 192.168.1.6 is an IP address, not a command!! >
Transferred: sent 3120, received 2512 bytes, in 0.0 seconds
Bytes per second: sent 292325.2, received 235359.2
debug1: Exit status 127
rsync_bpc: connection unexpectedly closed (0 bytes received so far)
[Receiver]
bpc_sysCall_cleanup: doneInit = 1
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 2 inode
Parsing done: nFilesTotal = 0
rsync error: remote command not found (code 127) at io.c(226)
[Receiver=3.1.2.0]
rsync_bpc exited with fatal status 127 (32512) (rsync error: remote command
not found (code 127) at io.c(226) [Receiver=3.1.2.0])
-Original Message-
From: G.W. Haywood via BackupPC-users
[mailto:backuppc-users@lists.sourceforge.net]
Sent: June 9, 2019 9:06 AM
To: backuppc-users@lists.sourceforge.net
Cc: G.W. Haywood
Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to
client
Hi Ged,
On Sun, 9 Jun 2019, David Wynn wrote:
Sorry, I don't genrally see attachments.
No problem .. the pic just reiterated the error from ssh processing
showing the IP address being send as part of the command and then of course
the error saying not found . and that the /usr/sbin/rsync was being sent
this time . I included the same info above .
Then I extracted the two archives into a scratch directory and did a
recursive diff between the two trees. It left me rather confused but there
are mentions of paths in there that you might find interesting.
Your steps in creating the diff between the two would be a little too
much for this old man to follow and try to recreate. I'll take your word
that there are probably some differences. Based on what I see in the two
directories I mentioned earlier (BackupPC vs backuppc) I don't think there
would be any cause for problems as they either contain old config files or
other stuff -- but no 'code'.
<<<
Well, back to debugging. How comfortable are you with coding in Perl?
Places you might look in the 4.3.0 directory tree for things relevant to the
rsync commands are
I'd say that I would be OK with trying to put in some print statements
if I could find the appropriate code to test ... but so far I just don't
think I've found the right module/subroutine that would be the one. I've
looked in all your suggested places and nothing jumps out as the 'aha ..
let's test this' location. I can find the spot in RSYNC.PM ( LN450
print("This is the rsync child about to exec $conf->{RsyncBackupPCPath}\n");
$bpc->cmdExecOrEval($rsyncCmd); ) that appears in the log just before all
the SSH DEBUG messages start appearing, but just can't follow who/where the
command gets created that is sent by SSH once the authentication has
completed.
<<
One other thing that springs to mind is your version of rsync_bpc.
tornado:# >>> ls -l `which rsync_bpc`
-rwxr-xr-x 1 root staff 1982456 Aug 28 2018 /usr/local/bin/rsync_bpc
It should be good ... but this is what I get
[root@ubuntu2 ~]# ls -l `which rsync_bpc`
-rwxr-xr-x 1 root root 2338784 May 29 16:49 /usr/local/bin/rsync_bpc
Where May 29 is the day I would have installed so that would have been the
'make' date. It appears to be a little larger so probably updated code?
<<<
I went through the same soul-searching when I moved from V3 to V4.
> Will keep plugging away on the RSYNC issue for a while and was also
thi
Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client
Thanks Michael .. Have checked and rechecked settings and they seem okay ...
but have included the netpublic4.pl file contents for review . I had to
change the RsyncClientPath because of the system that is on the Netstore
device - it works on my other system that is using RSYNC to backup the files
..
>>>>>> netpublic4.pl <<<<<<<<<
$Conf{BackupFilesOnly} = {
'/nfs/Public' => [
'.FULL BLAST CREATIVE Or INKPLOT PROJECTS/*',
'.HOTWINGS & WINGSNBEERS/*'
]
};
$Conf{RsyncClientPath} = 'rsync';
$Conf{RsyncShareName} = [
'/nfs/Public'
];
$Conf{RsyncSshArgs} = [
'-e',
'$sshPath nbox'
];
$Conf{FullAgeMax} = 90;
$Conf{ClientNameAlias} = [
'Netstore'
];
$Conf{XferLogLevel} = 5;
>>>>>>>>>>>>>>>>>> end <<<<<<<<<<<<<<<<<<<<
I also moved the paramters for the ssh command into the config file for the
host 'nbox' .. Just looks neater than the longer string that was there . and
it is still failing at the same place . somehow getting the IP address stuck
in the command being sent ..
DW
From: Michael Stowe [mailto:michael.st...@member.mensa.org]
Sent: June 7, 2019 4:44 PM
To: General list for user discussion, questions and support
Cc: m...@visionary.com; David Wynn
Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to
client
On 2019-06-05 12:52, David Wynn via BackupPC-users wrote:
Hi Mike ... don't know if I replied correctly to this or not And NO - I
have not changed the RsyncBackupPCPath, it is still
/usr/local/bin/rsync_bpc. And YES, the 192.168.1.6 is the IP address to our
Netstore device. Just can't figure out why it is appearing in the command
line ... aaarrrggghh (I almost hate technology!)
One minor thing, it actually looks like RsyncClientPath is set to
192.168.1.6. It should look like this:
$Conf{RsyncClientPath} = '/usr/bin/rsync';
Also worth checking:
$Conf{RsyncSshArgs} = [
'-e', '$sshPath -l root',
];
___
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] BACKUPPC V4 - rsync-bpc error connecting to client
-Original Message- From: G.W. Haywood via BackupPC-users [mailto:backuppc-users@lists.sourceforge.net] Sent: June 7, 2019 7:34 AM To: backuppc-users@lists.sourceforge.net Cc: G.W. Haywood Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client Hi there, On Fri, 7 Jun 2019, David Wynn wrote: > I?ve just noticed that there are two directories ... The fact that you have one of your IP addresses appearing some place it probably shouldn't be makes me wonder if you've made a typo in a configuration file, but I couldn't swear to it. DW>> I thought that way too and have been racking my brain looking at the files to see if anything missing or extraneous but just don't see it. And it is interesting because I have both an RSYNCD and SMB host running just fine . might just have to give up on RSYNC and go back to SMB for all the backups. <<< 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 <<< 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 ... < 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? < -- 73, Ged. ___ 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 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] BACKUPPC V4 - rsync-bpc error connecting to client
I’ve just noticed that there are two directories on the new servier – both for ‘backuppc’! One of the directories is ‘BackupPC’ (note the caps) and the other is simply ‘backuppc’. The latter contains a config.pl (2016/12/14) file as well as Apache.conf (2019/5/29), hosts (2016/12/14). htpasswd (2019/5/28) and localhost.pl (2016/12/14). BackupPC contains a config.pl (2019/6/4), hosts (2019/6/4) as well as BackupPC.users and a pc directory for the hosts .pl files. Hopefully this does not cause any problems, but just wanted to note it in case they shouldn’t be there.Just looking for any reason to try and find out why my rsync won’t run on the new server … and how the IP address for the client gets stuck in the command being sent …… any help appreciated!! Dave W From: David Wynn via BackupPC-users [mailto:backuppc-users@lists.sourceforge.net] Sent: June 5, 2019 1:52 PM To: m...@visionary.com; backuppc-users@lists.sourceforge.net Cc: David Wynn Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client Hi Mike … don’t know if I replied correctly to this or not …. And NO – I have not changed the RsyncBackupPCPath, it is still /usr/local/bin/rsync_bpc. And YES, the 192.168.1.6 is the IP address to our Netstore device. Just can’t figure out why it is appearing in the command line … aaarrrggghh (I almost hate technology!) From: Dave Wynn [mailto:dewyn...@yahoo.ca] Sent: June 5, 2019 1:19 PM To: m...@visionary.com <mailto:m...@visionary.com> Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client Sent from Yahoo Mail on Android <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature> On Wed., 5 Jun. 2019 at 12:55 p.m., Mike Hughes mailto:m...@visionary.com> > wrote: On Wed, 2019-06-05 at 11:51 -0600, David Wynn via BackupPC-users wrote: > debug1: Sending command: 192.168.1.6 rsync --server --sender > -slHogDtprcxe.iLsfxC > sh: 192.168.1.6: not found This line tells us that your shell (sh) is trying to run the command: "192.168.1.6" That looks like an IP address rather than a command. Did you modify the RsyncBackupPCPath variable? ___ 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] BACKUPPC V4 - rsync-bpc error connecting to client
Hi Mike … don’t know if I replied correctly to this or not …. And NO – I have not changed the RsyncBackupPCPath, it is still /usr/local/bin/rsync_bpc. And YES, the 192.168.1.6 is the IP address to our Netstore device. Just can’t figure out why it is appearing in the command line … aaarrrggghh (I almost hate technology!) From: Dave Wynn [mailto:dewyn...@yahoo.ca] Sent: June 5, 2019 1:19 PM To: m...@visionary.com Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client Sent from Yahoo Mail on Android <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature> On Wed., 5 Jun. 2019 at 12:55 p.m., Mike Hughes mailto:m...@visionary.com> > wrote: On Wed, 2019-06-05 at 11:51 -0600, David Wynn via BackupPC-users wrote: > debug1: Sending command: 192.168.1.6 rsync --server --sender > -slHogDtprcxe.iLsfxC > sh: 192.168.1.6: not found This line tells us that your shell (sh) is trying to run the command: "192.168.1.6" That looks like an IP address rather than a command. Did you modify the RsyncBackupPCPath variable? ___ 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] BACKUPPC V4 - rsync-bpc error connecting to client
Hi there .. I have a small home network and have been using Backuppc for the past 5 years. The last system was based on Ubuntu 16.04.6 LTS and Backuppc V3.3.1. I was originally using SMB for backing up our PC's and NETSTORE device but recently switched to using RSYNC/RSYNCD - and everything is working fine.We have a newer system that I just installed Ubuntu 18.04.2 LTS, Backuppc V4.3.0, RSYNC V3.1.2 and OpenSSH 7.6p1 on and am trying to get it running. By the way, our NETSTORE device is running Linux Netstore 3.2.40, has RSYNC at V3.0.7 and OpenSSH 5.0p1 that supports protocol 2. SSH has had keys generated and installed and I can connect from new server to client with no password. The only issue is that I had to account for ssh-dss differences and ended up having to add the following (-oKexAlgorithms=diffie-hellman-group14-sha1 -oHostKeyAlgorithms=+ssh-dss) options into the command get it working. On the new system I have been successful in using Backuppc and RYSNCD to backup the network PC's with no problems. Took a few tries to get them going but success in the end. I have also been successful in using SMB to connect and backup some of the NETSTORE files even tho it seems to take a little longer. But . I have not been successful in using RSYNC to connect and backup the NETSTORE files from the new installation. LOG FILE FROM BACKUPPC <<< XferLOG file /var/lib/backuppc/pc/netpublic4/XferLOG.0.z created 2019-06-05 09:00:00 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 /var/lib/backuppc --bpc-host-name netpublic4 --bpc-share-name /nfs/Public --bpc-bkup-num 0 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 2 --bpc-attrib-new --bpc-log-level 5 -e /usr/bin/ssh\ -v\ -l\ -oKexAlgorithms=diffie-hellman-group14-sha1\ -oHostKeyAlgorithms=+ssh-dss\ root@192.168.1.6 --rsync-path=rsync --super --recursive --protect-args --numeric-ids --perms --owner --group -D --times --links --hard-links --delete --delete-excluded --one-file-system --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --timeout=72000 --include=/.FULL\ BLAST\ CREATIVE\ \ Or\ \ INKPLOT\ PROJECTS --include=/.FULL\ BLAST\ CREATIVE\ \ Or\ \ INKPLOT\ PROJECTS/\* --include=/.HOTWINGS\ \&\ WINGSNBEERS --include=/.HOTWINGS\ \&\ WINGSNBEERS/\* --exclude=/\* --exclude=/.FULL\ BLAST\ CREATIVE\ \ Or\ \ INKPLOT\ PROJECTS/\* --exclude=/.HOTWINGS\ \&\ WINGSNBEERS/\* 192.168.1.6:/nfs/Public/ / full backup started for directory /nfs/Public Xfer PIDs are now 9656 This is the rsync child about to exec /usr/local/bin/rsync_bpc bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0 OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 192.168.1.6 [192.168.1.6] port 22. debug1: Connection established. .. ..(lines not shown but just connection stuff back and forth, till ...) Authenticated to 192.168.1.6 ([192.168.1.6]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: 192.168.1.6 rsync --server --sender -slHogDtprcxe.iLsfxC sh: 192.168.1.6: not found debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK debug1: fd 2 clearing O_NONBLOCK Transferred: sent 3120, received 2512 bytes, in 0.0 seconds Bytes per second: sent 280453.2, received 225800.8 debug1: Exit status 127 rsync_bpc: connection unexpectedly closed (0 bytes received so far) [Receiver] bpc_sysCall_cleanup: doneInit = 1 Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 2 inode Parsing done: nFilesTotal = 0 rsync error: remote command not found (code 127) at io.c(226) [Receiver=3.1.2.0] rsync_bpc exited with fatal status 127 (32512) (rsync error: remote command not found (code 127) at io.c(226) [Receiver=3.1.2.0]) ... ... (more cleanup lines and information but nothing useful) I cannot for the life of me determine what is happening or why ... is this an incompatability issue or just me screwing up the set-up. Thanks for the help - any and all questions, ideas, suggestions are welcome . (BTW - LINUX is not my area, I have a heavy PC background and it takes me twice as long to find the right UNIX command to do simple tasks - so please be gentle with this old man) Dave W dewyn...@yahoo.ca ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge
