Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
On 2018-03-01 07:22, Marc Gilliatt wrote: So I've since removed every instance of BackupPC from my server, all my backups and config files have gone. I have installed BackupPC 4 from a script I've seen from Github, and I cannot connect to the GUI whatsoever, it mentions on the webpage... _Not Found_ _The requested URL /BackupPC_Admin was not found on this server._ _Apache/2.4.18 (Ubuntu) Server at 10.16.0.163 Port 80_ I have also seen that the BackupPC service is still not running... _● backuppc.service_ _ Loaded: not-found (Reason: No such file or directory)_ _ Active: failed (Result: exit-code) since Tue 2018-02-20 12:44:10 GMT; 1 weeks 2 days ago_ _Feb 20 12:44:10 backuppc01 systemd[1]: Starting LSB: Launch backuppc server..._ _Feb 20 12:44:10 backuppc01 backuppc[45980]: Starting backuppc: 2018-02-20 12:44:10 Another BackupPC is running (pid 45589); quitting..._ _Feb 20 12:44:10 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1_ _Feb 20 12:44:10 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server._ _Feb 20 12:44:10 backuppc01 systemd[1]: backuppc.service: Unit entered failed state._ _Feb 20 12:44:10 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'._ _Mar 01 13:26:37 backuppc01 systemd[1]: Stopped LSB: Launch backuppc server._ I feel like I've tried everything to resolve this issue regarding a simple upgrade of this software. I feel my last resort now is to completely re-raid my server and start fresh with a new install of Ubuntu and BackupPC. Is there anything I can do to get BackupPC to work, please? - In a nutshell, what's going on is an aborted or crashed BackupPC instance left behind its PID file, which will need to be cleaned up before BackupPC will start. (As you can imagine, having more than a single instance running at a time is a bad idea.) If you're certain it's not running, you'll find the relevant files in RunDir, set at installation time and defined in config.pl. In my installation, this is '/var/run/BackupPC' but different installers/distros make different assumptions. -- 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!
So I've since removed every instance of BackupPC from my server, all my backups and config files have gone. I have installed BackupPC 4 from a script I've seen from Github, and I cannot connect to the GUI whatsoever, it mentions on the webpage... Not Found The requested URL /BackupPC_Admin was not found on this server. Apache/2.4.18 (Ubuntu) Server at 10.16.0.163 Port 80 I have also seen that the BackupPC service is still not running... ● backuppc.service Loaded: not-found (Reason: No such file or directory) Active: failed (Result: exit-code) since Tue 2018-02-20 12:44:10 GMT; 1 weeks 2 days ago Feb 20 12:44:10 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Feb 20 12:44:10 backuppc01 backuppc[45980]: Starting backuppc: 2018-02-20 12:44:10 Another BackupPC is running (pid 45589); quitting... Feb 20 12:44:10 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Feb 20 12:44:10 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Feb 20 12:44:10 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Feb 20 12:44:10 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. Mar 01 13:26:37 backuppc01 systemd[1]: Stopped LSB: Launch backuppc server. I feel like I've tried everything to resolve this issue regarding a simple upgrade of this software. I feel my last resort now is to completely re-raid my server and start fresh with a new install of Ubuntu and BackupPC. Is there anything I can do to get BackupPC to work, please? From: Marc Gilliatt <m.gilli...@live.co.uk> Sent: 19 February 2018 09:45:45 To: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! Ive just installed the backuppc 4 from a script I found online from git(https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS). ASfter running the script, Im not longer getting the internal error in the GUI, I am now 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. I feel I am slowly but steadily making progressI'm still unsure on how to correct the issue I'm having with both the GUI and when I run service backuppc status in the command line, I am still getting ● 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:29:16 GMT; 14min ago Docs: man:systemd-sysv-generator(8) Process: 37768 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Feb 19 09:29:16 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Feb 19 09:29:16 backuppc01 backuppc[37768]: * Starting backuppc... Feb 19 09:29:16 backuppc01 backuppc[37768]: BackupPC cannot be started because important parameters are missing from c Feb 19 09:29:16 backuppc01 backuppc[37768]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Feb 19 09:29:16 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Feb 19 09:29:16 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Feb 19 09:29:16 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Feb 19 09:29:16 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. [https://avatars2.githubusercontent.com/u/3910596?s=400=4]<https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS> Installing BackupPC 4 from git on Ubuntu Xenial 16.04 LTS ...<https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS> github.com backuppc - BackupPC is a high-performance, enterprise-grade system for backing up to a server's disk. From: Marc Gilliatt <m.gilli...@live.co.uk> Sent: 19 February 2018 09:22:41 To: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! 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 Lo
Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
I'm having no luck whatsoever with my issue, and I was thinking if I completely uninstalled all of backuppc, every config file etc, could I install the latest version and still keep my previous/archived data, I don't want to lose that? From: Marc Gilliatt <m.gilli...@live.co.uk> Sent: 20 February 2018 08:40:01 To: Michael Stowe; General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! I'm kinda a newbie to all this - how do I extract the relevant scripts from the .deb file and install them by hand, please? From: Michael Stowe <michael.st...@member.mensa.org> Sent: 19 February 2018 22:56:56 To: General list for user discussion, questions and support Cc: Marc Gilliatt Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-19 02:14, Marc Gilliatt wrote: I apologise for the bombardment of email/replies. However, I am able to get into the GUI now after playing about with backuppc. I went to back up my Linux servers and they are failing every time I try to do a full backup, I'm getting the same error for all my Linux servers: Backup aborted (fileListReceive failed) However my Windows share is backing up just fine, I haven't received any errors whatsoever and I've checked the top command and its running a BackupPC_tarExt dump. Surprisingly however, I’m still receiving the same failed error message when I run service backuppc status? - The error you're receiving is fairly generic, you should be able to glean more from the details logs. The big things which make rsync not work are usually authentication and configuration related, but I can't think of a good reason any of that would have changed during an up or downgrade. The service definition is a different matter — if I were to venture a guess, I'd suggest that the upgrade installed v4 service definitions, and the v3 reinstall did not touch them, for whatever reason (there are a number of possibilities: neglecting to run systemctl daemon-reload, v3 doesn't bother if it sees they're already installed, v3 uses the sys5 style instead of systemctl, or v3 tried but failed.) If I were sorting this out on my systems, I'd probably extract the relevant scripts from the .deb file and install them by hand. -- 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!
I'm kinda a newbie to all this - how do I extract the relevant scripts from the .deb file and install them by hand, please? From: Michael Stowe <michael.st...@member.mensa.org> Sent: 19 February 2018 22:56:56 To: General list for user discussion, questions and support Cc: Marc Gilliatt Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-19 02:14, Marc Gilliatt wrote: I apologise for the bombardment of email/replies. However, I am able to get into the GUI now after playing about with backuppc. I went to back up my Linux servers and they are failing every time I try to do a full backup, I'm getting the same error for all my Linux servers: Backup aborted (fileListReceive failed) However my Windows share is backing up just fine, I haven't received any errors whatsoever and I've checked the top command and its running a BackupPC_tarExt dump. Surprisingly however, I’m still receiving the same failed error message when I run service backuppc status? - The error you're receiving is fairly generic, you should be able to glean more from the details logs. The big things which make rsync not work are usually authentication and configuration related, but I can't think of a good reason any of that would have changed during an up or downgrade. The service definition is a different matter — if I were to venture a guess, I'd suggest that the upgrade installed v4 service definitions, and the v3 reinstall did not touch them, for whatever reason (there are a number of possibilities: neglecting to run systemctl daemon-reload, v3 doesn't bother if it sees they're already installed, v3 uses the sys5 style instead of systemctl, or v3 tried but failed.) If I were sorting this out on my systems, I'd probably extract the relevant scripts from the .deb file and install them by hand. -- 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/
Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
On 2018-02-19 01:22, Marc Gilliatt wrote: 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 ago Docs: man:systemd-sysv-generator(8) Process: 6728 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Feb 19 09:20:56 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Feb 19 09:20:56 backuppc01 backuppc[6728]: * Starting backuppc... Feb 19 09:20:56 backuppc01 backuppc[6728]: BackupPC cannot be started because important parameters are missing from config.pl. Feb 19 09:20:56 backuppc01 backuppc[6728]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Feb 19 09:20:56 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. dpkg: error processing package backuppc (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: backuppc E: Sub-process /usr/bin/dpkg returned an error code (1) I'm not too sure about what I have done wrong? It's worth looking at the config.pl to see what happened. It may be zero length, or missing, or the 3->4 upgrade may have partially worked after all. In any of these cases, you need only restore the config.pl from wherever you saved it, and you should be all set. -- 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-19 02:14, Marc Gilliatt wrote: I apologise for the bombardment of email/replies. However, I am able to get into the GUI now after playing about with backuppc. I went to back up my Linux servers and they are failing every time I try to do a full backup, I'm getting the same error for all my Linux servers: Backup aborted (fileListReceive failed) However my Windows share is backing up just fine, I haven't received any errors whatsoever and I've checked the top command and its running a BackupPC_tarExt dump. Surprisingly however, I’m still receiving the same failed error message when I run _service backuppc status_? - The error you're receiving is fairly generic, you should be able to glean more from the details logs. The big things which make rsync not work are usually authentication and configuration related, but I can't think of a good reason any of that would have changed during an up or downgrade. The service definition is a different matter -- if I were to venture a guess, I'd suggest that the upgrade installed v4 service definitions, and the v3 reinstall did not touch them, for whatever reason (there are a number of possibilities: neglecting to run systemctl daemon-reload, v3 doesn't bother if it sees they're already installed, v3 uses the sys5 style instead of systemctl, or v3 tried but failed.) If I were sorting this out on my systems, I'd probably extract the relevant scripts from the .deb file and install them by hand. -- 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!
I apologise for the bombardment of email/replies. However, I am able to get into the GUI now after playing about with backuppc. I went to back up my Linux servers and they are failing every time I try to do a full backup, I'm getting the same error for all my Linux servers: Backup aborted (fileListReceive failed) However my Windows share is backing up just fine, I haven't received any errors whatsoever and I've checked the top command and its running a BackupPC_tarExt dump. Surprisingly however, I’m still receiving the same failed error message when I run service backuppc status? From: Marc Gilliatt <m.gilli...@live.co.uk> Sent: 19 February 2018 09:45:45 To: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! Ive just installed the backuppc 4 from a script I found online from git(https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS). ASfter running the script, Im not longer getting the internal error in the GUI, I am now 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. I feel I am slowly but steadily making progressI'm still unsure on how to correct the issue I'm having with both the GUI and when I run service backuppc status in the command line, I am still getting ● 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:29:16 GMT; 14min ago Docs: man:systemd-sysv-generator(8) Process: 37768 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Feb 19 09:29:16 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Feb 19 09:29:16 backuppc01 backuppc[37768]: * Starting backuppc... Feb 19 09:29:16 backuppc01 backuppc[37768]: BackupPC cannot be started because important parameters are missing from c Feb 19 09:29:16 backuppc01 backuppc[37768]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Feb 19 09:29:16 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Feb 19 09:29:16 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Feb 19 09:29:16 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Feb 19 09:29:16 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. [https://avatars2.githubusercontent.com/u/3910596?s=400=4]<https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS> Installing BackupPC 4 from git on Ubuntu Xenial 16.04 LTS ...<https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS> github.com backuppc - BackupPC is a high-performance, enterprise-grade system for backing up to a server's disk. From: Marc Gilliatt <m.gilli...@live.co.uk> Sent: 19 February 2018 09:22:41 To: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! 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 ago Docs: man:systemd-sysv-generator(8) Process: 6728 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Feb 19 09:20:56 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Feb 19 09:20:56 backuppc01 backuppc[6728]: * Starting backuppc... Feb 19 09:20:56 backuppc01 backuppc[6728]: BackupPC cannot be started because important parameters are missing from config.pl. Feb 19 09:20:56 backuppc01 backuppc[6728]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Feb 19 09:20:56 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Feb 19 09:20:56 backuppc01 s
Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
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 ago Docs: man:systemd-sysv-generator(8) Process: 6728 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Feb 19 09:20:56 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Feb 19 09:20:56 backuppc01 backuppc[6728]: * Starting backuppc... Feb 19 09:20:56 backuppc01 backuppc[6728]: BackupPC cannot be started because important parameters are missing from config.pl. Feb 19 09:20:56 backuppc01 backuppc[6728]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Feb 19 09:20:56 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Feb 19 09:20:56 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. dpkg: error processing package backuppc (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: backuppc 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 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/
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/
Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
Also, I checked the Apache log for every time I reload the GUI, and the error I'm getting is... ==> /var/log/apache2/error.log <== [Fri Feb 16 09:12:41.868457 2018] [cgid:error] [pid 65501:tid 140267832579968] (13)Permission denied: AH01241: exec of '/usr/share/backuppc/cgi-bin/index.cgi' failed [Fri Feb 16 09:12:41.869199 2018] [cgid:error] [pid 65386:tid 140267625625344] [client 10.16.5.21:22444] End of script output before headers: index.cgi ==> /var/log/apache2/access.log <== 10.16.5.21 - backuppc [16/Feb/2018:09:12:41 +] "GET /backuppc/index.cgi?action=summary HTTP/1.1" 500 809 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36" From: Marc Gilliatt <m.gilli...@live.co.uk> Sent: 16 February 2018 09:05:19 To: Michael Stowe Cc: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! 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? From: Michael Stowe <michael.st...@member.mensa.org> Sent: 15 February 2018 06:23:19 To: Marc Gilliatt Cc: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! FROM: Michael Stowe <michael.st...@member.mensa.org> SENT: 13 February 2018 09:01 TO: Marc Gilliatt CC: General list for user discussion, questions and support SUBJECT: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-13 00:34, Marc Gilliatt wrote: So can I just install the tar file again then, and when it asks me for the _Full path to existing main config.pl []? _should I put what you had mentioned? My suggestion is yes, give it a whirl. More accurately, I'd suggest saving a copy of your current config.pl, so you can try again if anything goes awry. Also, depending on what procedure or script you're using, you may want to examine it to see if it has options to update your config.pl or assume you need a new one, as the one from which that command line came. It doesn't need to be done at the same time as the tar installation, but it won't hurt to go through the steps again, either. On 2018-02-14 04:18, Marc Gilliatt wrote: When I try and give it the full path to the config.pl path and I press enter. It's just repeating the path I have given it, it's not moving on to the next step of the installation? Example: --> Full path to existing main config.pl []? /configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC The file ‘/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC’ doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. --> Full path to existing main config.pl [/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC]? The file ‘/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC’ doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. It just keeps repeating itself? I believe I misunderstood what you were asking. When it asks for the full path, just give it the full path to your config.pl, which is likely to be something like /etc/BackupPC/config.pl — I'm not sure what the Ubuntu convention is, so you might need to locate it first. What I provided was a command line that would process a config.pl in the current di
Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
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? From: Michael Stowe <michael.st...@member.mensa.org> Sent: 15 February 2018 06:23:19 To: Marc Gilliatt Cc: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! FROM: Michael Stowe <michael.st...@member.mensa.org> SENT: 13 February 2018 09:01 TO: Marc Gilliatt CC: General list for user discussion, questions and support SUBJECT: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-13 00:34, Marc Gilliatt wrote: So can I just install the tar file again then, and when it asks me for the _Full path to existing main config.pl []? _should I put what you had mentioned? My suggestion is yes, give it a whirl. More accurately, I'd suggest saving a copy of your current config.pl, so you can try again if anything goes awry. Also, depending on what procedure or script you're using, you may want to examine it to see if it has options to update your config.pl or assume you need a new one, as the one from which that command line came. It doesn't need to be done at the same time as the tar installation, but it won't hurt to go through the steps again, either. On 2018-02-14 04:18, Marc Gilliatt wrote: When I try and give it the full path to the config.pl path and I press enter. It's just repeating the path I have given it, it's not moving on to the next step of the installation? Example: --> Full path to existing main config.pl []? /configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC The file ‘/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC’ doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. --> Full path to existing main config.pl [/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC]? The file ‘/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC’ doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. It just keeps repeating itself? I believe I misunderstood what you were asking. When it asks for the full path, just give it the full path to your config.pl, which is likely to be something like /etc/BackupPC/config.pl — I'm not sure what the Ubuntu convention is, so you might need to locate it first. What I provided was a command line that would process a config.pl in the current directory, that you may need to tailor to your current paths. Sorry about the confusion. -- 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!
FROM: Michael Stowe <michael.st...@member.mensa.org> SENT: 13 February 2018 09:01 TO: Marc Gilliatt CC: General list for user discussion, questions and support SUBJECT: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-13 00:34, Marc Gilliatt wrote: So can I just install the tar file again then, and when it asks me for the _Full path to existing main config.pl []? _should I put what you had mentioned? My suggestion is yes, give it a whirl. More accurately, I'd suggest saving a copy of your current config.pl, so you can try again if anything goes awry. Also, depending on what procedure or script you're using, you may want to examine it to see if it has options to update your config.pl or assume you need a new one, as the one from which that command line came. It doesn't need to be done at the same time as the tar installation, but it won't hurt to go through the steps again, either. On 2018-02-14 04:18, Marc Gilliatt wrote: When I try and give it the full path to the config.pl path and I press enter. It's just repeating the path I have given it, it's not moving on to the next step of the installation? Example: --> Full path to existing main config.pl []? /configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC The file '/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC' doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. --> Full path to existing main config.pl [/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC]? The file '/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC' doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. It just keeps repeating itself? I believe I misunderstood what you were asking. When it asks for the full path, just give it the full path to your config.pl, which is likely to be something like /etc/BackupPC/config.pl -- I'm not sure what the Ubuntu convention is, so you might need to locate it first. What I provided was a *command line* that would process a config.pl in the *current* directory, that you may need to tailor to your current paths. Sorry about the confusion. -- 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!
When I try and give it the full path to the config.pl path and I press enter. It's just repeating the path I have given it, it's not moving on to the next step of the installation? Example: --> Full path to existing main config.pl []? /configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC The file '/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC' doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. --> Full path to existing main config.pl [/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC]? The file '/configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --backuppc01 backuppc --html-dir /var/www/html/BackupPC' doesn't exist. Is this a new installation or upgrade for BackupPC? If this is an upgrade please tell me the full path of the existing BackupPC configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just hit return. It just keeps repeating itself? From: Michael Stowe <michael.st...@member.mensa.org> Sent: 13 February 2018 09:01 To: Marc Gilliatt Cc: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-13 00:34, Marc Gilliatt wrote: So can I just install the tar file again then, and when it asks me for the _Full path to existing main config.pl []? _should I put what you had mentioned? My suggestion is yes, give it a whirl. More accurately, I'd suggest saving a copy of your current config.pl, so you can try again if anything goes awry. Also, depending on what procedure or script you're using, you may want to examine it to see if it has options to update your config.pl or assume you need a new one, as the one from which that command line came. It doesn't need to be done at the same time as the tar installation, but it won't hurt to go through the steps again, either. -- 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-13 00:34, Marc Gilliatt wrote: So can I just install the tar file again then, and when it asks me for the _Full path to existing main config.pl []? _should I put what you had mentioned? My suggestion is yes, give it a whirl. More accurately, I'd suggest saving a copy of your current config.pl, so you can try again if anything goes awry. Also, depending on what procedure or script you're using, you may want to examine it to see if it has options to update your config.pl or assume you need a new one, as the one from which that command line came. It doesn't need to be done at the same time as the tar installation, but it won't hurt to go through the steps again, either. -- 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!
So can I just install the tar file again then, and when it asks me for the Full path to existing main config.pl []? should I put what you had mentioned? e.g. --> Full path to existing main config.pl []? /configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --hostname backuppc --html-dir /var/www/html/BackupPC From: Michael Stowe <michael.st...@member.mensa.org> Sent: 12 February 2018 21:28 To: Marc Gilliatt Cc: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-12 12:18, Marc Gilliatt wrote: Thanks for the quick response. How do I update the config.pl file, please? I'm not sure what upgrade instructions you followed, which may have more specific notes, but the usual course of action when installing from the tarball is this: # When upgrading, use this instead: # ./configure.pl --batch --config-path /etc/BackupPC/config.pl I note that in one of the popular Ubuntu upgrade scripts, it's commented just like that, so it may have attempted to install as new. I'm not sure what happens when that's attempted and a config.pl already exists, but if the above doesn't work (remove the # at the beginning of the second line, obviously) then you might want to move your config.pl to a backup and try this: # When installing, use this ./configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --hostname backuppc --html-dir /var/www/html/BackupPC Adjust the paths for your actual paths, of course. -- 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-12 12:18, Marc Gilliatt wrote: Thanks for the quick response. How do I update the config.pl file, please? I'm not sure what upgrade instructions you followed, which may have more specific notes, but the usual course of action when installing from the tarball is this: # When upgrading, use this instead: # ./configure.pl --batch --config-path /etc/BackupPC/config.pl I note that in one of the popular Ubuntu upgrade scripts, it's commented just like that, so it may have attempted to install as new. I'm not sure what happens when that's attempted and a config.pl already exists, but if the above doesn't work (remove the # at the beginning of the second line, obviously) then you might want to move your config.pl to a backup and try this: # When installing, use this ../configure.pl --batch --cgi-dir /var/www/cgi-bin/BackupPC --data-dir /var/lib/backuppc --hostname backuppc --html-dir /var/www/html/BackupPC --html-dir-url /BackupPC --install-dir /usr/local/BackupPC Adjust the paths for your actual paths, of course. -- 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!
Thanks for the quick response. How do I update the config.pl file, please? From: Michael Stowe <michael.st...@member.mensa.org> Sent: 12 February 2018 20:17 To: General list for user discussion, questions and support Cc: Marc Gilliatt Subject: Re: [BackupPC-users] Upgrading to backuppc-4.1.3 FAILED! On 2018-02-12 01:00, Marc Gilliatt wrote: I tried to download backuppc-4.1.3 tar file from the backuppc website. The upgrade went fine, I went through the upgrade steps and no error was shown, however, the 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. And 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 Before the upgrade, I was running smbd 4.3.11-Ubuntu and backuppc 3.3.1-2ubuntu3.3 Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. I have no working backuppc now…any ideas, please? If I may draw your attention to these lines from your logs: 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. The settings in config.pl have changed. These will need to be updated before you will be able to start 4.x. -- 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-12 01:00, Marc Gilliatt wrote: I tried to download backuppc-4.1.3 tar file from the backuppc website. The upgrade went fine, I went through the upgrade steps and no error was shown, however, the 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. And 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_ Before the upgrade, I was running smbd 4.3.11-Ubuntu and backuppc 3.3.1-2ubuntu3.3 Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. I have no working backuppc now...any ideas, please? If I may draw your attention to these lines from your logs: 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. The settings in config.pl have changed. These will need to be updated before you will be able to start 4.x. -- 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/
[BackupPC-users] Upgrading to backuppc-4.1.3 FAILED!
I tried to download backuppc-4.1.3 tar file from the backuppc website. The upgrade went fine, I went through the upgrade steps and no error was shown, however, the 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. And 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 Before the upgrade, I was running smbd 4.3.11-Ubuntu and backuppc 3.3.1-2ubuntu3.3 Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. I have no working backuppc now...any ideas, please? -- 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/
