[BackupPC-users] Xfer errors and BackupPC_serverMesg
Dear List, is it possible to get a number of xfer errors by using BackupPC_serverMesg? "BackupPC_serverMesg status host(hostname)" doesn't provide this information. -- Karol Jędrzejczyk -- CONFIDENTIALITY NOTICE This message and any attachment is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, confidential, legally privileged or otherwise exempt from disclosure. The security and integrity of e-mails cannot be guaranteed. Any reply to this e-mail and any attachment received may be subject to Icotera monitoring. If you are not the named addressee, you are not authorized to use, distribute, copy or take any action in reliance on this message. The unauthorized use, disclosure, or copying of this communication, or any attachment, is strictly prohibited and may be unlawful. No waiver of confidentiality or any applicable privilege is intended by any mistransmission. If you have received this message in error, please notify the sender immediately by replying to this e-mail and delete all copies of this message and any attachments. ___ 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] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
On 2019-04-05 01:11, Daniel Berteaud wrote: Thanks for your response Michael, some comments inline Le 2019-04-04 23:22, Michael Stowe a écrit : On 2019-04-03 05:02, Daniel Berteaud wrote: First, as soon as there's a single error (most common are "file has vanished"), BackupPC reports 3 errors. Often, the backup reports an error count of 2, with these kind of errors : [ 213 lignes sautées ] rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022/_metadata" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023/_metadata" failed: No such file or directory (2) These files seem likely to have been updated or removed during the backup run. That directory contains bookmarks, cookies, extensions, and all kinds of things one might expect to change. My log snippets are just examples. I know this directory contains moving parts, I just try to understand why I do get this error while the mentionned dirs exist both on the source, and in the backup. To me this makes no sense. Either the dir doesn't exist during the scan, and rsync won't try to transfert it, or the dir exists and rsync transfert it, or the dir exists during the scan, but disapears before rsync transfert it. In this last case, I expect this kind of errors in the logs, but the directory should not exists in the backup. There are other possibilities: the directory is moved, or files are deleted and recreated (the latter is likely the case for Chrome's transient files.) Do you have any examples of files or directories which are not volatile? The symptoms here and the directory in question matches the behavior that is expected when backing up a Samba share used by Windows systems with access to a recycle bin. Windows will rename a file into the recycle bin, so you'll see this when you back up the original file -and- the recycle bin. I can't imagine why one would normally want to back up a recycle bin, since presumably one would have already backed up the file before it was deleted, so it's probably simplest just to exclude the bin from the backups. Alternatively, one can remove the bin (or access to it) so that Windows clients delete the original files, though that also makes backup of the recycle bin somewhat pointless. This was also just the first occurence of the error I found in my logs, I have the same errors for other files. Besides that, in this case, from BackupPC's POV, it doesn't matter if the directory is used a Recycle Bin for samba. It's just a directory where files which were previously elswhere have been moved. It could have been done by a human intervention in a FooBar directory. I'm just trying to understand what the error means You're correct; the error and BackupPC are telling you that the files moved during the backup. Perhaps I'm not understanding -- if the file has moved, and the error reflects that fact ... what are you trying to understand? ___ 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] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
Thanks for your response Michael, some comments inline Le 2019-04-04 23:22, Michael Stowe a écrit : > On 2019-04-03 05:02, Daniel Berteaud wrote: > > First, as soon as there's a single error (most common are "file has > vanished"), BackupPC reports 3 errors. > > Often, the backup reports an error count of 2, with these kind of > errors : > > [ 213 lignes sautées ] > rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022" > failed: No such file or directory (2) > rsync_bpc: stat > "/.config/google-chrome/CertificateRevocation/5022/_metadata" failed: > No such file or directory (2) > rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023" > failed: No such file or directory (2) > rsync_bpc: stat > "/.config/google-chrome/CertificateRevocation/5023/_metadata" failed: > No such file or directory (2) These files seem likely to have been updated or removed during the backup run. That directory contains bookmarks, cookies, extensions, and all kinds of things one might expect to change. My log snippets are just examples. I know this directory contains moving parts, I just try to understand why I do get this error while the mentionned dirs exist both on the source, and in the backup. To me this makes no sense. Either the dir doesn't exist during the scan, and rsync won't try to transfert it, or the dir exists and rsync transfert it, or the dir exists during the scan, but disapears before rsync transfert it. In this last case, I expect this kind of errors in the logs, but the directory should not exists in the backup. > The symptoms here and the directory in question matches the behavior that is expected when backing up a Samba share used by Windows systems with access to a recycle bin. Windows will rename a file into the recycle bin, so you'll see this when you back up the original file -and- the recycle bin. I can't imagine why one would normally want to back up a recycle bin, since presumably one would have already backed up the file before it was deleted, so it's probably simplest just to exclude the bin from the backups. Alternatively, one can remove the bin (or access to it) so that Windows clients delete the original files, though that also makes backup of the recycle bin somewhat pointless. This was also just the first occurence of the error I found in my logs, I have the same errors for other files. Besides that, in this case, from BackupPC's POV, it doesn't matter if the directory is used a Recycle Bin for samba. It's just a directory where files which were previously elswhere have been moved. It could have been done by a human intervention in a FooBar directory. I'm just trying to understand what the error means -- Daniel Berteaud FIREWALL-SERVICES SAS, La sécurité des réseaux Société de Services en Logiciels Libres Tel/Fax : +33.5 56 64 15 32 Mail : dan...@firewall-services.com Web : https://www.firewall-services.com___ 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] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
On 2019-04-03 05:02, Daniel Berteaud wrote: Am I the only one having this kind of errors, or the only one caring about the errors ? Cheers Daniel Le 12/03/2019 à 08:56, Daniel Berteaud a écrit : Hi. I've been using BackupPC since the past 13 years (starting with 2.1.2 I think), with great success. I'm now running a few installations with v4, and one of the things I don't understand is the Xfer errors. I regularily check Xfer error to be sure my backups are OK. Before v3, I could reliabily check the number of Xfer errors, but in v4, I don't understand. First, as soon as there's a single error (most common are "file has vanished"), BackupPC reports 3 errors. Often, the backup reports an error count of 2, with these kind of errors : [ 213 lignes sautées ] rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022/_metadata" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023/_metadata" failed: No such file or directory (2) These files seem likely to have been updated or removed during the backup run. That directory contains bookmarks, cookies, extensions, and all kinds of things one might expect to change. [ 106 lignes sautées ] [...] rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1676) [generator=3.1.2.0] rsync_bpc exited with benign status 23 (5888) This essentially summarizes that files weren't found during the rsync transfer that were identified before the transfer, which matches the symptom above, which is expected when trying to back up transient files. This is quite confusing because, in this example, the directories does exist, both on the source, and in the backup accounting these errors. For files which are frequently deleted and recreated (such as cache files) this is expected behavior. So, what does this error mean ? It looks like it happens when those directories did not exist in the previous backup (the one aginst which rsync is transfering deltas), but, why would this be an error ? rsync doesn't know why files would disappear or be created during a run -- as has been pointed out elsewhere, you may want to quiesce chrome, or (more sensibly) not try to back up transient files. Last, and the most important to me, I have some hosts with hundreds of Xfer errors like these : [ 53777 lignes sautées ] R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle Bin/BIBLIOTHEQUE/DOCUMENTATION/AMIANTE/Courrier FEDEREC-CRAMIF-Demande de conventionnement.pdf): file doesn't exist R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle Bin/BIBLIOTHEQUE/DOCUMENTATION/BTP/Courrier FEDEREC-CRAMIF-Demande de conventionnement.pdf): file doesn't exist R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle Bin/DOSSIERS COMMUNS GROUPE PENA/ACHATS/DEMANDES D'ACHAT/2019/2 FEV 19/110319CB - GESTECO Château de France.docx): file doesn't exist [ 161 lignes sautées ] Those errors are not accounted in the Xfer error count, but displayed if we open the XferErr log. My C foo is not good enough to understand exactly what's going on in https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7dCyrjIWd3LVbeqZFg4ygUGvSfi41qKNj5ycIIg4GkJF3ZYo8-2Fl9JPHIyP-2FT2T5NlSfZvMVW9z8xIQ8r-2FhomH40-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CBnNjwF56OFtfIV34pOjuQRpX-2B3dRh-2FjPvm7nBC7QxnAw7MCkPTmIk5XYe1BLmUKuA6iTm8N0OT4B0OgafrFblGeYsQ8kd01o5RmDhP2n6-2B8W41NzlSMQcHJX7hUnGeIeAdm5W7NTHAd2gXpp7P0Ej3e-2BOUWZ1nTVQpIsrBRs8alPGkONXI1q-2Be9bHyoBqXWW Looks like this error can be logged when a file is moved (so it exists in the pool, but not at the same path in the previous backup agsint which we delta ?) Can someone confirm this is harmless ? I so, wouldn't it make sens to remove this from the XferErr (or maybe just include it if XferLogLevel > 3 or something like that ?) The symptoms here and the directory in question matches the behavior that is expected when backing up a Samba share used by Windows systems with access to a recycle bin. Windows will rename a file into the recycle bin, so you'll see this when you back up the original file -and- the recycle bin. I can't imagine why one would normally want to back up a recycle bin, since presumably one would have already backed up the file before it was deleted, so it's probably simplest just to exclude the bin from the backups. Alternatively, one can remove the bin (or access to it) so that Windows clients delete the original files, though that also makes backup of the recycle bin somewhat pointless. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:
Re: [BackupPC-users] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
Le 04/04/2019 à 16:20, G.W. Haywood via BackupPC-users a écrit : > Hi there, Hi, thanks for your response :-) > > Like you, after using V3 for many years I'm playing with V4, but only > seriously since about August 2018. There were a few hiccups to begin > with, but I don't see the kinds of errors that you're seeing. > > No hosts here use the 'rsync' XferMethod. I've grepped XferLOGs for > the past year for errors on hosts which use the 'rsyncd' XferMethod, > and apart from a few expected errors where machines have been shut > down mid-backup, nothing is making itself obvious. Maybe the issue only manifest itself when using the rsync transport then (I use almost exclusively rsync over ssh). Craig, if you're arround, could you explain what those errors mean ? ++ ___ 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] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
Hi there, On Tue, 12 Mar 2019, Daniel Berteaud wrote: I've been using BackupPC since the past 13 years (starting with 2.1.2 I think), with great success. I'm now running a few installations with v4, and one of the things I don't understand is the Xfer errors. [...snip...] On Thu, 4 Apr 2019, Daniel Berteaud wrote: Am I the only one having this kind of errors, or the only one caring about the errors ? Your patience is commendable. :) Like you, after using V3 for many years I'm playing with V4, but only seriously since about August 2018. There were a few hiccups to begin with, but I don't see the kinds of errors that you're seeing. No hosts here use the 'rsync' XferMethod. I've grepped XferLOGs for the past year for errors on hosts which use the 'rsyncd' XferMethod, and apart from a few expected errors where machines have been shut down mid-backup, nothing is making itself obvious. I've grepped BackupPC XferLOGs going all the way back to 2016 for the strings 'No such file or directory' and 'bpc_sysCall_checkFileMatch'. There was no instance of 'No such file or directory', and just a few 'bpc_sysCall_checkFileMatch ... file doesn't exist'. The majority of the latter were in the hidden sub-directories of home directories on machines which run X sessions/desktops. The errors are reasonable and since moving to BPC V4 I've routinely excluding those directories from backups anyway. The error has never appeared for any of our server machines which offer only shell access. HTH -- 73, Ged. ___ 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] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
Am I the only one having this kind of errors, or the only one caring about the errors ? Cheers Daniel Le 12/03/2019 à 08:56, Daniel Berteaud a écrit : > > Hi. > > I've been using BackupPC since the past 13 years (starting with 2.1.2 > I think), with great success. I'm now running a few installations with > v4, and one of the things I don't understand is the Xfer errors. I > regularily check Xfer error to be sure my backups are OK. Before v3, I > could reliabily check the number of Xfer errors, but in v4, I don't > understand. > > First, as soon as there's a single error (most common are "file has > vanished"), BackupPC reports 3 errors. > > Often, the backup reports an error count of 2, with these kind of errors : > > [ 213 lignes sautées ] > rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022" > failed: No such file or directory (2) > rsync_bpc: stat > "/.config/google-chrome/CertificateRevocation/5022/_metadata" failed: > No such file or directory (2) > rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023" > failed: No such file or directory (2) > rsync_bpc: stat > "/.config/google-chrome/CertificateRevocation/5023/_metadata" failed: > No such file or directory (2) > [ 106 lignes sautées ] > > [...] > > rsync error: some files/attrs were not transferred (see previous > errors) (code 23) at main.c(1676) [generator=3.1.2.0] > rsync_bpc exited with benign status 23 (5888) > > > This is quite confusing because, in this example, the directories does > exist, both on the source, and in the backup accounting these errors. > So, what does this error mean ? It looks like it happens when those > directories did not exist in the previous backup (the one aginst which > rsync is transfering deltas), but, why would this be an error ? > > Last, and the most important to me, I have some hosts with hundreds of > Xfer errors like these : > > > [ 53777 lignes sautées ] > R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle > Bin/BIBLIOTHEQUE/DOCUMENTATION/AMIANTE/Courrier FEDEREC-CRAMIF-Demande > de conventionnement.pdf): file doesn't exist > R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle > Bin/BIBLIOTHEQUE/DOCUMENTATION/BTP/Courrier FEDEREC-CRAMIF-Demande de > conventionnement.pdf): file doesn't exist > R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle > Bin/DOSSIERS COMMUNS GROUPE PENA/ACHATS/DEMANDES D'ACHAT/2019/2 FEV > 19/110319CB - GESTECO Château de France.docx): file doesn't exist > [ 161 lignes sautées ] > > Those errors are not accounted in the Xfer error count, but displayed > if we open the XferErr log. My C foo is not good enough to understand > exactly what's going on in > https://github.com/backuppc/rsync-bpc/blob/master/bpc_sysCalls.c#L759 > > Looks like this error can be logged when a file is moved (so it exists > in the pool, but not at the same path in the previous backup agsint > which we delta ?) > > Can someone confirm this is harmless ? I so, wouldn't it make sens to > remove this from the XferErr (or maybe just include it if XferLogLevel > > 3 or something like that ?) > > ___ 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] Xfer errors in "Failures that need attention"
>From: Karol Jędrzejczyk >I'm using BackupPC to back up a bunch of servers only. In this scenario >any transfer error is critical. Hi Karol, I like to receive reports of any failures so I install BackupPC_report [1] on the BackupPC server then I explore the logs from any that error out. I call it with these cronjobs to reduce the amount of clutter in my inbox: #Ansible: BackupPC - Send report Monday morning 5 08 * * 1 /usr/share/BackupPC/bin/BackupPC_report.pl | mail -r `hostname -s`@`hostname -d` -s "BackupPC@`hostname -s` weekly report" my_team@my_domain.com #Ansible: BackupPC - Send report on error 5 08 * * * /usr/share/BackupPC/bin/BackupPC_report.pl -s | mail -E -r `hostname -s`@`hostname -d` -s "BackupPC@`hostname -s` warning" my_team@my_domain.com [1] https://github.com/moisseev/BackupPC_report ___ 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/
[BackupPC-users] Xfer errors in "Failures that need attention"
Hello, I'm using BackupPC to back up a bunch of servers only. In this scenario any transfer error is critical. Is it possible to list hosts for witch xfer errors occurred in the latest backup under "Failures that need attention" in the WebUI? -- Karol Jędrzejczyk -- CONFIDENTIALITY NOTICE This message and any attachment is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, confidential, legally privileged or otherwise exempt from disclosure. The security and integrity of e-mails cannot be guaranteed. Any reply to this e-mail and any attachment received may be subject to Icotera monitoring. If you are not the named addressee, you are not authorized to use, distribute, copy or take any action in reliance on this message. The unauthorized use, disclosure, or copying of this communication, or any attachment, is strictly prohibited and may be unlawful. No waiver of confidentiality or any applicable privilege is intended by any mistransmission. If you have received this message in error, please notify the sender immediately by replying to this e-mail and delete all copies of this message and any attachments. ___ 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/
[BackupPC-users] Xfer errors (especially bpc_sysCall_checkFileMatch(/path/to/file): file doesn't exist)
Hi. I've been using BackupPC since the past 13 years (starting with 2.1.2 I think), with great success. I'm now running a few installations with v4, and one of the things I don't understand is the Xfer errors. I regularily check Xfer error to be sure my backups are OK. Before v3, I could reliabily check the number of Xfer errors, but in v4, I don't understand. First, as soon as there's a single error (most common are "file has vanished"), BackupPC reports 3 errors. Often, the backup reports an error count of 2, with these kind of errors : [ 213 lignes sautées ] rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5022/_metadata" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023" failed: No such file or directory (2) rsync_bpc: stat "/.config/google-chrome/CertificateRevocation/5023/_metadata" failed: No such file or directory (2) [ 106 lignes sautées ] [...] rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1676) [generator=3.1.2.0] rsync_bpc exited with benign status 23 (5888) This is quite confusing because, in this example, the directories does exist, both on the source, and in the backup accounting these errors. So, what does this error mean ? It looks like it happens when those directories did not exist in the previous backup (the one aginst which rsync is transfering deltas), but, why would this be an error ? Last, and the most important to me, I have some hosts with hundreds of Xfer errors like these : [ 53777 lignes sautées ] R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle Bin/BIBLIOTHEQUE/DOCUMENTATION/AMIANTE/Courrier FEDEREC-CRAMIF-Demande de conventionnement.pdf): file doesn't exist R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle Bin/BIBLIOTHEQUE/DOCUMENTATION/BTP/Courrier FEDEREC-CRAMIF-Demande de conventionnement.pdf): file doesn't exist R bpc_sysCall_checkFileMatch(shares/assistantedirection/files/Recycle Bin/DOSSIERS COMMUNS GROUPE PENA/ACHATS/DEMANDES D'ACHAT/2019/2 FEV 19/110319CB - GESTECO Château de France.docx): file doesn't exist [ 161 lignes sautées ] Those errors are not accounted in the Xfer error count, but displayed if we open the XferErr log. My C foo is not good enough to understand exactly what's going on in https://github.com/backuppc/rsync-bpc/blob/master/bpc_sysCalls.c#L759 Looks like this error can be logged when a file is moved (so it exists in the pool, but not at the same path in the previous backup agsint which we delta ?) Can someone confirm this is harmless ? I so, wouldn't it make sens to remove this from the XferErr (or maybe just include it if XferLogLevel > 3 or something like that ?) Cheers, Daniel -- Logo FWS *Daniel Berteaud* FIREWALL-SERVICES SAS. Société de Services en Logiciels Libres Tel : 05 56 64 15 32 Matrix: @dani:fws.fr /www.firewall-services.com/ ___ 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] Xfer errors
Pete, Can you send me more lines from the XferLOG file for a full backup? Ideally the entire log file, or otherwise several hundred lines before and after the errors. Craig On Fri, Jun 29, 2018 at 4:53 AM Pete Geenhuizen wrote: > I'm running BackupPC 4.2.1 on CentOS 7.5 using rsync and it's running > just fine with one seemingly minor problem. > > I recently upgraded a host from CentOS 6.9 to CentOS 7.5 and forced a > level 0 backup, and since then I see the following errors. > > cannot delete non-empty directory: bin > could not make way for new symlink: bin > cannot delete non-empty directory: lib > could not make way for new symlink: lib > cannot delete non-empty directory: lib64 > could not make way for new symlink: lib64 > cannot delete non-empty directory: sbin > could not make way for new symlink: sbin > cannot delete non-empty directory: var/lock > could not make way for new symlink: var/lock > cannot delete non-empty directory: var/run > could not make way for new symlink: var/run > > Although these errors don't seem to affect the backups and seem to be > benign I'd like to deal with them. > > Any ideas on how to best eliminate these error? > > 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. > > > > -- > 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/
[BackupPC-users] Xfer errors
I'm running BackupPC 4.2.1 on CentOS 7.5 using rsync and it's running just fine with one seemingly minor problem. I recently upgraded a host from CentOS 6.9 to CentOS 7.5 and forced a level 0 backup, and since then I see the following errors. cannot delete non-empty directory: bin could not make way for new symlink: bin cannot delete non-empty directory: lib could not make way for new symlink: lib cannot delete non-empty directory: lib64 could not make way for new symlink: lib64 cannot delete non-empty directory: sbin could not make way for new symlink: sbin cannot delete non-empty directory: var/lock could not make way for new symlink: var/lock cannot delete non-empty directory: var/run could not make way for new symlink: var/run Although these errors don't seem to affect the backups and seem to be benign I'd like to deal with them. Any ideas on how to best eliminate these error? 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. -- 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] Xfer errors for 31 files
Le 27/08/2017 à 23:18, Craig Barratt via BackupPC-users a écrit :
Daniel,
Thanks Craig for looking at this. To check if the problem could be
reproduced, I've renamed the faulty host dir and started with fresh
backup (and up to now, no errors occured). I still have the faulty
directory (renamed robert.xferErr), here are the info requested
Can you check if there is an attrib file in that directory
(/var/lib/BackupPC//pc/robert/242/f%2f/fusr/fbin)? (You might need to
update the 242 to be the number of the latest filled backup.) It
should have a file name of the form "attrib_" where is 32 hex
digits.
Yes, there's
/var/lib/BackupPC//pc/robert.xferErr/244/f%2f/fusr/fbin/attrib_5ecf35554e19361c98c012c616eb838c
Next, run this command to display the contents of the attrib file:
BackupPC_attribPrint
/var/lib/BackupPC//pc/robert/242/f%2f/fusr/fbin/attrib_
Either send the whole output to me directly (not to the list), or
excerpt just the perl entry (about a dozen lines starting with 'perl'
=> {)
Here's the part regarding the perl binary:
'perl' => {
'compress' => 3,
'digest' => '',
'gid' => 0,
'inode' => 2833243,
'mode' => 493,
'mtime' => 1490180558,
'name' => 'perl',
'nlinks' => 0,
'size' => 13304,
'type' => 0,
'uid' => 0
},
And, as the digest is missing, I can't lookup in the cpool. The file
must be there now anyway (as it was present in previous backups, and is
now for sure present in the new backups of the same host since I've
started new backups from scratch). So I guess the issue is just the
missing digest in the attrib.
Anything else you'd need ?
Cheers,
Daniel
--
Logo FWS
*Daniel Berteaud*
FIREWALL-SERVICES SAS.
Société de Services en Logiciels Libres
Tel : 05 56 64 15 32
Visio : http://vroom.fws.fr/dani
/www.firewall-services.com/
--
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] Xfer errors for 31 files
Daniel,
Can you check if there is an attrib file in that directory
(/var/lib/BackupPC//pc/robert/242/f%2f/fusr/fbin)? (You might need to
update the 242 to be the number of the latest filled backup.) It should
have a file name of the form "attrib_" where is 32 hex digits.
Next, run this command to display the contents of the attrib file:
BackupPC_attribPrint
/var/lib/BackupPC//pc/robert/242/f%2f/fusr/fbin/attrib_
Either send the whole output to me directly (not to the list), or excerpt
just the perl entry (about a dozen lines starting with 'perl' => {)
Next, look in the digest value (eg: 'digest' =>
'90bd39764f9259dd7eafad8ce8b59939'), and see if that digest is in the cpool
(the subdirs are even, so bd becomes bc):
ls -l /var/lib/BackupPC/cpool/90/bc/90bd39764f9259dd7eafad8ce8b59939
Craig
On Mon, Aug 21, 2017 at 3:20 AM, Daniel Berteaud <
dan...@firewall-services.com> wrote:
> Hi.
>
>
> Running BackupPC 4.1.3 (with rsync-bpc 3.0.9.8 and BackupPC::XS 0.56)
> since a few months on my EL6 server. I'm backing up 53 machines
> successfuly. Except for 1 of them, where for each backup I have 31 xfer
> errors like this one:
>
>
> G bpc_fileOpen: can't open file
> /var/lib/BackupPC//pc/robert/242/f%2f/fusr/fbin/fperl
> (from usr/bin/perl, 3, 0, 0)
> G bpc_fileDescFree: fdNum = 3, tmpFd = -1, tmpFileName = NULL
> G bpc_open(usr/bin/perl, 0x0, 00) -> -1
> rsync_bpc: failed to open "/usr/bin/perl", continuing: No such file or
> directory (2)
>
> Nothing special about thses files on the client, they are readable. I
> guess there's an issue in BackupPC's pool, but I don't know how to track
> it. At the begining (migration from v3), I didn't had these errors. v4 ran
> fine for a few weeks, and then started to show these errors.
>
> How can I track this down ?
>
>
> Cheers,
>
> Daniel
> --
>
> [image: Logo FWS]
> *Daniel Berteaud*
>
> FIREWALL-SERVICES SAS.
> Société de Services en Logiciels Libres
> Tel : 05 56 64 15 32 <0556641532>
> Visio : http://vroom.fws.fr/dani
> *www.firewall-services.com *
>
>
> --
> 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/
[BackupPC-users] Xfer errors for 31 files
Hi. Running BackupPC 4.1.3 (with rsync-bpc 3.0.9.8 and BackupPC::XS 0.56) since a few months on my EL6 server. I'm backing up 53 machines successfuly. Except for 1 of them, where for each backup I have 31 xfer errors like this one: G bpc_fileOpen: can't open file /var/lib/BackupPC//pc/robert/242/f%2f/fusr/fbin/fperl (from usr/bin/perl, 3, 0, 0) G bpc_fileDescFree: fdNum = 3, tmpFd = -1, tmpFileName = NULL G bpc_open(usr/bin/perl, 0x0, 00) -> -1 rsync_bpc: failed to open "/usr/bin/perl", continuing: No such file or directory (2) Nothing special about thses files on the client, they are readable. I guess there's an issue in BackupPC's pool, but I don't know how to track it. At the begining (migration from v3), I didn't had these errors. v4 ran fine for a few weeks, and then started to show these errors. How can I track this down ? Cheers, Daniel -- Logo FWS *Daniel Berteaud* FIREWALL-SERVICES SAS. Société de Services en Logiciels Libres Tel : 05 56 64 15 32 Visio : http://vroom.fws.fr/dani /www.firewall-services.com/ -- 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/
