I'm running FreeBSD 4.6.2 on two different machines. Both machines have rync installed by way of the ports library, but one of them is running it as a server. I followed the directions in the man pages for running the server using inetd. Here is what happens: rsync rsync://myusername@10.0.0.8/ rsync: server sent "rysnc version 2.5.5 protocol version 26" rather than greeting rsync error: error starting client-server protocol (code 5) at main.c(923) I get that same error message any way that I try to access the server, even with a simple "rsync 10.0.0.8::" Has anyone seen a message like this before? Does it mean that I set something up wrong? I can post my rsyncd.conf contents if necessary. - Doug -------------- next part -------------- HTML attachment scrubbed and removed
tim.conway@philips.com
2002-Sep-06 14:39 UTC
error starting client-server protocol (code 5)
Yes, send the conf. It sounds like it's running, but has nothing to say.
Tim Conway
tim.conway@philips.com
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"
"Doug Schasteen" <dschast@escindex.com>
Sent by: rsync-admin@lists.samba.org
09/06/2002 08:10 AM
To: <rsync@lists.samba.org>
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: error starting client-server protocol (code 5)
Classification:
I'm running FreeBSD 4.6.2 on two different machines. Both machines have
rync installed by way of the ports library, but one of them is running it
as a server. I followed the directions in the man pages for running the
server using inetd.
Here is what happens:
rsync rsync://myusername@10.0.0.8/
rsync: server sent "rysnc version 2.5.5 protocol version 26" rather
than
greeting
rsync error: error starting client-server protocol (code 5) at main.c(923)
I get that same error message any way that I try to access the server,
even with a simple "rsync 10.0.0.8::"
Has anyone seen a message like this before? Does it mean that I set
something up wrong? I can post my rsyncd.conf contents if necessary.
- Doug
Ok, I played around with it some more and I found that if I run rsync as
a standalone daemon, it works fine. So it appears the problem I was
having was with inetd, specially my inetd.conf file. I?d still rather
run this thing through inetd so I?m going to keep trying to get this to
work. When I first put my rsync line into inetd.conf I was just
following the instructions in the man pages. But after looking it over,
the line I added is missing something at the end that the rest of the
inetd.conf lines have. Here is a sample taken from my inetd.conf
#shell stream tcp nowait root /usr/libexec/rshd rshd
#login stream tcp nowait root /usr/libexec/rlogind rlogind
#finger stream tcp nowait/3/10 nobody /usr/libexec/fingerd fingerd
-s
#exec stream tcp nowait root /usr/libexec/rexecd rexecd
#uucpd stream tcp nowait root /usr/libexec/uucpd uucpd
#nntp stream tcp nowait usenet /usr/libexec/nntpd nntpd
# Added by Doug
rsync stream tcp nowait root /usr/local/bin/rsync --daemon
#
As you can see, the rest of the inetd lines have a ?name? or something
after the path/command. The man pages didn?t say to put anything there,
but maybe I should put ?rsync? after -?daemon? If that?s not the problem
then I don't know what is.
Here is the contents of my /usr/local/etc/rsynd.conf file just in case.
------------------------------------------------------------------------
# rsyncd.conf configuration file
# GLOBAL OPTIONS
log file=/var/log/rsyncd.log
# MODULE OPTIONS
[www]
path = /www
use chroot = no
max connections = 4
auth users = rsync
hosts allow = 10.0.0.6
read only = yes
secrets file = /etc/.rs_sec
uid = nobody
gid = nogroup
transfer logging = yes
dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz
------------------------------------------------------------------------
- Doug
-----Original Message-----
From: rsync-admin@lists.samba.org [mailto:rsync-admin@lists.samba.org]
On Behalf Of Doug Schasteen
Sent: Friday, September 06, 2002 9:10 AM
To: rsync@lists.samba.org
Subject: error starting client-server protocol (code 5)
?
I?m running FreeBSD 4.6.2 on two different machines. Both machines have
rync installed by way of the ports library, but one of them is running
it as a server. I followed the directions in the man pages for running
the server using inetd.
?
Here is what happens:
?
rsync rsync://myusername@10.0.0.8/
?
rsync: server sent ?rysnc version 2.5.5 protocol version 26? rather than
greeting
rsync error: error starting client-server protocol (code 5) at
main.c(923)
?
?
I get that same error message any way that I try to access the server,
even with a simple ?rsync 10.0.0.8::?
?
Has anyone seen a message like this before? Does it mean that I set
something up wrong? I can post my rsyncd.conf contents if necessary.
?
?
- Doug
?
tim.conway@philips.com
2002-Sep-06 21:00 UTC
error starting client-server protocol (code 5)
get pid of inetd
kill -HUP that pid
some systems have handy killers, like killall on linux, and pkill on
solaris. be sure what it does. first time i tried to use killall on
solaris, i found that it wasn't what I expected.
Example:
CTools@willy
/users/Tools>ps -ef |grep inetd
root 194 1 0 Jun 06 ? 0:08 /usr/sbin/inetd -s
Tools 1893 2093 0 13:56:51 pts/7 0:00 grep inetd
Tools@willy
/users/Tools>kill -HUP 194
bash: kill: (194) - Not owner
Tools@willy
/users/Tools>
If I were root, that would have happenned.
Cool think about running your rsyncd out of inetd - you can make changes
to the rsyncd.conf any time you want, and they're active immediately.
Tim Conway
tim.conway@philips.com
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"
"Doug Schasteen" <dschast@escindex.com>
Sent by: rsync-admin@lists.samba.org
09/06/2002 09:40 AM
To: <rsync@lists.samba.org>
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: RE: error starting client-server protocol (code 5)
Classification:
I fixed it. I misread the man pages about the line to put in inetd.conf.
It DID tell me to put an rsyncd, but I didn't see it because it goes
BEFORE the --daemon. So for anyone in the future that has this same
problem (mistake), make sure you have the following line in your inetd,
WITH "rsyncd" BEFORE --daemon.
rsync stream tcp nowait root /usr/local/bin/rsync rsyncd
--daemon
Also, the man page tells me to send an HUP signal to inetd in order for
it to reread its configuration file. I don't know how to do that so I've
just been rebooting the server. Can anyone tell me how to send an HUP
signal?
- Doug
-----Original Message-----
From: rsync-admin@lists.samba.org [mailto:rsync-admin@lists.samba.org]
On Behalf Of Doug Schasteen
Sent: Friday, September 06, 2002 10:19 AM
To: rsync@lists.samba.org
Subject: RE: error starting client-server protocol (code 5)
Ok, I played around with it some more and I found that if I run rsync as
a standalone daemon, it works fine. So it appears the problem I was
having was with inetd, specially my inetd.conf file. I'd still rather
run this thing through inetd so I'm going to keep trying to get this to
work. When I first put my rsync line into inetd.conf I was just
following the instructions in the man pages. But after looking it over,
the line I added is missing something at the end that the rest of the
inetd.conf lines have. Here is a sample taken from my inetd.conf
#shell stream tcp nowait root /usr/libexec/rshd rshd
#login stream tcp nowait root /usr/libexec/rlogind rlogind
#finger stream tcp nowait/3/10 nobody /usr/libexec/fingerd fingerd
-s
#exec stream tcp nowait root /usr/libexec/rexecd rexecd
#uucpd stream tcp nowait root /usr/libexec/uucpd uucpd
#nntp stream tcp nowait usenet /usr/libexec/nntpd nntpd
# Added by Doug
rsync stream tcp nowait root /usr/local/bin/rsync --daemon
#
As you can see, the rest of the inetd lines have a "name" or something
after the path/command. The man pages didn't say to put anything there,
but maybe I should put "rsync" after -?daemon? If that's not the
problem
then I don't know what is.
Here is the contents of my /usr/local/etc/rsynd.conf file just in case.
------------------------------------------------------------------------
# rsyncd.conf configuration file
# GLOBAL OPTIONS
log file=/var/log/rsyncd.log
# MODULE OPTIONS
[www]
path = /www
use chroot = no
max connections = 4
auth users = rsync
hosts allow = 10.0.0.6
read only = yes
secrets file = /etc/.rs_sec
uid = nobody
gid = nogroup
transfer logging = yes
dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz
------------------------------------------------------------------------
- Doug
-----Original Message-----
From: rsync-admin@lists.samba.org [mailto:rsync-admin@lists.samba.org]
On Behalf Of Doug Schasteen
Sent: Friday, September 06, 2002 9:10 AM
To: rsync@lists.samba.org
Subject: error starting client-server protocol (code 5)
?
I'm running FreeBSD 4.6.2 on two different machines. Both machines have
rync installed by way of the ports library, but one of them is running
it as a server. I followed the directions in the man pages for running
the server using inetd.
?
Here is what happens:
?
rsync rsync://myusername@10.0.0.8/
?
rsync: server sent "rysnc version 2.5.5 protocol version 26" rather
than
greeting
rsync error: error starting client-server protocol (code 5) at
main.c(923)
?
?
I get that same error message any way that I try to access the server,
even with a simple "rsync 10.0.0.8::"
?
Has anyone seen a message like this before? Does it mean that I set
something up wrong? I can post my rsyncd.conf contents if necessary.
?
?
- Doug
?
--
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