On 5/11/2010 12:45 PM, Les Mikesell wrote: > On 5/11/2010 12:26 PM, Nick Bright wrote: > >> On 5/11/2010 9:53 AM, Les Mikesell wrote: >> >>> On 5/10/2010 8:14 PM, Nick Bright wrote: >>> >>> >>>> Let me start off by saying this: I know what I'm doing. >>>> >>>> >>>> >>> [...] >>> >>> >>>> full backup started for directory / (baseline backup #259) >>>> started full dump, share=/ >>>> Running: /usr/bin/ssh -q -x -l root TargetServer /usr/bin/rsync --server >>>> --sender --numeric-ids --perms --owner --group -D --links --hard-links >>>> --times --block-size=2048 --recursive --port=38271 --ignore-times . / >>>> >>>> >>> What does --port=38271 mean here? Isn't that supposed to be used for >>> standalone rsyncd, not over ssh? >>> >>> >>> >> Thank you for taking the time to reply. >> >> It's the port that SSHD is listening on. I had been stripping that out >> because the guy that runs the target server is a little paranoid about >> his SSH access. >> > In that case, shouldn't it be in the ssh arguments, not part of the > rsync command passed to the remote? I don't see how this would connect > at all. > >
Precisely correct. I removed those port arguments and set the SSH server on the target machine back to port 22 and it's working. Now I need to figure out how to properly tell BackupPC that SSH is on a non-standard port. I thought that I was doing it properly, but clearly not. All my other boxes use the standard ports, which is why I've not had this issue before. Thank you very much for taking the time to reply and help find the resolution to the issue. - Nick ------------------------------------------------------------------------------ _______________________________________________ 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/
