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
Your MPM seems to be threaded. Selecting cgid instead of cgi.
Module cgid already enabled
Not replacing deleted config file /etc/backuppc/config.pl
* Starting backuppc... [149G grep: /etc/backuppc/config.pl: No such file or directory
BackupPC cannot be started because important parameters are missing from config.pl.
If you just upgraded BackupPC, please update /etc/backuppc/config.pl.
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.
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.