Update: WARNING: --rsh or -e option ignored when connecting
torsyncdaemon]
Jack Khoo
jackkhoo at xybase.com
Wed Apr 17 03:39:01 EST 2002
i try to start the rsync daemon with " rsync -p 22 --daemon" on the remote server(host) and then
ps -ef |grep rsync
root 44262 1 0 01:18:57 - 0:00 /usr/local/bin/rsync -p --daemon 22
"rsync -auvz --password-file=/export/home/tester01/rsync.pwd
/export/home/tester01/. axlink at host::/home/axlink/rs"
i got the error below:
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)
but if i use back "rsync -auve ssh -z --password-file=/export/home/tester01/rsync.pwd
/export/home/tester01/. axlink at host:/home/axlink/rs"
it prompt for password, how do i escape from key in the passwd where auto login is possible by refer to rsync.pwd
kindly advise
tim.conway at philips.com wrote:
> the --pasword-file= option is only for passing a password to a rsync
> server, as you have set up with the rsync --daemon process. Your
> rsyncd.conf file is fine, too. The problem is that you aren't calling
> your rsync daemon from your commandline. You are trying to connect via
> rsync to host as axlink and start a 'rsync --sender' process, to transfer
> data within the ssh process.
>
> "rsync -auve ssh -z --port=22
> --password-file=/export/home/tester01/rsync.pwd
> /export/home/tester01/. axlink at host:/home/axlink/rs"
> should be
> "rsync -auvz --password-file=/export/home/tester01/rsync.pwd
> /export/home/tester01/. axlink at host::/home/axlink/rs"
> You don't use an external transport (-e ssh) to go to a rsync daemon.
> --port=22 implies that you don't have ssh, but rather rsyncd on port 22.
> rsyncd ordinarily listens on port 873, or at least you have inetd
> listening there and spawning off rsyncds as needed(my preferred method).
> You don't specify an alternate port to rsync --daemon, so i assume it's
> still on the default. Also, since you use a single colon in "axlink at host:/home/axlink/rs", along with "-e ssh", it's certain that you successfully connected to
> ssh (which coincidentally connected to port 22... in your invocation,
> --port= was ignored). I'll bet you can't ssh into host as axlink, at
> least, not without a password. Try my revised commandline.
>
> I'm ccing the list to keep people up on your resolution (they really do
> care).
>
> Tim Conway
> tim.conway at philips.com
> 303.682.4917
> Philips Semiconductor - Longmont TC
> 1880 Industrial Circle, Suite D
> Longmont, CO 80501
> Available via SameTime Connect within Philips, n9hmg on AIM
> perl -e 'print pack(nnnnnnnnnnnn,
> 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
> ".\n" '
> "There are some who call me.... Tim?"
>
> Jack Khoo <jackkhoo at xybase.com>
> 04/16/2002 04:42 AM
>
>
> To: Tim Conway/LMT/SC/PHILIPS at AMEC
> cc:
> Subject: Re: Update: WARNING: --rsh or -e option ignored when connecting to
> rsyncdaemon]
> Classification:
>
> thank for reply.
>
> anyway, i have rsync daemon on the remote system:
>
> ps -ef |grep rsync
> root 21540 1 0 Apr 09 - 0:00 /usr/local/bin/rsync
> --daemon
>
> motd file = /etc/motd_rsync
> max connections = 10
> lock file = /etc/rsyncd.lock
> syslog facility = local3
>
> [rs]
> comment = rs backup
> path = /home/axlink/rs
> read only = no
> uid = axlink
> gid = staff
> auth users = axlink
> secrets file = /etc/rsyncd.secrets
> dont compress = yes
>
> then when i try :
> rsync -auve ssh -z --port=22
> --password-file=/export/home/tester01/rsync.pwd
> /export/home/tester01/. axlink at host:/home/axlink/rs
>
> it's still prompt for the passwd, why? file permission of rsync.pwd =600
>
> i have not problem on doing all this in my LAN, but not on the WAN where
> both server is on
> different country. each of the server is behind the firewall where only
> port 22 is open, do i
> really need to open the port 873 as well, althrough we already define to
> use port 22 as a
> transport
>
> kindly advise
>
> thank in advance
>
> tim.conway at philips.com wrote:
>
> > You'll have to choose between transports. You are using the
> double-colon
> > (::) syntax, which specifies that rsync is to connect to a rsync daemon
> > running on port 873 (unless you specify a different port with --port=),
> > making its own tcp connection, rather than using an external transport
> > like rsh or ssh, thus the "-e ssh" part of your command is meaningless,
> > and rsync tells you so. From the output of your commands, it's apparent
> > that you have not set up a rsync daemon on the remote system. As ssh
> > works, you can simply use the standard single-colon syntax, which will
> > have rsync use an external transport, either the default, or the one you
> > specify via -e.
> > The developers have provided a very useful resource for answering such
> > questions, which is included in most methods of distributing rsync.
> Here's
> > a relevant excerpt:
> >
> > There are six different ways of using rsync. They are:
> >
> > SunOS 5.7 Last change: 29 May 2001 1
> >
> > User Commands rsync(1)
> >
> > o for copying local files. This is invoked when neither
> > source nor destination path contains a : separator
> >
> > o for copying from the local machine to a remote machine
> > using a remote shell program as the transport (such as
> > rsh or ssh). This is invoked when the destination path
> > contains a single : separator.
> >
> > o for copying from a remote machine to the local machine
> > using a remote shell program. This is invoked when the
> > source contains a : separator.
> >
> > o for copying from a remote rsync server to the local
> > machine. This is invoked when the source path contains
> > a :: separator or a rsync:// URL.
> >
> > o for copying from the local machine to a remote rsync
> > server. This is invoked when the destination path con-
> > tains a :: separator.
> >
> > o for listing files on a remote machine. This is done the
> > same way as rsync transfers except that you leave off
> > the local destination.
> >
> > Note that in all cases (other than listing) at least one of
> > the source and destination paths must be local.
> >
> > SETUP
> > See the file README for installation instructions.
> >
> > Tim Conway
> > tim.conway at philips.com
> > 303.682.4917
> > Philips Semiconductor - Longmont TC
> > 1880 Industrial Circle, Suite D
> > Longmont, CO 80501
> > Available via SameTime Connect within Philips, n9hmg on AIM
> > perl -e 'print pack(nnnnnnnnnnnn,
> > 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
> > ".\n" '
> > "There are some who call me.... Tim?"
> >
> > Jack Khoo <jackkhoo at xybase.com>
> > Sent by: rsync-admin at lists.samba.org
> > 04/14/2002 10:38 PM
> >
> >
> > To: rsync at samba.org
> > cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
> > Subject: Update: WARNING: --rsh or -e option ignored when
> connecting to rsync
> > daemon]
> > Classification:
> >
> > UPDATE
> >
> > i able to ssh between this 2 remote server, below is the extra info
> >
> > rsync -avue ssh . username at hostname::sharefolder
> > WARNING: --rsh or -e option ignored when connecting to rsync daemon
> > rsync: failed to connect to HOSTNAME: Connection timed out
> > rsync error: error in socket IO (code 10) at clientserver.c(89)
> >
> > ----- Message from Jack Khoo <jackkhoo at xybase.com> on Mon, 15 Apr 2002
> > 12:22:49 +0800 -----
> > To:
> > rsync at samba.org
> > Subject:
> > WARNING: --rsh or -e option ignored when connecting to rsync daemon
> > i faced a problem as below :
> >
> > WARNING: --rsh or -e option ignored when connecting to rsync daemon
> >
> > when i trying to sync between 2 remote server, Sun 2.8 and AIX 4.3.3
> >
> > Sun Rsync - 2.5.4
> > AIX Rsync - 2.4.5
> >
> > isn't ok for this 2 different version of rsync to communicate each
> > others,
> >
> > don't it affect by ssh daemon/version as well
> >
> > kindly advise
> >
> > --
> > To unsubscribe or change options:
> > http://lists.samba.org/mailman/listinfo/rsync
> > Before posting, read:
> http://www.tuxedo.org/~esr/faqs/smart-questions.html
>
> --
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
More information about the rsync
mailing list