@ERROR access denied

[Hardy Merrill]

If anyone else has any ideas, please chime in, as I'm
getting to the end of my list of things to try.  The
server is a SCO box and the client is a RH8 box.

Hugh, let's go back to the beginning - in your first
message, you stated:
-----------------------
In the above example "fisdev" is an SCO OSR5.0.4 system with rsync
V2.5.5 that I have downloaded as source and compiled. The daemon
was started from a root command line session. "pgiprd" is a RH8
system with rsync V2.5.5 as supplied by Red Hat. The daemon has
been started via xinetd.
-----------------------

You say that the deamon was started from a root command line
session, which to me means something like 'rsync --daemon'.
Then you say that the daemon was started via xinetd.  Which
way have you been using going through these iterations?

I forgot about your 'xinetd' statement, so in all my
testing on this I've been using a server started from
a root command line session - 'rsync --daemon'.  If you've
been running your server the same way (rsync --daemon), then
I'm about out of ideas - it works for me, but not for you.
I don't have a SCO box to test on.

Hardy

Hugh E Cruickshank [hugh at forsoft.com] wrote:
> Hi Hardy:
> 
> Well that seemed to do something. See my comments below.
> 
> Thanks, Hugh
> 
> -- 
> Hugh E Cruickshank, Forward Software, www.forward-software.com
> 
> From: Hardy Merrill Sent: Monday, July 07, 2003 12:38
> > 
> > 1) First, comment out both 'hosts allow' and 'auth users',
> > save it, kill and restart the rsync daemon, and try your
> > rsync again.  Hopefully that will work.
> 
> This made a small difference. The client no reports:
> 
>     building file list ... done                                            
>     rsync: connection unexpectedly closed (28 bytes read so far)           
>     rsync error: error in rsync protocol data stream (code 12) at 
>                  io.c(150)
> 
> The server log shows:
> 
>     2003/07/07 14:08:48 [3817] rsync to bak/ from pgiprd.forsoft.com
>                           (192.168.2.19)
> 
> And there is now a core file in the /bak directory.
> 
> > 
> > 2) Uncomment the 'hosts allow' line, save, kill and
> > restart daemon, and try rsync again - you will probably
> > get the same error you had before.  Your hosts allow line
> > looked like this:
> > 
> >   hosts allow	= fisdev pgiprd
> 
> Back to the original messages.
> 
> > 
> > 
> > 3) Now, change the values of that hosts allow to be complete
> > domain names, like 'fisdev.your.domain.com' and
> > 'pgiprd.your.domain.com' and see if that works now.
> > 
> > If you're not sure what the correct domain name is, on the
> > rsync server machine (this works on linux - not sure about
> > sco), do 'host fisdev' and see what it spits back.
> > 
> > According to 'man rsyncd.conf', you can use dotted quad ip
> > addresses, host names as determined by reverse dns, and
> > a few other things.
> 
> FQDN or IP address results in same messages as 1). 
> 
> > 
> > 4) Once you have 'hosts allow' working ok, then move on to
> > 'auth users' - my thought is that that will go smoothly once
> > the 'hosts allow' works right.
> 
> Since I did not get "hosts allow" working, I did not try anything 
> with "auth users". - HEC
> 
> > 
> > Again, please post your results.
> > 
> > -- 
> > Hardy Merrill
> > Red Hat, Inc.
> > 
> 
> [snip]
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.497 / Virus Database: 296 - Release Date: 03/07/04
> 
> -- 
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html