Re: [BackupPC-users] Unable to connect on port -1
I'll clarify a bit: the Backup.sock and LOCK file deletions were a long
shot that just happened to work. I noticed that those files were there with
the service stopped, and my suspicion / reasoning was that perhaps backuppc
was having trouble generating the socket because those represented a hung /
locked / otherwise old session. Deleting them worked a couple times (stop
service, delete, start service) but that seems to have stopped working as
well.
I will check NFS version, perhaps the NAS has started defaulting to v4, but
I can't be sure. In the past, mounting without nock on a synology NAS (I've
gone through a couple, issue happened on an old WD nas as well) would cause
a load average spike that would make Backuppc appear unstable, so my
default for many years has been nolock.
~Phil
On Sun, Jun 28, 2020, 6:45 PM Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
> 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/
>
___
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] Unable to connect on port -1
G.W. Haywood via BackupPC-users wrote at about 14:16:15 +0100 on Monday, June 29, 2020: > Hi there, > > On Mon, 29 Jun 2020, Craig Barratt wrote: > > > ... > > 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. > > ... > > I would go further than that. My feeling is that NFS is not suitable > for something so important as your backups. > That being said I ran BackupPC successfully for almost a decade using NFS-v3 to store the backups on a small under-powered/under-memory ARM-based NAS. Never had a problem with lock files... ___ 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] Unable to connect on port -1
For what it is worth, I have been using an nfs mount to hold the pool files for both BPC V3 and V4. This is the fstab entry: 192.168.1.80:/mnt/HD/HD_a2/POOLS /home/disks/nasPOOLS nfs nolock,rw,suid 0 0 The man page nfs(5) explains that nolock does not turn off locking completely. On 2020-06-29 6:16 a.m., G.W. Haywood via BackupPC-users wrote: Hi there, On Mon, 29 Jun 2020, Craig Barratt wrote: ... 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. ... I would go further than that. My feeling is that NFS is not suitable for something so important as your backups. ___ 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] Unable to connect on port -1
Hi there, On Mon, 29 Jun 2020, Craig Barratt wrote: ... 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. ... I would go further than that. My feeling is that NFS is not suitable for something so important as your backups. -- 73, Ged. ___ 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] Unable to connect on port -1
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/
