Re: [BackupPC-users] [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
On 2018-02-02 01:20, Marc Gilliatt wrote: Can I please get an update on my issue, please? This is our only source of backing up our servers, we are not backing up at the current moment because of this issue. As mentioned, I upgraded backuppc from 3.3.1 to 4.1.3 from which I download the tar file from the backuppc website. However, when I see what version of backuppc I'm currently running right now, it's still 3.3.1? I'm not sure what I've done wrong? - This will be somewhat backwards due to top-posting, but I'll start here -- the first thing you've done wrong is persisted in using the developer list, but it is a user issue. You're much more likely to get faster and better responses on the correct list. I've taken the liberty of crossposting this reply to the users list (see above) in the hopes that we can terminate this thread in the developer discussion, where it does not belong. FROM: Marc GilliattSENT: 31 January 2018 10:17 TO: Michael Stowe; Developers discussion SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* I apologize for the multiple emails. I am now getting the following message when I go into the GUI INTERNAL SERVER ERROR The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. - Apache/2.4.18 (Ubuntu) Server at backuppc01.dsdb.int Port 80 Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. - That part about more information available in the server error log is usually a good clue -- what does the server error log say? FROM: Marc Gilliatt SENT: 31 January 2018 09:39 TO: Michael Stowe; Developers discussion SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* I tried to download backuppc-4.1.3 from the backuppc website. The upgrade went fine, however, I backuppc.server won't start now? In the GUI, I'm getting. ERROR: UNABLE TO CONNECT TO BACKUPPC SERVER This CGI script (/backuppc/index.cgi) is unable to connect to the BackupPC server on backuppc01 port -1. The error was: unix connect: No such file or directory. Perhaps the BackupPC server is not running or there is a configuration error. Please report this to your Sys Admin. And when I try to run "service backuppc restart", Im getting. Job for backuppc.service failed because the control process exited with error code. See "systemctl status backuppc.service" and "journalctl -xe" for details. And when I run "systemctl status backuppc.service", Im getting. backuppc.service - LSB: Launch backuppc server Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT; 20s ago Docs: man:systemd-sysv-generator(8) Process: 29163 ExecStop=/etc/init.d/backuppc stop (code=exited, status=0/SUCCESS) Process: 29425 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc... Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be started because important parameters are missing from config.pl. Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. I followed the upgrade instructions correctly. I have no working backuppc now...any ideas, please? - I can't speak to which upgrade instructions you followed and whether or not you did so correctly, but this is telling you that you're trying to start a version 4 server with a version 3 config.pl, which probably isn't going to work well. FROM: Marc Gilliatt SENT: 31 January 2018 08:37 TO: Michael Stowe CC: Developers discussion SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* My distro is Ubuntu 16.04.3 I try to upgrade just backuppc, and it's telling me that "backuppc is already the newest version (3.3.1-2ubuntu3.3)." I'm not sure on how I can
Re: [BackupPC-users] Serious error: last backup ... directory doesn't exist!!!
Other things to check include: - is the file system full? (df) - you did say it was only 65% full, so that should be ok - have you run out of inodes? (df -i) If you can't directly see some problem with the file system the next step is to stop backuppc, unmount the file system and run fsck. Craig On Fri, Feb 2, 2018 at 9:19 AM, Craig Barratt < cbarr...@users.sourceforge.net> wrote: > Here are a few things to check: > >- can you manually create files and directories below >/vol/bpc4/BackupPC as the backuppc user (eg, "su backuppc; cd >/vol/bpc4/BackupPC; mkdir foo; rmdir foo; touch foobar; rm foobar") >- is the file system mounted readonly? >- has the backuppc user lost permissions? > > It does look like the failure to update the filesystem exposes a bug which > I'll fix, but this is secondary to your main issue: > > Can't use an undefined value as an ARRAY reference at > /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380 > > > Craig > > On Fri, Feb 2, 2018 at 5:56 AM,wrote: > >> Dear BackupPC Users, >> >> >> I am running BackupPC-4.1.3 for several months without problems >> (really a great piece of software). >> >> About a week ago a strange type of error occured and keeps staying, >> which I cannot understand. The error messages are like this ("fs" is >> the name of one of my systems to be backed up; I did some linebreaks >> to increase readability): >> >> >> 2018-01-28 23:43:34 Can't create /vol/bpc4/BackupPC/pc/fs/149/refCnt >> 2018-01-29 02:09:34 Serious error: last backup >> /vol/bpc4/BackupPC/pc/fs/149 directory doesn't exist!!! Need to >> remove back to last filled backup >> 2018-01-29 02:09:34 Deleting backup 147 >> 2018-01-29 02:09:35 BackupPC_backupDelete: removing #147 >> 2018-01-29 02:09:35 BackupPC_backupDelete: No prior backup for merge >> 2018-01-29 02:09:52 BackupPC_refCountUpdate: doing fsck on fs #149 >> since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist >> 2018-01-29 02:09:52 Can't use an undefined value as an ARRAY reference >> at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380. >> 2018-01-29 02:09:52 BackupPC_backupDelete: got 1 errors >> 2018-01-29 02:09:52 Finished BackupPC_backupDelete, status = 256 >> (running time: 18 sec) >> 2018-01-29 02:09:52 Deleting backup 148 >> 2018-01-29 02:09:52 BackupPC_backupDelete: removing #148 >> 2018-01-29 02:09:52 BackupPC_backupDelete: No prior backup for merge >> 2018-01-29 02:09:55 BackupPC_refCountUpdate: doing fsck on fs #149 >> since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist >> 2018-01-29 02:09:55 Can't use an undefined value as an ARRAY reference >> at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380. >> 2018-01-29 02:09:55 BackupPC_backupDelete: got 1 errors >> 2018-01-29 02:09:55 Finished BackupPC_backupDelete, status = 256 >> (running time: 3 sec) >> 2018-01-29 02:09:55 Deleting backup 149 >> 2018-01-29 02:09:56 BackupPC_backupDelete: removing #149 >> 2018-01-29 02:09:56 BackupPC_backupDelete: No prior backup for merge >> 2018-01-29 02:38:20 BackupPC_refCountUpdate: host fs got 0 errors >> (took 1704 secs) >> 2018-01-29 02:38:20 Finished BackupPC_backupDelete, status = 0 >> (running time: 1705 sec) >> 2018-01-29 03:16:29 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-29 03:55:15 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-29 04:15:15 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-29 23:43:54 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-30 01:24:02 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-30 02:36:01 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-30 03:42:01 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-30 04:12:01 dump failed: unable to open/create >> /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z >> 2018-01-30 23:57:53 Copying backup #146 to #147 >> >> 2018-01-31 01:05:38 Can't mkpath >> /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00 >> 2018-01-31 01:05:38 Can't copy >> ./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1 >> to /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00/attr >> ib_dc793dc4650baa1a8cc3b69d211573c1 >> ... >> >> The last pair of messages is then repeated for thousands of files. >> >> >> It seems, that there is an error concerning the sequence. >> >> I had checked for several default reasons: >> - No files or directories have been manipulated manually >> - BackupPC is almost the only task running on my backup server (there >> should be no side effects from other services; no user is normally >> working on that machine) >> - the file system has about 1.6 TB at a usage of 65% (this rate was >> never exceeded) >> - the system had no crash (uptime is 217 days,
Re: [BackupPC-users] Serious error: last backup ... directory doesn't exist!!!
Here are a few things to check: - can you manually create files and directories below /vol/bpc4/BackupPC as the backuppc user (eg, "su backuppc; cd /vol/bpc4/BackupPC; mkdir foo; rmdir foo; touch foobar; rm foobar") - is the file system mounted readonly? - has the backuppc user lost permissions? It does look like the failure to update the filesystem exposes a bug which I'll fix, but this is secondary to your main issue: Can't use an undefined value as an ARRAY reference at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380 Craig On Fri, Feb 2, 2018 at 5:56 AM,wrote: > Dear BackupPC Users, > > > I am running BackupPC-4.1.3 for several months without problems > (really a great piece of software). > > About a week ago a strange type of error occured and keeps staying, > which I cannot understand. The error messages are like this ("fs" is > the name of one of my systems to be backed up; I did some linebreaks > to increase readability): > > > 2018-01-28 23:43:34 Can't create /vol/bpc4/BackupPC/pc/fs/149/refCnt > 2018-01-29 02:09:34 Serious error: last backup > /vol/bpc4/BackupPC/pc/fs/149 directory doesn't exist!!! Need to > remove back to last filled backup > 2018-01-29 02:09:34 Deleting backup 147 > 2018-01-29 02:09:35 BackupPC_backupDelete: removing #147 > 2018-01-29 02:09:35 BackupPC_backupDelete: No prior backup for merge > 2018-01-29 02:09:52 BackupPC_refCountUpdate: doing fsck on fs #149 > since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist > 2018-01-29 02:09:52 Can't use an undefined value as an ARRAY reference > at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380. > 2018-01-29 02:09:52 BackupPC_backupDelete: got 1 errors > 2018-01-29 02:09:52 Finished BackupPC_backupDelete, status = 256 > (running time: 18 sec) > 2018-01-29 02:09:52 Deleting backup 148 > 2018-01-29 02:09:52 BackupPC_backupDelete: removing #148 > 2018-01-29 02:09:52 BackupPC_backupDelete: No prior backup for merge > 2018-01-29 02:09:55 BackupPC_refCountUpdate: doing fsck on fs #149 > since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist > 2018-01-29 02:09:55 Can't use an undefined value as an ARRAY reference > at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380. > 2018-01-29 02:09:55 BackupPC_backupDelete: got 1 errors > 2018-01-29 02:09:55 Finished BackupPC_backupDelete, status = 256 > (running time: 3 sec) > 2018-01-29 02:09:55 Deleting backup 149 > 2018-01-29 02:09:56 BackupPC_backupDelete: removing #149 > 2018-01-29 02:09:56 BackupPC_backupDelete: No prior backup for merge > 2018-01-29 02:38:20 BackupPC_refCountUpdate: host fs got 0 errors > (took 1704 secs) > 2018-01-29 02:38:20 Finished BackupPC_backupDelete, status = 0 > (running time: 1705 sec) > 2018-01-29 03:16:29 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-29 03:55:15 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-29 04:15:15 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-29 23:43:54 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-30 01:24:02 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-30 02:36:01 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-30 03:42:01 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-30 04:12:01 dump failed: unable to open/create > /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z > 2018-01-30 23:57:53 Copying backup #146 to #147 > > 2018-01-31 01:05:38 Can't mkpath > /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00 > 2018-01-31 01:05:38 Can't copy > ./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1 > to /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00/attrib_ > dc793dc4650baa1a8cc3b69d211573c1 > ... > > The last pair of messages is then repeated for thousands of files. > > > It seems, that there is an error concerning the sequence. > > I had checked for several default reasons: > - No files or directories have been manipulated manually > - BackupPC is almost the only task running on my backup server (there > should be no side effects from other services; no user is normally > working on that machine) > - the file system has about 1.6 TB at a usage of 65% (this rate was > never exceeded) > - the system had no crash (uptime is 217 days, since setup of > BackupPC). > - /vol/bpc4 is a mount point of an ext4 file system (normally very > reliable) > - Kernel 4.1.39, OpenSuSE 42.1 - not really outdated > > > > > Any advice to repair this error is highly appretiated. > > > Best regards > > > Torsten Finke > > > > -- > > Torsten Finke > f...@igh.de > > Ingenieurgemeinschaft IgH > Gesellschaft für Ingenieurleistungen mbH > Heinz-Bäcker-Str. 34 > D-45356 Essen > >
[BackupPC-users] Serious error: last backup ... directory doesn't exist!!!
Dear BackupPC Users, I am running BackupPC-4.1.3 for several months without problems (really a great piece of software). About a week ago a strange type of error occured and keeps staying, which I cannot understand. The error messages are like this ("fs" is the name of one of my systems to be backed up; I did some linebreaks to increase readability): 2018-01-28 23:43:34 Can't create /vol/bpc4/BackupPC/pc/fs/149/refCnt 2018-01-29 02:09:34 Serious error: last backup /vol/bpc4/BackupPC/pc/fs/149 directory doesn't exist!!! Need to remove back to last filled backup 2018-01-29 02:09:34 Deleting backup 147 2018-01-29 02:09:35 BackupPC_backupDelete: removing #147 2018-01-29 02:09:35 BackupPC_backupDelete: No prior backup for merge 2018-01-29 02:09:52 BackupPC_refCountUpdate: doing fsck on fs #149 since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist 2018-01-29 02:09:52 Can't use an undefined value as an ARRAY reference at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380. 2018-01-29 02:09:52 BackupPC_backupDelete: got 1 errors 2018-01-29 02:09:52 Finished BackupPC_backupDelete, status = 256 (running time: 18 sec) 2018-01-29 02:09:52 Deleting backup 148 2018-01-29 02:09:52 BackupPC_backupDelete: removing #148 2018-01-29 02:09:52 BackupPC_backupDelete: No prior backup for merge 2018-01-29 02:09:55 BackupPC_refCountUpdate: doing fsck on fs #149 since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist 2018-01-29 02:09:55 Can't use an undefined value as an ARRAY reference at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380. 2018-01-29 02:09:55 BackupPC_backupDelete: got 1 errors 2018-01-29 02:09:55 Finished BackupPC_backupDelete, status = 256 (running time: 3 sec) 2018-01-29 02:09:55 Deleting backup 149 2018-01-29 02:09:56 BackupPC_backupDelete: removing #149 2018-01-29 02:09:56 BackupPC_backupDelete: No prior backup for merge 2018-01-29 02:38:20 BackupPC_refCountUpdate: host fs got 0 errors (took 1704 secs) 2018-01-29 02:38:20 Finished BackupPC_backupDelete, status = 0 (running time: 1705 sec) 2018-01-29 03:16:29 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-29 03:55:15 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-29 04:15:15 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-29 23:43:54 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-30 01:24:02 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-30 02:36:01 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-30 03:42:01 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-30 04:12:01 dump failed: unable to open/create /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z 2018-01-30 23:57:53 Copying backup #146 to #147 2018-01-31 01:05:38 Can't mkpath /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00 2018-01-31 01:05:38 Can't copy ./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1 to /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1 ... The last pair of messages is then repeated for thousands of files. It seems, that there is an error concerning the sequence. I had checked for several default reasons: - No files or directories have been manipulated manually - BackupPC is almost the only task running on my backup server (there should be no side effects from other services; no user is normally working on that machine) - the file system has about 1.6 TB at a usage of 65% (this rate was never exceeded) - the system had no crash (uptime is 217 days, since setup of BackupPC). - /vol/bpc4 is a mount point of an ext4 file system (normally very reliable) - Kernel 4.1.39, OpenSuSE 42.1 - not really outdated Any advice to repair this error is highly appretiated. Best regards Torsten Finke -- Torsten Finke f...@igh.de Ingenieurgemeinschaft IgH Gesellschaft für Ingenieurleistungen mbH Heinz-Bäcker-Str. 34 D-45356 Essen -- 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] BackupPC 4.1.5 released (plus new versions of backuppc-xs and rsync-bpc)
Hi did anybody notice that this won't work for Centos6? BackupPC-XS-0.57 is not available as there has been an error in the build process BackupPC-4.1.5 relies on the .57 version, so the system breaks, if updated to 4.1.5 :-( Michael Thursday, December 14, 2017, 11:00:00 AM, you wrote: JB> https://copr.fedorainfracloud.org/coprs/hobbes1069/BackupPC/ >JB> Do we know of any repos for RHEL/CentOS that usually package the >JB> latest BPC versions like this one? -- 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/