I've hit my wits end on an issue with my backuppc instance. The system ran fine, untouched, for many months. This is an ubuntu 16.0.4 system, running backuppc 3.3.1, installed via apt. When accessing the index (or any other pages), I get the following: Error: Unable to connect to BackupPC server This CGI script (/backuppc/index.cgi) is unable to connect to the BackupPC server on pirate port -1. The error was: unix connect: Connection refused. Perhaps the BackupPC server is not running or there is a configuration error. Please report this to your Sys Admin.
The backuppc & apache services are running, and restarting without error. The backuppc pool (and other important folders, such as log) lives on an NFS mount, and /var/lib/backuppc is symlinked to /mnt/backup. Below is the fstab entry that I use: 10.0.0.4:/backup /mnt/backup nfs users,auto,nolock,rw 0 0 (I'm specifically using nolock, since that can cause a similar issue. Mounting an NFS mount via some of the off the shelf NAS's out there can have performance issues without nolock set.) I've been able to get the instance to start and run briefly by deleting the BackupPC.sock and LOCK files from /var/lib/log, but the instance doesn't stay running for very long (minutes to an hour or two), and the LOG isn't giving me much data. On top of that, deleting those files doesn't always let the service restart. Thoughts? This box lives a pretty stagnent life, nothing tends to change configuration-wise. ~Phil
_______________________________________________ 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/
