Re: SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
Michael Stowe <[email protected]> Sat, 03 Feb 2018 07:34:06 +0000 (UTC)
| Newsgroups | gmane.comp.sysutils.backup.backuppc.devel,gmane.comp.sysutils.backup.backuppc.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... --===============5007370723173203534== Content-type: multipart/alternative; boundary="----------=_1517643246-21163-461" This is a multi-part message in MIME format... ------------=_1517643246-21163-461 Content-Type: text/plain; charset=UTF-8; format=flowed content-transfer-encoding: quoted-printable On 2018-02-02 01:20, Marc Gilliatt wrote:=0D > Can I please get an update on my issue, please?=0D > =0D > This is our only source of backing up our servers, we are not backing=0D > up at the current moment because of this issue.=0D > =0D > As mentioned, I upgraded backuppc from 3.3.1 to 4.1.3 from which I=0D > download the tar file from the backuppc website.=0D > =0D > However, when I see what version of backuppc I'm currently running=0D > right now, it's still 3.3.1?=0D > =0D > I'm not sure what I've done wrong?=0D > =0D > -------------------------=0D =0D This will be somewhat backwards due to top-posting, but I'll start here =0D -- the first thing you've done wrong is persisted in using the developer = =0D list, but it is a user issue. You're much more likely to get faster and = =0D better responses on the correct list. I've taken the liberty of =0D crossposting this reply to the users list (see above) in the hopes that =0D we can terminate this thread in the developer discussion, where it does =0D not belong.=0D > =0D > FROM: Marc Gilliatt <[email protected]>=0D > SENT: 31 January 2018 10:17=0D > TO: Michael Stowe; Developers discussion=0D > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up -=0D > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*=0D > =0D > I apologize for the multiple emails.=0D > =0D > I am now getting the following message when I go into the GUI....=0D > =0D > INTERNAL SERVER ERROR=0D > =0D > The server encountered an internal error or misconfiguration and was=0D > unable to complete your request.=0D > =0D > Please contact the server administrator at webmaster@localhost to=0D > inform them of the time this error occurred, and the actions you=0D > performed just before this error.=0D > =0D > More information about this error may be available in the server error=0D > log.=0D > -------------------------=0D > Apache/2.4.18 (Ubuntu) Server at backuppc01.dsdb.int Port 80=0D > =0D > Any ideas or suggestions on how to fix this, please? This is our only=0D > source of backing up our servers.=0D > -------------------------=0D =0D That part about more information available in the server error log is =0D usually a good clue -- what does the server error log say?=0D =0D > FROM: Marc Gilliatt <[email protected]>=0D > SENT: 31 January 2018 09:39=0D > TO: Michael Stowe; Developers discussion=0D > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up -=0D > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*=0D > =0D > I tried to download backuppc-4.1.3 from the backuppc website.=0D > =0D > The upgrade went fine, however, I backuppc.server won't start now?=0D > =0D > In the GUI, I'm getting.....=0D > =0D > ERROR: UNABLE TO CONNECT TO BACKUPPC SERVER=0D > =0D > This CGI script (/backuppc/index.cgi) is unable to connect to the=0D > BackupPC server on backuppc01 port -1.=0D > The error was: unix connect: No such file or directory.=0D > Perhaps the BackupPC server is not running or there is a configuration=0D > error. Please report this to your Sys Admin.=0D > =0D > And when I try to run "service backuppc restart", Im getting.....=0D > =0D > Job for backuppc.service failed because the control process exited=0D > with error code. See "systemctl status backuppc.service" and=0D > "journalctl -xe" for details.=0D > =0D > And when I run "systemctl status backuppc.service", Im getting.....=0D > =0D > backuppc.service - LSB: Launch backuppc server=0D > Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled)=0D > =0D > Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT;=0D > 20s ago=0D > Docs: man:systemd-sysv-generator(8)=0D > Process: 29163 ExecStop=3D/etc/init.d/backuppc stop (code=3Dexited,=0D > status=3D0/SUCCESS)=0D > =0D > Process: 29425 ExecStart=3D/etc/init.d/backuppc start (code=3Dexited,=0D > status=3D1/FAILURE)=0D > Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Launch backuppc=0D > server...=0D > Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc...=0D > =0D > Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be=0D > started because important parameters are missing from config.pl.=0D > =0D > Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded=0D > BackupPC, please update /etc/backuppc/config.pl.=0D > =0D > Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control=0D > process exited, code=3Dexited status=3D1=0D > =0D > Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch=0D > backuppc server.=0D > =0D > Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered=0D > failed state.=0D > =0D > Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with=0D > result 'exit-code'.=0D > =0D > I followed the upgrade instructions correctly.=0D > =0D > I have no working backuppc now...any ideas, please?=0D > -------------------------=0D =0D I can't speak to which upgrade instructions you followed and whether or =0D not you did so correctly, but this is telling you that you're trying to =0D start a version 4 server with a version 3 config.pl, which probably =0D isn't going to work well.=0D =0D > FROM: Marc Gilliatt <[email protected]>=0D > SENT: 31 January 2018 08:37=0D > TO: Michael Stowe=0D > CC: Developers discussion=0D > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up -=0D > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*=0D > =0D > My distro is Ubuntu 16.04.3=0D > =0D > I try to upgrade just backuppc, and it's telling me that "backuppc is=0D > already the newest version (3.3.1-2ubuntu3.3)."=0D > =0D > I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you=0D > suggested?=0D > =0D > -------------------------=0D > =0D > FROM: Michael Stowe <[email protected]>=0D > SENT: 31 January 2018 07:49=0D > TO: Marc Gilliatt=0D > CC: Developers discussion=0D > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up -=0D > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*=0D > =0D > On 2018-01-30 02:27, Marc Gilliatt wrote:=0D > =0D >> Sincere apologies for the late reply.=0D >> =0D >> You mention that version 3.3.1 doesn=E2=80=99t work with 4.3 of smbclien= t.=0D >> =0D >> How do I downgrade the smbclient, please?=0D > =0D > Unfortunately, that highly depends on your distro and/or flavor or how=0D > you've installed samba or smbclient in the first place. For some=0D > distros, it's as simple as specifying the version to the package=0D > manager or using the recommended downgrade path, for others, it can be=0D > much more complicated, requiring building from source or alternative=0D > repositories.=0D > =0D > It might be simpler to upgrade to version 3.3.2 (or later) instead.=0D > =0D > IIRC, the issue is that smbclient changed its reporting, so that=0D > BackupPC has trouble recognizing when the files are actually=0D > successfully retrieved, when in fact they are. ------------=_1517643246-21163-461 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <html><body> <p>On 2018-02-02 01:20, Marc Gilliatt wrote:</p> <blockquote><p>Can I please get an update on my issue, please?</p> <pre>This is our only source of backing up our servers, we are not backing<= /pre> <p>up at the current moment because of this issue.</p> <pre>As mentioned, I upgraded backuppc from 3.3.1 to 4.1.3 from which I</pr= e> <p>download the tar file from the backuppc website.</p> <pre>However, when I see what version of backuppc I'm currently running</pr= e> <p>right now, it's still 3.3.1?</p> <pre>I'm not sure what I've done wrong?</pre> <p>-------------------------</p></blockquote> <p>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 develop= er 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 crosspost= ing this reply to the users list (see above) in the hopes that we can termi= nate this thread in the developer discussion, where it does not belong.</p> <blockquote><pre>FROM: Marc Gilliatt <[email protected]> SENT: 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\*</pre> <pre>I apologize for the multiple emails.</pre> <pre>I am now getting the following message when I go into the GUI....</pre> <pre>INTERNAL SERVER ERROR</pre> <pre>The server encountered an internal error or misconfiguration and was unable to complete your request.</pre> <pre>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.</pre> <pre>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</pre> <pre> Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. -------------------------</pre></blockquote> <p>That part about more information available in the server error log is us= ually a good clue — what does the server error log say?</p> <blockquote><p>FROM: Marc Gilliatt <[email protected]> SENT: 31 J= anuary 2018 09:39 TO: Michael Stowe; Developers discussion SUBJECT: Re: [Ba= ckupPC-devel] SMB Windows share not backing up – NT_STATUS_ACCESS_DEN= IED listing \System Volume Information\SRM\*</p> <pre>I tried to download backuppc-4.1.3 from the backuppc website.</pre> <pre>The upgrade went fine, however, I backuppc.server won't start now?</pr= e> <pre>In the GUI, I'm getting.....</pre> <pre>ERROR: UNABLE TO CONNECT TO BACKUPPC SERVER</pre> <pre>This CGI script (/backuppc/index.cgi) is unable to connect to the</pre> <p>BackupPC server on backuppc01 port -1. The error was: unix connect: No s= uch file or directory. Perhaps the BackupPC server is not running or there = is a configuration error. Please report this to your Sys Admin.</p> <pre>And when I try to run "service backuppc restart", Im getting.....</pre> <pre>Job for backuppc.service failed because the control process exited</pr= e> <p>with error code. See “systemctl status backuppc.service” and= “journalctl -xe” for details.</p> <pre>And when I run "systemctl status backuppc.service", Im getting.....</p= re> <p>backuppc.service – LSB: Launch backuppc server Loaded: loaded (/et= c/init.d/backuppc; bad; vendor preset: enabled)</p> <p>Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT; 20= s ago Docs: man:systemd-sysv-generator(8)</p> <pre>Process: 29163 ExecStop=3D/etc/init.d/backuppc stop (code=3Dexited,</p= re> <p>status=3D0/SUCCESS)</p> <p>Process: 29425 ExecStart=3D/etc/init.d/backuppc start (code=3Dexited, st= atus=3D1/FAILURE) Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Laun= ch backuppc server…</p> <pre>Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc...</p= re> <pre>Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be</pre> <p>started because important parameters are missing from config.pl.</p> <p>Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded BackupP= C, please update /etc/backuppc/config.pl.</p> <p>Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control process= exited, code=3Dexited status=3D1</p> <p>Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch backu= ppc server.</p> <p>Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered fa= iled state.</p> <p>Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with res= ult ‘exit-code’.</p> <pre>I followed the upgrade instructions correctly.</pre> <h3>I have no working backuppc now…any ideas, please?</h3></blockquo= te> <p>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 sta= rt a version 4 server with a version 3 config.pl, which probably isn't goin= g to work well.</p> <blockquote><p>FROM: Marc Gilliatt <[email protected]> SENT: 31 J= anuary 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\*</p> <pre>My distro is Ubuntu 16.04.3</pre> <pre>I try to upgrade just backuppc, and it's telling me that "backuppc is<= /pre> <p>already the newest version (3.3.1-2ubuntu3.3)."</p> <pre>I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you</p= re> <p>suggested?</p> <p>-------------------------</p> <p>FROM: Michael Stowe <[email protected]> SENT: 31 Janu= ary 2018 07:49 TO: Marc Gilliatt CC: Developers discussion SUBJECT: Re: [Ba= ckupPC-devel] SMB Windows share not backing up – NT_STATUS_ACCESS_DEN= IED listing \System Volume Information\SRM\*</p> <p>On 2018-01-30 02:27, Marc Gilliatt wrote:</p> <blockquote><p>Sincere apologies for the late reply.</p> <p>You mention that version 3.3.1 doesn=E2=80=99t work with 4.3 of smbclien= t.</p> <p>How do I downgrade the smbclient, please?</p></blockquote> <p>Unfortunately, that highly depends on your distro and/or flavor or how y= ou've installed samba or smbclient in the first place. For some distros, it= 's as simple as specifying the version to the package manager or using the = recommended downgrade path, for others, it can be much more complicated, re= quiring building from source or alternative repositories.</p> <p>It might be simpler to upgrade to version 3.3.2 (or later) instead.</p> <p>IIRC, the issue is that smbclient changed its reporting, so that BackupP= C has trouble recognizing when the files are actually successfully retrieve= d, when in fact they are.</p></blockquote> <img src=3D"https://u2182357.ct.sendgrid.net/wf/open?upn=3DOypFYCWzG5ApGW-2= FFpGTxc73zzje-2FkFPhXiwUUFhBdTDFF5huz7qBgIbOvLhaFsHKdC-2BV2ZS6uHSmHMgcMAvES= G5EIxPwo-2BXWstyvnEynbE8pY9W3ROYz7fBZnRkvODGGFDuDOxJmcQ9R1yZ8ZLAydD3nCk7MGW= 9kDeo-2B1uC4RzC8PGpFrW-2BMPo2JfRgTW2LA5xx-2Fu9NYkxDeAyFi-2Bd1TeU1v-2Ba60nAn= 5zGeZDsMyaVY-2BZCOvzTJ-2Bi2BgDYET57Ps" alt=3D"" width=3D"1" height=3D"1" bo= rder=3D"0" style=3D"height:1px !important;width:1px !important;border-width= :0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-rig= ht:0 !important;margin-left:0 !important;padding-top:0 !important;padding-b= ottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517643246-21163-461-- --===============5007370723173203534== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot --===============5007370723173203534== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ BackupPC-devel mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/ --===============5007370723173203534==--