The CGI script is trying to connect to the BackupPC server using the
unix-domain socket, which is at $Conf{LogDir}/BackupPC.sock. From your
email, on your system that appears to be /var/lib/log/BackupPC.sock.Are you running nfs v3 or v4? I have had experience with v3 not working reliably with BackupPC (related to buggy lock file behaviour). BackupPC does rely on lock files working, so it's definitely not recommended to turn locking off. You said you deleted the BackupPC.sock file. That would explain why the CGI script can't connect to the server. Why did you delete it? You said "deleting those files doesn't always let the service restart" - deleting those files should not be used to get the server to restart. Craig On Sat, Jun 27, 2020 at 9:26 AM Phil Kennedy < phillip.kenn...@yankeeairmuseum.org> wrote: > 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/ >
_______________________________________________ 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/
