/usr/share/BackupPC/bin/BackupPC_zcat
./attrib_d4c95788f1e2e67ddadd2e2ff26e0fc6 |wc
0 0 0
/usr/share/BackupPC/bin/BackupPC_attribPrint
/etc/alternatives/froot/fetc/falternatives/attrib
$attrib = {
};
All the attrib_ files that I find are 0 length.
On 1/9/21 10:42 PM, Craig Barratt wrote:
Pete,
Also, it would be good to see if that attrib file exists or has some
problem. What happens when you look in that directory on a full
(filled) backup? There should be a single file there with the name
attrib_DIGEST, where DIGEST is the 32 hex digits of the md5 digest.
What happens when you run these commands:
BackupPC_zcat DIGEST | wc
BackupPC_attribPrint path_to_attrib_file
Craig
On Sun, Jan 10, 2021 at 2:38 PM Craig Barratt
<cbarr...@users.sourceforge.net
<mailto:cbarr...@users.sourceforge.net>> wrote:
Peter,
Ok, those are all the latest versions. The next step is to
increase the debug level (eg, XferLogLevel to 7 and "-vv" to
rsync-bpc args) and send me a healthy portion of the log (eg, a
couple of thousand lines up until the error, and a few hundred
lines after the error).
Craig
On Sat, Jan 9, 2021 at 11:10 PM Pete Geenhuizen
<pgeenhui...@gmail.com <mailto:pgeenhui...@gmail.com>> wrote:
Craig,
Thanks for the response, these are the versions that I'm running
BackupPC4-4.4.0-2.el7.fws.x86_64
BackupPC-XS-0.62-2.el7.fws.x86_64
rsync-bpc-3.1.3.0-2.el7.fws.x86_64
Pete
On 1/8/21 9:08 PM, Craig Barratt wrote:
This should be fixed in the latest version of rsync-bpc.
What versions are you using (BackupPC, rsync-bpc and
backuppc-xs)?
Craig
On Sat, Jan 9, 2021 at 8:08 AM Pete Geenhuizen
<pgeenhui...@gmail.com <mailto:pgeenhui...@gmail.com>> wrote:
After a recent kernel update for Centos 7 I started
seeing the following
error on 2 hosts. I didn't give it much thought figuring
that it
probably would disappear when the next level 0 backup was
done, but nope
the error persists.
file has vanished:
"/etc/alternatives/froot/fetc/falternatives/attrib"
I have no idea how to resolve this error other than
simply deleting the
entire pool which seems like a pretty drastic way to
solve the problem.
So other than that is there a better way to handle this
problem?
Thanks
Pete
--
Unencumbered by the thought process.
-- Click and Clack the Tappet brothers
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
<mailto:BackupPC-users@lists.sourceforge.net>
List:
https://lists.sourceforge.net/lists/listinfo/backuppc-users
<https://lists.sourceforge.net/lists/listinfo/backuppc-users>
Wiki: https://github.com/backuppc/backuppc/wiki
<https://github.com/backuppc/backuppc/wiki>
Project: https://backuppc.github.io/backuppc/
<https://backuppc.github.io/backuppc/>
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
--
Unencumbered by the thought process.
-- Click and Clack the Tappet brothers
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
--
Unencumbered by the thought process.
-- Click and Clack the Tappet brothers
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
