Re: [BackupPC-users] bpc_read error messages
No, those are recently added warnings as part of a fix for the case where the pool file is actually smaller than the file size in the attributes. In your case, the file size from the attributes is 18446744073709551613 (64 bit unsigned -3). I'm not sure how it got that way (possibly some corruption of the attribute file for that directory?), but the log message should mean it will get repaired during that backup. Craig On Tuesday, January 30, 2018, infos+backu...@ba-cst.net < infos+backu...@ba-cst.net> wrote: > Hello, > > We are using BPC 4, should be with latest release of every component. > > Not sure if this could mean troubles or some bug, so... > > While looking at a full XferLog, we found several "read past EOF" error > messages, with a huge fileSize (always the same for each error). Here > are two of those (with very short context in case it's useful) : > > same recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http > G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize = > 18446744073709551613, bufferSize = 8388608 > G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize = > 18446744073709551613, bufferSize = 8388608 > new recv >f.st.. rw-r--r-- 0, 0 3070 > usr/portage/dev-php/pecl-http/Manifest > > Are those errors troubles in the making ? They seem to have appeared > after a storage disk upgrade with offline rsync between old and new BPC > data repository. > > Tia, > -- B Consultants > > > -- > 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] bpc_read error messages
No, those are recently added warnings as part of a fix for the case where the pool file is actually smaller than the file size in the attributes. In your case, the file size from the attributes is 18446744073709551613 (64 bit unsigned -3). I'm not sure how it got that way (possibly some corruption of the attribute file for that directory?), but the log message should mean it will get repaired during that backup. Craig On Tuesday, January 30, 2018, infos+backu...@ba-cst.net < infos+backu...@ba-cst.net> wrote: > Hello, > > We are using BPC 4, should be with latest release of every component. > > Not sure if this could mean troubles or some bug, so... > > While looking at a full XferLog, we found several "read past EOF" error > messages, with a huge fileSize (always the same for each error). Here > are two of those (with very short context in case it's useful) : > > same recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http > G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize = > 18446744073709551613, bufferSize = 8388608 > G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize = > 18446744073709551613, bufferSize = 8388608 > new recv >f.st.. rw-r--r-- 0, 0 3070 > usr/portage/dev-php/pecl-http/Manifest > > Are those errors troubles in the making ? They seem to have appeared > after a storage disk upgrade with offline rsync between old and new BPC > data repository. > > Tia, > -- B Consultants > > > -- > 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] Upgrading to backuppc-4.1.3 FAILED!
On 2018-02-16 01:05, Marc Gilliatt wrote: I've just tried the _/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC' _command, and it hasn't worked I'm afraid, I tried reinstalling the Bakcuppc-41.3 tar file again, and gave it the full correct paths, and when I try to restart the service I'm still getting _Job for backuppc.service failed because the control process exited with error code. See "systemctl status backuppc.service" and "_journalctl_ -_xe_" for details. _With regards to the SCGI port number, do I set it to -1 or give it a port number? __And I'm still getting the internal error in the GUI. I don't understand why this has happened, all I did was upgraded the software, it looks like I'm going to have to re-raid my server and start fresh!!! Is there any way to roll back to my previous version of BackupPC please? - Moving from an installation package to a source-based install can be a bit of a trial, depending on how much the norms of that distro and packaging system deviate from the tarball. Version 4 is a fairly dramatic leap as well, which complicates things further. First, though, I'll address your question and give you the good news: since you never actually launched BackupPC 4, your repository is instact and in the expected location for your distro. Therefore, to revert to the previous version, you need only delete the tarball's files, and install the distro's version. N.B. preserve your config.pl and return it to its original location, as your distro may assume it is a new installation and do god-knows-what to your config.pl. Some are kinder than others. -- The SCGI question is a bit harder to answer without knowing what other choices you've made. Since I have set up SCGI, I match the port to what I have set up within Apache... which can be anything, as long as the number in Apache and in config.pl are the same. If I had not set up SCGI, I'd set it to -1. -- 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/
