It should only affect rsync-bpc 3.1.3+. 3.1.2 and 3.0.9 use the original
style of handling long path and filename strings (just a large fixed size
is used).
Craig
On Tue, Jan 12, 2021 at 5:28 PM wrote:
> Craig Barratt via BackupPC-users wrote at about 15:32:27 +1100 on Tuesday,
> January 12,
Craig,
Thanks for looking into this been using BackupPC for many years and have
been very happy with the way it has performed.
I'm glad that the info I provided was of some use and hopefully it helps
in resolving the bug. Other than a bit annoying to see the error this
issue isn't affecting
Just posting this as a change in the format of the rsync server/sender
command tripped me up when I upgraded from rsync-bpc 3.0.9 to 3.1.2.
Specifically, I use my /etc/sudoers file to restrict the scope of the
backuppc and backuppc-client users as narrowly as possible.
For rsync_bpc < 3.1.x, the
So far, I have recompiled my x86 Ubuntu debian packages for 4.0.4 for
the Pi and it seems to be working.
I am using without email or apache for now...
Will keep you all updated if issues arrive...
backu...@kosowsky.org wrote at about 11:19:37 -0500 on Sunday, January 3, 2021:
> Has anybody had
On 13.1.2021 0.58, Adam Goryachev via BackupPC-users wrote:
On 13/1/21 09:21, Les Mikesell wrote:
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris
wrote:
Yeah, that “if you can interpret it” part gets really hard when it
looks like:
select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6],
BackupPC_refCountUpdate: host consult got 0 errors
(took 5 secs)
2021-01-12 01:03:38 Finished BackupPC_backupDelete, status = 0 (running
time: 6 sec)
2021-01-12 20:42:40 incr backup started for directory root (client path
/mnt/btrfs-root/@_snapshot-backuppc-20210112-204239)
2021-01-12 20:42:41 Got fatal
I tend to look in the top, if rsync is in progres, it its some CPU. It
does not, if it hangs.
Jan
On 1/12/21 6:04 PM, backu...@kosowsky.org wrote:
Short of waiting for 'rsync' to timeout, is there any way to see the
current status of an rsync backuppc backup, such as:
- Current average
Short of waiting for 'rsync' to timeout, is there any way to see the
current status of an rsync backuppc backup, such as:
- Current average 'transfer rate'
- Time last byte was transferred
Sometimes, especially when backing up laptops, it's hard to know if
the ssh connection has been disrupted
>>> I tend to look in the top, if rsync is in progres, it its some CPU. It
iotop would be another method
You could also try following the rsync process with strace
Doug
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:
While all of that is true, the answers so far still seem to be kind of like
looking at the parking lot outside the ice hockey arena. (Well, at least,
pre-Covid days anyways.) Is there a game going on or is it a pre-game show
listing players? Is the zamboni on the ice? Which game is in which
Any ideas? Sorry, it is bugging me... I tried many different things...
Command from the log below. Notice the lastBkupNUm = and last Bkup Idx =
It works on every other client. The bad think is, that this is the
biggest one...
Help would be much appreciated.
XferLOG file
On Tue, Jan 12, 2021 at 2:24 PM Greg Harris wrote:
>
I’ve yet to find a solid way to peer into the arena of BackupPC and
find answers to these types of questions.
Strace'ing the rsync process - possibly at both ends - gives you a
pretty detailed view of what is happening if you can interpret
Yeah, that “if you can interpret it” part gets really hard when it looks like:
select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6], left {tv_sec=59,
tv_usec=99})
read(6,
"\0\200\0\0\4\200\0\7\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
32768) = 27748
Scrolling at 32756
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris wrote:
>
> Yeah, that “if you can interpret it” part gets really hard when it looks like:
>
> select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6], left {tv_sec=59,
> tv_usec=99})
> read(6,
>
BackupPC_refCountUpdate: host consult got 0 errors
(took 5 secs)
2021-01-12 01:03:38 Finished BackupPC_backupDelete, status = 0 (running
time: 6 sec)
2021-01-12 20:42:40 incr backup started for directory root (client path
/mnt/btrfs-root/@_snapshot-backuppc-20210112-204239)
2021-01-12 20:42:41 Got fatal
On 13/1/21 09:21, Les Mikesell wrote:
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris wrote:
Yeah, that “if you can interpret it” part gets really hard when it looks like:
select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6], left {tv_sec=59,
tv_usec=99})
read(6,
Additionally, 'top' only tells you what is happening now (or in the
last few second sampling period).
What I really want to know is when was the last time data was
successfully transferred across the rsync/ssh pipe which generally
would signal that the backup is progressing vs. being stalled on a
17 matches
Mail list logo
