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?
________________________________
From: Marc Gilliatt <m.gilli...@live.co.uk>
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 upgrade backuppc to 3.3.2 or later as you suggested?


________________________________
From: Michael Stowe <michael.st...@member.mensa.org>
Sent: 31 January 2018 07:49
To: Marc Gilliatt
Cc: Developers discussion
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - 
NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*


On 2018-01-30 02:27, Marc Gilliatt wrote:

Sincere apologies for the late reply.

You mention that version 3.3.1 doesn’t work with 4.3 of smbclient.

How do I downgrade the smbclient, please?

Unfortunately, that highly depends on your distro and/or flavor or how you'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, 
requiring building from source or alternative repositories.

It might be simpler to upgrade to version 3.3.2 (or later) instead.

IIRC, the issue is that smbclient changed its reporting, so that BackupPC has 
trouble recognizing when the files are actually successfully retrieved, when in 
fact they are.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to