package backuppc 3.3.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
backuppc (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
backuppc is not taking backups
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: backuppc 3.3.0-1ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.19
AptOrdering:
backuppc: Install
backuppc: Configure
Architecture: i386
Date: Tue Jan 19 10:44:44 2016
DuplicateSignature: package:
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageV
dpkg 1.17.5ubuntu5.5
apt 1.0.1ubuntu2.10
SourcePackage: backuppc
Title: package backuppc 3.3.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report a bug and sorry for the long delay in replying.
Based on the output from DpkgTerminalLog .txt:
apache2: Syntax error on line 216 of /etc/apache2/ apache2. conf: Could not open configuration file /etc/apache2/ conf-enabled/ backuppc. conf: No such file or directory config. pl config. pl: No such file or directory config. pl.
Your MPM seems to be threaded. Selecting cgid instead of cgi.
Module cgid already enabled
Not replacing deleted config file /etc/backuppc/
* Starting backuppc... [149G grep: /etc/backuppc/
BackupPC cannot be started because important parameters are missing from config.pl.
If you just upgraded BackupPC, please update /etc/backuppc/
It is very likely that this problem was caused by a local configuration issue. The file /etc/backuppc/ config. pl had been deleted before the upgrade process, which caused the backuppc error. There seems to be another error affecting apache2 as well.
For that reason, I am closing this bug as Invalid. Feel free to reopen it if you still experience the issue. Thank you.