On Thursday 14 April 2005 21:07, Jan Harkes wrote:
> On Thu, Apr 14, 2005 at 11:45:37AM +0100, Alastair Johnson wrote:
> > On Tuesday 12 April 2005 20:40, Jan Harkes wrote:
> > > On Tue, Apr 12, 2005 at 11:42:36AM +0100, Alastair Johnson wrote:
> > > > 11:25:44 Fetch failed with RPC2_SEFAIL2 (F)
> > > >
> > > > updatefetch failed with RPC2_SEFAIL2 (F)
> > > > Could not fetch prot_users.cdb from SCM.  Make sure SCM is setup
> > > > correctly and then rerun /usr/sbin/vice-setup.
> > >
> > > Interesting, it already managed to fetch several files before it failed
> > > on this one. So I guess rpc2portmap and updatesrv are already running
> > > on the SCM.
> > >
> > > Does the file /vice/db/prot_users.cdb exist on the SCM?
> >
> > Manually running the updatefetch for db/prot_users.cdb fails as in
> > vice-setup.
>
> The other files that got fetched were all fairly small they probably got
> piggybacked on the RPC2 reply. My guess is that this was the first file
> that it tried to send with the SFTP side-effect, and this transfer is
> initiated by the server side of the connection. There might be some ip
> difference.
>
I didn't realise there were different transfer processes for different sizes 
of file. That gives me something to check in the morning, as I think I may 
still have a problem with some files not syncing. What might cause the 
piggybacking to work but the SFTP to fail? 

thanks for the input

Al