Re: [BackupPC-users] No files dumped for share for localhost

[RAKOTONDRAINIBE Harimino Lalatiana]

So I it seems hat the issue is about DNS lookup error: general failure when
I run ssh .

backuppc@backup:/ % /usr/bin/ssh -v -x -l backuppc localhost /bin/foobar
OpenSSH_7.2p2, OpenSSL 1.0.2k-freebsd  26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /home/backuppc/.ssh/id_rsa type 1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_rsa-cert type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_dsa type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_dsa-cert type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_ecdsa type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_ecdsa-cert type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_ed25519 type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /home/backuppc/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2 FreeBSD-20161230
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2
FreeBSD-20161230
debug1: match: OpenSSH_7.2 FreeBSD-20161230 pat OpenSSH* compat 0x0400
debug1: Authenticating to localhost:22 as 'backuppc'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha...@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC:
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC:
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:7IBJcg+uURyKkFB/9QuGJoU9tgm4m+gBiiVG44+nvyY
DNS lookup error: general failure
debug1: Host 'localhost' is known and matches the ECDSA host key.
debug1: Found key in /home/backuppc/.ssh/known_hosts:14
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_EXT_INFO received
debug1: Fssh_kex_input_ext_info: server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/backuppc/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/backuppc/.ssh/id_dsa
debug1: Trying private key: /home/backuppc/.ssh/id_ecdsa
debug1: Trying private key: /home/backuppc/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).

But it's a bit confusing because as I understand the server connect to
himself when it try to backup the localhost so when the connection can't be
set up ?

Regards,

Hari

2018-01-30 9:28 GMT+03:00 Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net>:

> Please remove the -q option.  Try adding -v (or even -vv) to the ssh args.
>
> What happens if you run some other command, eg, /bin/date?  What happens
> if you run some path that doesn't exist, eg, /bin/foobar.
>
> Examples:
>
> /usr/bin/ssh -v -x -l backuppc localhost /bin/date
> /usr/bin/ssh -v -x -l backuppc localhost /bin/foobar
>
>
> Craig
>
>
> On Mon, Jan 29, 2018 at 10:14 PM, RAKOTONDRAINIBE Harimino Lalatiana <
> mimino...@gmail.com> wrote:
>
>> Hi Alexander, Graig
>>
>> I installed the backuppc4 and p5-BackupPC-XS via ports. And I reinstalled
>> the rsync-bpc via ports.
>>
>> Anyway their still no output for the command below and yes it exit
>> immediately:
>>
>> backuppc@backup:/ % /usr/bin/ssh -q -x -l backuppc localhost
>> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
>>
>> Regards,
>>
>> Hari
>>
>>
>> 2018-01-29 22:05 GMT+03:00 Alexander Moisseev via BackupPC-users <
>> backuppc-users@lists.sourceforge.net>:
>>
>>> On 1/29/2018 2:53 PM, RAKOTONDRAINIBE Harimino Lalatiana wrote:
>>>
 The backuppc is installed in freebsd 11.1
 All hosts seems to be backuppc well except the localhost.
 I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
 current git .

>>>
>>> BTW, You could use ports:
>>>
>>> net/rsync-bpc
>>> sysutils/backuppc4
>>> sysutils/p5-BackupPC-XS
>>>
>>>
>>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> BackupPC-users mailing list
>>> BackupPC-users@lists.sourceforge.net
>>> List:

Re: [BackupPC-users] No files dumped for share for localhost

[Craig Barratt via BackupPC-users]

Please remove the -q option.  Try adding -v (or even -vv) to the ssh args.

What happens if you run some other command, eg, /bin/date?  What happens if
you run some path that doesn't exist, eg, /bin/foobar.

Examples:

/usr/bin/ssh -v -x -l backuppc localhost /bin/date
/usr/bin/ssh -v -x -l backuppc localhost /bin/foobar


Craig


On Mon, Jan 29, 2018 at 10:14 PM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi Alexander, Graig
>
> I installed the backuppc4 and p5-BackupPC-XS via ports. And I reinstalled
> the rsync-bpc via ports.
>
> Anyway their still no output for the command below and yes it exit
> immediately:
>
> backuppc@backup:/ % /usr/bin/ssh -q -x -l backuppc localhost
> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
>
> Regards,
>
> Hari
>
>
> 2018-01-29 22:05 GMT+03:00 Alexander Moisseev via BackupPC-users <
> backuppc-users@lists.sourceforge.net>:
>
>> On 1/29/2018 2:53 PM, RAKOTONDRAINIBE Harimino Lalatiana wrote:
>>
>>> The backuppc is installed in freebsd 11.1
>>> All hosts seems to be backuppc well except the localhost.
>>> I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
>>> current git .
>>>
>>
>> BTW, You could use ports:
>>
>> net/rsync-bpc
>> sysutils/backuppc4
>> sysutils/p5-BackupPC-XS
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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/
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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/

Re: [BackupPC-users] No files dumped for share for localhost

[RAKOTONDRAINIBE Harimino Lalatiana]

Hi Alexander, Graig

I installed the backuppc4 and p5-BackupPC-XS via ports. And I reinstalled
the rsync-bpc via ports.

Anyway their still no output for the command below and yes it exit
immediately:

backuppc@backup:/ % /usr/bin/ssh -q -x -l backuppc localhost
/usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf

Regards,

Hari


2018-01-29 22:05 GMT+03:00 Alexander Moisseev via BackupPC-users <
backuppc-users@lists.sourceforge.net>:

> On 1/29/2018 2:53 PM, RAKOTONDRAINIBE Harimino Lalatiana wrote:
>
>> The backuppc is installed in freebsd 11.1
>> All hosts seems to be backuppc well except the localhost.
>> I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
>> current git .
>>
>
> BTW, You could use ports:
>
> net/rsync-bpc
> sysutils/backuppc4
> sysutils/p5-BackupPC-XS
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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/

Re: [BackupPC-users] No files dumped for share for localhost

[Alexander Moisseev via BackupPC-users]

On 1/29/2018 2:53 PM, RAKOTONDRAINIBE Harimino Lalatiana wrote:

The backuppc is installed in freebsd 11.1
All hosts seems to be backuppc well except the localhost.
I did like it was said in the forum so  I build rsync-bpc 3.0.9 from current 
git .


BTW, You could use ports:

net/rsync-bpc
sysutils/backuppc4
sysutils/p5-BackupPC-XS

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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/

Re: [BackupPC-users] No files dumped for share for localhost

[Craig Barratt via BackupPC-users]

What happens when you run this command as the backuppc user?

su backuppc
/usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync --server
--sender -svvlHogDtpre.iLsf


Is there any output?  Does it exit immediately?

Craig

On Mon, Jan 29, 2018 at 3:53 AM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi everyone,
>
> After an issues with backuppc v3 , I upgraded to v4.1.4.
>
> The backuppc is installed in freebsd 11.1
>
> All hosts seems to be backuppc well except the localhost.
>
> I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
> current git .
>
> In addition to that I run :
>
> /usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync
>
> Which don't give any output.
>
> I also run the dump manually and the out is :
>
> backuppc@backup:/ % /usr/local/bin/BackupPC_dump -v -i localhost
> Backup type: type = incr, needs_full = 1, needs_incr = 1, lastFullTime =
> 1512601200, opts{f} = , opts{i} = 1, opts{F} =
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> CheckHostAlive: ran '/sbin/ping -c 1 localhost'; returning 0.020
> XferLOG file /var/db/BackupPC/pc/localhost/XferLOG.153 created 2018-01-29
> 14:47:18
> Backup prep: type = incr, case = 6, inPlace = 1, doDuplicate = 0,
> newBkupNum = 153, newBkupIdx = 3, lastBkupNum = , lastBkupIdx =  (FillCycle
> = 0, noFillCnt = 0)
> __bpc_progress_state__ backup share "/"
> Running: /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc --bpc-top-dir
> /var/db/BackupPC --bpc-host-name localhost --bpc-share-name /
> --bpc-bkup-num 153 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1
> --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 530710 --bpc-attrib-new
> --bpc-log-level 5 -e /usr/bin/ssh\ -q\ -x\ -l\ backuppc
> --rsync-path=/usr/local/bin/rsync --super --recursive --protect-args
> --numeric-ids --perms --owner --group -D --times --links --hard-links
> --delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\
> %8U,%8G\ %9l\ %f%L --stats -vv --timeout=72000 --exclude=/dev
> --exclude=/media --exclude=/mnt --exclude=/nonexistent --exclude=/proc
> --exclude=/sys --exclude=/tmp --exclude=/usr/src/sys --exclude=/var/run
> --exclude=/var/tmp --exclude=/var/db/BackupPC localhost:/ /
> incr backup started for directory /
> started incr dump, share=/
> Xfer PIDs are now 39051
> xferPids 39051
> This is the rsync child about to exec /home/backuppc/rsyns-git/
> rsync-bpc/rsync_bpc
> cmdExecOrEval: about to exec /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
> --bpc-top-dir /var/db/BackupPC --bpc-host-name localhost --bpc-share-name /
> --bpc-bkup-num 153 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1
> --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 530710 --bpc-attrib-new
> --bpc-log-level 5 -e /usr/bin/ssh\ -q\ -x\ -l\ backuppc
> --rsync-path=/usr/local/bin/rsync --super --recursive --protect-args
> --numeric-ids --perms --owner --group -D --times --links --hard-links
> --delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\
> %8U,%8G\ %9l\ %f%L --stats -vv --timeout=72000 --exclude=/dev
> --exclude=/media --exclude=/mnt --exclude=/nonexistent --exclude=/proc
> --exclude=/sys --exclude=/tmp --exclude=/usr/src/sys --exclude=/var/run
> --exclude=/var/tmp --exclude=/var/db/BackupPC localhost:/ /
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
> = 0
> opening connection using: /usr/bin/ssh -q -x -l backuppc localhost
> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
> protected args: --timeout=72000 --numeric-ids . /
> rsync_bpc: connection unexpectedly closed (0 bytes received so far)
> [Receiver]
> bpc_sysCall_cleanup: doneInit = 1
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal,
> 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 530710 inode
> Parsing done: nFilesTotal = 0
> rsync error: error in rsync protocol data stream (code 12) at io.c(629)
> [Receiver=3.0.9.11]
> rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync
> protocol data stream (code 12) at io.c(629) [Receiver=3.0.9.11])
> Xfer PIDs are now
> xferPids
> __bpc_progress_state__ post-cmd
> Executing DumpPostUserCmd: /var/db/BackupPC/mailadmin.sh 0 localhost
> cmdSystemOrEval: about to system /var/db/BackupPC/mailadmin.sh 0 localhost
> send-mail: Cannot open smtp.irenala.edu.mg:25
> Got fatal error during xfer (rsync error: error in rsync protocol data
> stream (code 12) at io.c(629) [Receiver=3.0.9.11])
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> CheckHostAlive: ran '/sbin/ping -c 1 localhost'; returning 0.070
> Backup aborted (rsync error: error in rsync protocol data stream (code 12)
> at io.c(629) [Receiver=3.0.9.11])
> __bpc_progress_state__ fail cleanup
> BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace =
> 1, lastBkupNum =
> BackupFailCleanup: inPlace with no new files... no cleanup
> __bpc_progress_state__ 

[BackupPC-users] No files dumped for share for localhost

[RAKOTONDRAINIBE Harimino Lalatiana]

Hi everyone,

After an issues with backuppc v3 , I upgraded to v4.1.4.

The backuppc is installed in freebsd 11.1

All hosts seems to be backuppc well except the localhost.

I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
current git .

In addition to that I run :

/usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync

Which don't give any output.

I also run the dump manually and the out is :

backuppc@backup:/ % /usr/local/bin/BackupPC_dump -v -i localhost
Backup type: type = incr, needs_full = 1, needs_incr = 1, lastFullTime =
1512601200, opts{f} = , opts{i} = 1, opts{F} =
cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
CheckHostAlive: ran '/sbin/ping -c 1 localhost'; returning 0.020
XferLOG file /var/db/BackupPC/pc/localhost/XferLOG.153 created 2018-01-29
14:47:18
Backup prep: type = incr, case = 6, inPlace = 1, doDuplicate = 0,
newBkupNum = 153, newBkupIdx = 3, lastBkupNum = , lastBkupIdx =  (FillCycle
= 0, noFillCnt = 0)
__bpc_progress_state__ backup share "/"
Running: /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc --bpc-top-dir
/var/db/BackupPC --bpc-host-name localhost --bpc-share-name /
--bpc-bkup-num 153 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1
--bpc-bkup-prevcomp -1 --bpc-bkup-inode0 530710 --bpc-attrib-new
--bpc-log-level 5 -e /usr/bin/ssh\ -q\ -x\ -l\ backuppc
--rsync-path=/usr/local/bin/rsync --super --recursive --protect-args
--numeric-ids --perms --owner --group -D --times --links --hard-links
--delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\
%8U,%8G\ %9l\ %f%L --stats -vv --timeout=72000 --exclude=/dev
--exclude=/media --exclude=/mnt --exclude=/nonexistent --exclude=/proc
--exclude=/sys --exclude=/tmp --exclude=/usr/src/sys --exclude=/var/run
--exclude=/var/tmp --exclude=/var/db/BackupPC localhost:/ /
incr backup started for directory /
started incr dump, share=/
Xfer PIDs are now 39051
xferPids 39051
This is the rsync child about to exec
/home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
cmdExecOrEval: about to exec /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
--bpc-top-dir /var/db/BackupPC --bpc-host-name localhost --bpc-share-name /
--bpc-bkup-num 153 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1
--bpc-bkup-prevcomp -1 --bpc-bkup-inode0 530710 --bpc-attrib-new
--bpc-log-level 5 -e /usr/bin/ssh\ -q\ -x\ -l\ backuppc
--rsync-path=/usr/local/bin/rsync --super --recursive --protect-args
--numeric-ids --perms --owner --group -D --times --links --hard-links
--delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\
%8U,%8G\ %9l\ %f%L --stats -vv --timeout=72000 --exclude=/dev
--exclude=/media --exclude=/mnt --exclude=/nonexistent --exclude=/proc
--exclude=/sys --exclude=/tmp --exclude=/usr/src/sys --exclude=/var/run
--exclude=/var/tmp --exclude=/var/db/BackupPC localhost:/ /
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
= 0
opening connection using: /usr/bin/ssh -q -x -l backuppc localhost
/usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
protected args: --timeout=72000 --numeric-ids . /
rsync_bpc: connection unexpectedly closed (0 bytes received so far)
[Receiver]
bpc_sysCall_cleanup: doneInit = 1
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 530710 inode
Parsing done: nFilesTotal = 0
rsync error: error in rsync protocol data stream (code 12) at io.c(629)
[Receiver=3.0.9.11]
rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync
protocol data stream (code 12) at io.c(629) [Receiver=3.0.9.11])
Xfer PIDs are now
xferPids
__bpc_progress_state__ post-cmd
Executing DumpPostUserCmd: /var/db/BackupPC/mailadmin.sh 0 localhost
cmdSystemOrEval: about to system /var/db/BackupPC/mailadmin.sh 0 localhost
send-mail: Cannot open smtp.irenala.edu.mg:25
Got fatal error during xfer (rsync error: error in rsync protocol data
stream (code 12) at io.c(629) [Receiver=3.0.9.11])
cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
CheckHostAlive: ran '/sbin/ping -c 1 localhost'; returning 0.070
Backup aborted (rsync error: error in rsync protocol data stream (code 12)
at io.c(629) [Receiver=3.0.9.11])
__bpc_progress_state__ fail cleanup
BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace =
1, lastBkupNum =
BackupFailCleanup: inPlace with no new files... no cleanup
__bpc_progress_state__ fsck
Running BackupPC_refCountUpdate -h localhost -f on localhost
cmdSystemOrEval: about to system /usr/local/bin/BackupPC_refCountUpdate -h
localhost -f
Xfer PIDs are now 39069
xferPids 39069
BackupPC_refCountUpdate: host localhost #153: gotFsck = 1, gotDelta = ,
gotPoolCnt = 1, gotNoPoolCntOk =
BackupPC_refCountUpdate: processing host localhost #153 (fsck = 1)
__bpc_progress_state__ refCnt #153
__bpc_progress_state__ cntUpdate #153
BackupPC_refCountUpdate: processing host localhost #153 deltaFile

Re: [BackupPC-users] backup failing with "No files dumped for share /"

[RAKOTONDRAINIBE Harimino Lalatiana]

Hi Graig,

Nothing happen after I run the command, I will open a new thread then to
avoid confusion.

Thank you

Regards,

Hari

2018-01-27 20:27 GMT+03:00 Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net>:

> Hari,
>
> This doesn't look related to the original thread.  For some reason
> rsync_bpc's connection to the client is closed before any files get
> transferred.
>
> What happens when you run this comment as the backuppc user:
>
> /usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync
>
> Craig
>
> On Fri, Jan 26, 2018 at 5:01 AM, RAKOTONDRAINIBE Harimino Lalatiana <
> mimino...@gmail.com> wrote:
>
>> Hi everyone,
>>
>> I encounter the same issue now when I backup my localhost. I had a
>> problem after an OS upgrade and after some change and an upgrade in 4.1.4,
>> the issue has been resolved for all the hosts except for my localhost.
>>
>> I already tried all that was said earlier in the forum by  building
>> rsync-bpc with the current git and increasing the xferlog
>>
>> The error in xferlog :
>>
>> This is the rsync child about to exec 
>> /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
>> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = >> 0
>> opening connection using: /usr/bin/ssh -q -x -l backuppc localhost 
>> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
>> protected args: --timeout=72000 --numeric-ids . /
>> rsync_bpc: connection unexpectedly closed (0 bytes received so far) 
>> [Receiver]
>> bpc_sysCall_cleanup: doneInit = 1
>> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
>> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 530710 inode
>> Parsing done: nFilesTotal = 0
>> rsync error: error in rsync protocol data stream (code 12) at io.c(629) 
>> [Receiver=3.0.9.11]
>> rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync 
>> protocol data stream (code 12) at io.c(629) [Receiver=3.0.9.11])
>> Xfer PIDs are now
>> Executing DumpPostUserCmd: /var/db/BackupPC/mailadmin.sh 0 localhost
>> Got fatal error during xfer (rsync error: error in rsync protocol data 
>> stream (code 12) at io.c(629) [Receiver=3.0.9.11])
>> Backup aborted (rsync error: error in rsync protocol data stream (code 12) 
>> at io.c(629) [Receiver=3.0.9.11])
>> BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace = 
>> 1, lastBkupNum =
>> BackupFailCleanup: inPlace with no new files... no cleanup
>> Running BackupPC_refCountUpdate -h localhost -f on localhost
>> Xfer PIDs are now 17115
>> BackupPC_refCountUpdate: host localhost #153: gotFsck = 1, gotDelta = , 
>> gotPoolCnt = 1, gotNoPoolCntOk =
>> BackupPC_refCountUpdate: processing host localhost #153 (fsck = 1)
>> BackupPC_refCountUpdate: processing host localhost #153 deltaFile 
>> /var/db/BackupPC/pc/localhost/153/refCnt/poolCntDelta_0_0_0_17115 with 
>> 510160 entries
>> BackupPC_refCountUpdate: computing totals for host localhost
>> BackupPC_refCountUpdate: host localhost got 0 errors (took 5 secs)
>> BackupPC_refCountUpdate total errors: 0
>> Xfer PIDs are now
>> Finished BackupPC_refCountUpdate (running time: 5 sec)
>> Xfer PIDs are now
>>
>> As I understand it's a problem with rsync-bpc but I didn't find any solution 
>> to resolve it.
>>
>> Thank you,
>>
>> Hari
>>
>>
>>
>>
>> 2018-01-24 14:16 GMT+03:00 Joel Uckelman :
>>
>>> Thus spake Craig Barratt via BackupPC-users:
>>> > Joel,
>>> >
>>> > It's hard to tell from the log.  However, one thing worth trying is to
>>> > build rsync-bpc 3.0.9 from current git, since there was a bug I fixed
>>> last
>>> > week that could be related to this:
>>> >
>>> > mkdir somewhere
>>> > cd somewhere
>>> > git clone https://github.com/backuppc/rsync-bpc
>>> > cd rsync-bpc
>>> > git checkout 3.0.9
>>> >
>>> > ./configure
>>> >
>>> > make
>>> >
>>> > Then set $Conf{RsyncBackupPCPath} to the new rysnc_bpc executable (ie:
>>> > /path/to/somewhere/rsync-bpc/rsync_bpc) and try running the backup
>>> again.
>>> >
>>> > If that still fails, the next steps are to increase XferLogLevel (eg,
>>> to 5
>>> > or 6), and add -vv to RsyncArgsExtra and send the log file.
>>> >
>>> > Craig
>>> >
>>>
>>> I had a complete successful backup with the patched rsync-bpc. I get
>>> a bunch of these (~50) in the log now:
>>>
>>> G bpc_read: read past EOF; readSize = 262101, posn = 43, fileSize = 43,
>>> bufferSize = 8388608
>>> G bpc_read: read past EOF; readSize = 262144, posn = 262144, fileSize =
>>> 43, bufferSize = 8388608
>>> G bpc_read: read past EOF; readSize = 262144, posn = 524288, fileSize =
>>> 43, bufferSize = 8388608
>>>
>>> But the backup appears to have been successful. Thanks!
>>>
>>> --
>>> J.
>>>
>>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> BackupPC-users 

Re: [BackupPC-users] Handle Backup as inconsistent on xfer error

[Zielke, Julian, NLI]

Alex,

yes I understand your points and they may apply in most backup scenarios. 
However, in my case it's a little bit different:

I'm saving lucene indices, which currently rely on results of a postgres 
database process. The problem with lucene is that a partitial backup of an 
index will
make the segments-file being incompatible with the rest of the files because of 
the segments pointing to nowhere or non-existent files, because
lucene first writes data to it's data-segments and in the end updates the 
segments-catalogue. So having a partitial backup is the same like a corrupted 
backup.

We have the ability to restore a consistnet index and later restore the missing 
part from the database tables so we're always able to restore data up to date.
Also we're constantly monitoring every backup through some post-share / 
post-user scripts, hence we'll be notified immediately when such an xfer error 
occours.
Normally they shouldn't because the index is configured to be in pause state 
during backup times so this xfer error abort will let us know if the index 
interfered with the
backup somehow.

Talking about the point on not saving the rest of the archives: There is afaik 
no current way to tell BackuPC to stop the backup on this share, execute 
post-share using xferOK = 0 and continue
with the rest of the backups. So we'll keep it that way. Maybe this could be a 
nice feature implementation to skip a share on xfer errors and return xferOK=0. 
This would be a perfect way to have
a solution of partitial backups AND notification in both ways.

- Julian

-Ursprüngliche Nachricht-
Von: Alexander Moisseev via BackupPC-users 
[mailto:backuppc-users@lists.sourceforge.net] 
Gesendet: Sonntag, 28. Januar 2018 16:58
An: General list for user discussion, questions and support 

Cc: Alexander Moisseev 
Betreff: Re: [BackupPC-users] Handle Backup as inconsistent on xfer error

On 1/26/2018 5:31 PM, Zielke, Julian, NLI wrote:
> It will be marked as partial but not continuing and/or doing rotation. 
> Also the xfer status won't be 1, because there were actual problems 
> saving all files within the share. This is just to prevent BackupPC from 
> running backups with xfer errors and doing rotation while some files in all 
> series always were open during backup.
> 

Julian, If I understood you correctly, you are trying to solve the following 
problem:
If xfer errors occurred during a backup (files were open or whatever), the 
backup is inconsistent as it misses some files.
In current implementation such a backup is considered successful despite xfer 
errors.
The expiration algorithm dosen't take xfer errors in account as well.
Here is a problem: under certain circumstances BackupPC expiration can leave 
errored backups, but expire consistent ones, so we will be unable to restore 
some files.

That is the reason why I do daily checks for xfer errors and remove backups 
with xfer errors.

Sure, the patch you are proposing will do it automatically, but it seem not a 
good solution to me.
What if something happened with the host's data? In many cases a recent partial 
backup is better than nothing. But you've aborted it!
More over you haven't saved the rest of shares on this host!!! 
https://github.com/backuppc/backuppc/blob/master/bin/BackupPC_dump#L1230
If some files always are open during backup, every backup will be aborted, so 
you will end up with no backups at all.

If we mark the backup as partial instead of aborting it, the partial backup 
will be removed when the next successful backup completes, or if another full 
backup fails resulting in a newer partial backup.
Advantages: files from partial backup can be restored, on the next backup we 
don't need to retransfer files already in the partial backup (for rsync, not 
for tar).

The situation when some files always are open during backup should be avoided, 
in general. In case if there are just a few files and they are always the same, 
it is probably a good idea to create an exclusion list. So if all xfer errors 
happen when attempting to transfer files that are in the exclusion list, do not 
mark that backup as partial.

--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
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/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list