Re: [BackupPC-users] Unable to read 4 bytes revisited

> -----Original Message-----
> From: Adam Goryachev [mailto:mailinglists AT websitemanagers.com DOT au]
> Sent: den 11 oktober 2014 13:21
> To: backuppc-users AT lists.sourceforge DOT net
> Subject: Re: [BackupPC-users] Unable to read 4 bytes revisited
> 
> On 11/10/14 21:12, Sorin Srbu wrote:
> 
> 
>       Hi all,
> 
> 
> 
>       I set up BackupPC at home to make more systematic backups
> of mine and wifeys homefolders on the  samba-server and ran into the
> somewhat dreaded "Unable to read 4 bytes"-error.
> 
> 
> 
>       Problem is *maybe* that the host to be backed up is running
> sshd on port 522.
> 
> Yep, but that is easily solved.
> 
> 
>       What I've done so far is to create the passwordless login with
> my backuppc-user to the host, tested and this works.
> 
>       As the backuppc-user I can login to the host using ssh over port
> 522 without entering a password and becoming root.
> 
> 
> 
>       Rsync is used as the transfer method, BTW.
> 
> 
> 
>       In the BPC web-GUI, I've added port 522 to RsyncClientCMD,
> so that now it reads:
>       $sshPath -q -x -l -p 522 root $host $rsyncPath $argList+
> 
>       Was this correct to do?
> 
> 
> 
> 
> No, this is your mistake. You need to know what all those options mean. -l is
> the username to use when authenticating with the remote host, you have
> provided the username as -p, and then I don't know what 522 and root are
> going to be interpreted as, I guess 522 would be the hostname, and root
> would become the path to rsync...
> 
> Try this:
> $sshPath -q -x -l root -p 522 $host $rsyncPath $argList+
> 
> 
> 
>       I've tried to disable iptables on the host, with no change, still
> getting the 4 byte-error.
> 
> 
> 
>       What am I missing?? Is there something with rsync not
> connecting properly maybe?
> 
> 
> 
> Also, next time please provide the log file as that will usually provide more
> information if the solution isn't so easy.

Thanks for the hints. I'll try this when I get home.

Seems I assumed to much with the arguments list... 8-/

--
//Sorin

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/