Sorry to top post and reply to myself. After a bit of debugging the
RsyncP.pm script, I found that it was puking on some blank lines from the
server. I added the following to sub serverService just below $line =
$rs->getLine;
# Set a counter so I don't spin in hell for ever
my $cnt = 0;
while ($line eq '' && $cnt < 3){
$line = $rs->getLine;
$cnt++;
}
And no more auth required but service open/insecure. As I type there is a
1gig backup taking place from this host/module.
Of course the question still remains as to why this was taking place, issue
with RsycnP or a protocol difference with later versions of rsync it's self,
even though they agreed on version 28?
Rick
> -----Original Message-----
> From: Rick Cooper [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2008 7:21 AM
> To: 'Rob Owens'
> Subject: RE: [BackupPC-users] Ryncd issues
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On
> > Behalf Of Rob Owens
> > Sent: Tuesday, June 24, 2008 7:08 AM
> > Cc: Backuppc-Users
> > Subject: Re: [BackupPC-users] Ryncd issues
> >
> > I'd try commenting out the "hosts allow" line, just to
> > eliminate it as a
> > possibility.
>
> Even though the hosts allow is a security feature, I
> commented it out and have exactly the same result. I wish
> the author of File::RsyncP was able to tell me what on earth
> is triggering that message.
>
> Rick
>
>
> >
> > -Rob
> >
> > Rick Cooper wrote:
> > > I am trying to perform a backup using rsyncd
> > > The host to be backup up resides on a remote network
> > connected via ipsec
> > > tunnel
> > >
> > > The client and host are both running rsync version 3.0.2
> > protocol version
> > > 30
> > >
> > > The daemon (remote to be backed up) set up is
> > >
> > > /etc/rsyncd.secrets
> > >
> > > -rw-r----- 1 root root 33 Jun 23 17:02 /etc/rsyncd.secrets
> > > Contents:
> > > backuppc:password
> > >
> > > Rsyncd.conf:
> > >
> > > [BackupPC]
> > > comment = BackupPC Data Directory
> > > path = /data
> > > read only = yes
> > > secrets file = /etc/rsyncd.secrets
> > > hosts allow = 192.168.1.0/24
> > > auth users = backuppc
> > >
> > > The host config relating to this host xfers
> > >
> > > $Conf{RsyncShareName} = [
> > > 'BackupPC'
> > > ];
> > >
> > > $Conf{RsyncdAuthRequired} = '1';
> > > $Conf{RsyncdPasswd} = 'password';
> > > $Conf{RsyncdUserName} = 'backuppc';
> > >
> > > The error that BackupPC gives is:
> > >
> > > full backup started for directory BackupPC
> > > Connected to dfnsrv01:873, remote version 30
> > > Negotiated protocol version 28
> > > Error connecting to module BackupPC at dfnsrv01:873: auth
> > required, but
> > > service BackupPC is open/insecure
> > > Got fatal error during xfer (auth required, but service
> BackupPC is
> > > open/insecure)
> > > Backup aborted (auth required, but service BackupPC is
> > open/insecure)
> > > Not saving this as a partial backup since it has fewer
> > files than the prior
> > > one (got 0 and 0 files versus 0)
> > >
> > > The error that the remote rsync daemon gives is
> > > Jun 23 19:17:38 dfnsrv01 rsyncd[25783]: connect from srv2
> > (192.168.1.1)
> > > Jun 23 19:17:43 dfnsrv01 rsyncd[25783]: rsync: read error:
> > Connection reset
> > > by peer (104)
> > > Jun 23 19:17:43 dfnsrv01 rsyncd[25783]: rsync error: error
> > in rsync protocol
> > > data stream (code 12) at io.c(794) [receiver=3.0.2]
> > >
> > >
> > > If I set both sides so they do not require authentication
> > BackupPC gives
> > > this error:
> > >
> > > 2008-06-23 19:00:32 full backup started for directory BackupPC
> > > 2008-06-23 19:00:32 Got fatal error during xfer (auth
> > required, but service
> > > BackupPC is open/insecure)
> > > 2008-06-23 19:00:37 Backup aborted (auth required, but
> > service BackupPC is
> > > open/insecure)
> > > 2008-06-23 19:01:06 full backup started for directory BackupPC
> > > 2008-06-23 19:01:06 Got fatal error during xfer
> > (unexpected response: '')
> > > 2008-06-23 19:01:11 Backup aborted (unexpected response: '')
> > >
> > >
> > > I have no idea where to go next. Clearly the rsync daemon
> > side is *not*
> > > open/insecure and suspect this might have something to do
> > with the fact that
> > > the last version of File::RsyncP is from November 2006 and
> > something has
> > > changed in the last *several* versions. Has anyone
> > encountered and found a
> > > way around this situation?
> > >
> > >
> > > Rick Cooper
> > >
> > >
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
