Hi,
Johan Ehnberg wrote on 2009-04-08 15:49:30 +0300 [Re: [BackupPC-users] Here my
log]:
> [...]
> SSH is backgrounded with the -f switch.
ah, didn't know that one, but it's just what is needed here, obviously.
> [...]
> >- The script which starts ssh (or, equivale
Boniforti Flavio wrote:
>>> What should I do?
>> Set the value correctly:
>> # Whether authentication is mandatory when connecting to the
>> client's # rsyncd. By default this is on, ensuring that
>> BackupPC will refuse to # connect to an rsyncd on the client
>> that is not password protected.
> The tunnel is working well now. I bet you'll find answers
> here or by googling for more. This may have to do with the
> variant of rsync on the client.
>
> http://backuppc.wiki.sourceforge.net/ErrorMessages
> http://www.mail-archive.com/backuppc-us...@lists.sourceforge.n
> et/msg13703.html
> > What should I do?
>
> Set the value correctly:
> # Whether authentication is mandatory when connecting to the
> client's # rsyncd. By default this is on, ensuring that
> BackupPC will refuse to # connect to an rsyncd on the client
> that is not password protected.
> # Turn off at your own
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Boniforti Flavio wrote:
>>> Still, there remains "auth required, but service data is
>> open/insecure":
>>> to what does it refer?
>> I think that means backuppc had a password configured but the rsyncd
>> server didn't ask for it. You can test rsy
> > Still, there remains "auth required, but service data is
> open/insecure":
> > to what does it refer?
>
> I think that means backuppc had a password configured but the rsyncd
> server didn't ask for it. You can test rsyncd operation
> with command
> line rsync using '::' to separate th
(I invite Craig Barratt and any developer to check out my last paragraph
below.)
> it doesn't seem like ssh actually *is* backgrounded. I didn't read
> the tutorial and haven't played around with this, so I'm not quite
> sure *what* you would want to background to keep the tunnel open
> [long eno
Boniforti Flavio wrote:
> [cut]
>
>>> How do I debug this further?
>> For testing, you can remove the "1>/dev/null 2>/dev/null"
>> from the script to see the output of SSH. Note that the
>> backup will not proceed like this as SSH can't be
>> backgrounded without redirecting the output.
>> Yo
Boniforti Flavio wrote:
> [cut]
>
>>> How do I debug this further?
>> For testing, you can remove the "1>/dev/null 2>/dev/null"
>> from the script to see the output of SSH. Note that the
>> backup will not proceed like this as SSH can't be
>> backgrounded without redirecting the output.
>> You
[cut]
> > How do I debug this further?
>
> For testing, you can remove the "1>/dev/null 2>/dev/null"
> from the script to see the output of SSH. Note that the
> backup will not proceed like this as SSH can't be
> backgrounded without redirecting the output.
> You could perhaps also redirect i
Hi,
Johan Ehnberg wrote on 2009-04-08 13:32:23 +0300 [Re: [BackupPC-users] Here my
log]:
>
> [...]
> > I would like to get some more detailed log about the "DumpPreUserCmd"
> > (which reads: ssh $@ 1>/dev/null 2>/dev/null && echo "SSH started
>
> Executing DumpPreUserCmd: /var/lib/backuppc/tunnel.sh -fC
> administra...@mail.omv.ch -L 8874:127.0.0.1:873 sleep 20
The SSH tunnel is not working yet.
> full backup started for directory data
> Error connecting to rsync daemon at localhost:8874: inet connect:
> Connessione rifiutata
> Got fa
> because you are forwarding port 8874 on the BackupPC server
> to localhost:873 on the client host (that's the whole purpose
> of the ssh tunnel). So you need to make BackupPC connect to
> port 8874 on the BackupPC server in order to reach the
> client's rsyncd.
You're right, I just forgot h
Hi,
Boniforti Flavio wrote on 2009-04-08 10:13:41 +0200 [Re: [BackupPC-users] Here
my log]:
>
> > > Executing DumpPreUserCmd: /root/tunnel.sh -f administra...@mail...
> > > -L 8874:127.0.0.1:873 sleep 20
^
> [...]
> > Exactly. You need t
> > Executing DumpPreUserCmd: /root/tunnel.sh -f administra...@mail...
> > -L 8874:127.0.0.1:873 sleep 20
>
> First you have to make sure the SSH tunnel works with key
> based authentication (=no password but file) for the user
> running backuppc.
Damn! That part was missing, because actually
Boniforti Flavio wrote:
>> Hi again.
>>
>> You need to change the method from rsync to rsyncd.
>
> Well, I changed it now and here's what I got:
>
> Executing DumpPreUserCmd: /root/tunnel.sh -f administra...@mail...
> -L 8874:127.0.0.1:873 sleep 20
First you have to make sure the SSH tunnel work
16 matches
Mail list logo
