[LUNI] rsync HELP NEEDED.

[Kristian Kielhofner]

Richard Reina wrote:
> Joe,
> 
> Thanks very much for the reply.  I followed your
> advice  and I'm getting closer.
> 
> rsync -vv file1 192.168.0.14::test-data
> total: matches=0 tag_hits=0 data=0
> wrote 98 bytes read 41 bytes 278 bytes/sec
> total size is 9 speed is 0.06
> 
> After seeing that I thought it had worked. Except
> file1 is not on 192.168.0.14. 
> 
> 192.168.0.14
> cat /var/log/rsync
> 
> 2005/03/12 11:33:27 [18105] rsyncd version 2.6.2
> starting, listening on port 873
> 2005/03/12 11:33:27 [18105] rsync: open inbound socket
> on port 873 failed: Address already in use
> 2005/03/12 11:33:27 [18105] rsync error: error in
> socket IO (code 10) at socket .c(456)
> 
> Any idea what am I missing?  Thanks again ofr your
> help thus far.
> 
> R
> 
> --- Joe Digilio <jgd42-luni at yahoo.com> wrote:
> 
> 
>>First, your rsyncd.conf file...
>>* remove the "syslog facility" line. You don't need
>>it for testing and likely
>>don't have it set correctly anyways (unless "yes" is
>>a facility in your
>>syslog.conf file)
>>
>>* add a line for logging similar to this in the
>>global section (ie, not in a
>>module)
>>log file = /var/log/rsync
>>
>>* Most of those options should be in the global
>>section. Your rsyncd.conf
>>should look similar to this:
>>
>>### BEGIN rsyncd.conf ###
>>pid file = /var/run/rsyncd.pid
>>motd     = /etc/rsyncd/motd
>>log file = /var/log/rsync
>>
>>[test-data]
>>  path    = /home/richard
>>  max connections = 10
>>  read only = no
>>### END rsyncd.conf ###
>>
>>
>>Next, because you have the "path" option set in
>>rsyncd.conf, you don't need
>>/home/richard when you run rsync.  I should be
>>something like this:
>>
>>  rsync file1 192.168.0.14::test-data/home/richard
> 
> 
>>I added the verbose options so you can see more of
>>what's going on.
>>
>>If it still doesn't work, check the log file
>>(/var/log/rsync) on 192.168.0.14.
>>Also, what version are you using? 2.6.3 has better
>>error handling functionality
>>than previous versions.
>>
>>HTH.
>>
>>-Joe
>>
>>
>>--- Richard Reina wrote:
>>
>>>I am trying to copy a file with rsync.
>>>
>>>the remote machine's /etc/rsyncd.conf 
>>>
>>>[test-data]
>>>path    = /home/richard
>>>motd    = /etc/rsyncd/motd
>>>max connections = 10
>>>read only = no
>>>syslog facility = yes
>>>pid file = /var/run/rsyncd.pid
>>>
>>>I have started rsyncd with the command:
>>>rsync --daemon
>>>
>>>When I try:
>>>
>>>rsync file1 192.168.0.14::test-data/home/richard
>>>
>>>I get:
>>>
>>>unexpected EOF in read_timeout
>>>
>>>If I try:
>>>
>>>rsync file1 192.168.0.14::test-data /home/richard
>>>
>>>I get:
>>>
>>>link_stat 192.168.0.14::test-data : No such file
>>
>>or
>>
>>>directory
>>>
>>>If nayone can help me I would be greatly
>>>apprecieative.
>>>
>>>Thanks 
>>>
>>>R


Richard,

	If this is your home directory, why not get rid of the native rsync 
protocol (and rsyncd.conf) altogether and encrypt your session with SSH:

rsync -avr -e ssh 192.168.0.14:/path/to/directory/file /path/to/local/copy/

	Or, like the ncftpput thread before, use scp.  That being said, I think 
that you may be running rsyncd from an init script AND inetd.  That's 
just a guess, I still think you are better off using SSH to wrap your 
rsync transfers and ditching rsyncd altogther.

	Rsyncd/rsync protocol it seems was made for mirroring public FTP/web 
sites, etc.  The kind of thing where your 25 mirror servers all over the 
globe could easily do incremental updates to a main repo.  Rsync over 
SSH is easier (IMHO), more flexible, and more secure for what it looks 
like you are trying to do.

--
Kristian Kielhofner