I removed the BackupPC 4.1.3 tarball's file, and I've installed the
backuppc_3.3.1-2ubuntu3_amd64.deb(my previous version) I got from online. When
I ran it I still receive the following message...
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Job for backuppc.service failed because the control process exited with error
code. See "systemctl status backuppc.service" and "journalctl -xe" for details.
invoke-rc.d: initscript backuppc, action "start" failed.
● backuppc.service - LSB: Launch backuppc server
Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-02-19 09:20:56 GMT; 12ms
Process: 6728 ExecStart=/etc/init.d/backuppc start (code=exited,
Feb 19 09:20:56 backuppc01 systemd: Starting LSB: Launch backuppc server...
Feb 19 09:20:56 backuppc01 backuppc: * Starting backuppc...
Feb 19 09:20:56 backuppc01 backuppc: BackupPC cannot be started because
important parameters are missing from config.pl.
Feb 19 09:20:56 backuppc01 backuppc: If you just upgraded BackupPC,
please update /etc/backuppc/config.pl.
Feb 19 09:20:56 backuppc01 systemd: backuppc.service: Control process
exited, code=exited status=1
Feb 19 09:20:56 backuppc01 systemd: Failed to start LSB: Launch backuppc
Feb 19 09:20:56 backuppc01 systemd: backuppc.service: Unit entered failed
Feb 19 09:20:56 backuppc01 systemd: backuppc.service: Failed with result
dpkg: error processing package backuppc (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
I'm not too sure about what I have done wrong?
From: Michael Stowe <michael.st...@member.mensa.org>
Sent: 16 February 2018 21:52:58
To: General list for user discussion, questions and support
Subject: 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
the control process exited with error code. See "systemctl status
backuppc.service" and "_journalctl_ -_xe_" for details. _With
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
it looks like I'm going to have to re-raid my server and start
Is there any way to roll back to my previous version of BackupPC
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
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