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 taken in reliance
on it, is prohibited and may be unlawful. If you have received this message
in error, please notify us immediately. Please also destroy and delete the
message from your computer. Viruses - Any loss/damage incurred by receiving
this email is not the sender's responsibility.
_______________________________________________
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/
