If memory serves, the crux of the issue was that smbclient (well, samba in
general) changed the way verbose output was handled. The tar errors
(unexpected end of file) resulted from a samba not reporting the same
number of files (specifically, reporting 0 files backed up as verbose
output was
t 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 <
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
How far of a jump in upgrade did you make to get to Sierra?
Apple switched over the sshd_config to use Authorized_keys rather than
Authorized_keys2 as the home for trusted keypairs several versions ago.
Verify that your sshd config is really doing what you are expecting it to
do. WRT key based
Changing to an NFS mount point isn't any different from the docs that
detail how to change the mount point in general. Create your mount point,
Mount the NFS share, the change /var/lib/backuppc to a softlink to where
ever your new backuppc location is.
(Those the 10,000 foot view. You'll want to
What errors are you seeing? If it's the tar:712 error, that has been
discussed in the list archives; the patch for the recent badlock
vulnerabilities changed samba's verbose output in such a manner that the
backup runs but does not complete successfully. There is a workaround
involving a small
/lib/backuppc nfs rw,hard,intr,nolock 0 0
Thanks for the prompt replies all round. Hopefully others with similar
issues will find the above useful.
regards, Tom
On 24/09/2014 22:33, Phil Kennedy wrote:
Tom,
You may want to try mounting with the 'nolock' option. I had a similar
issue with a D
Tom,
You may want to try mounting with the 'nolock' option. I had a similar
issue with a D-Link NAS. It's a quick and easy fix to try.
~Phil
On 9/24/2014 2:01 PM, Tom Fallon wrote:
Well I've since removed the /etc/fstab as server hung after a reboot but
it did look like this:
Hi,
I recently had a somewhat odd system failure (poorly configured software
RAID) that lead to a *very* old set of BackupPC config files being
loaded. On one windows machine (possibly more), the default SMB share
was reset to C$ instead of E$. The full count keep, plus the min keep
values
all permissions are correct?)
Thanks for the pointers. This event has furthered my belief that
software RAID is crap.
~Phil
On 3/20/2013 12:37 PM, Phil Kennedy wrote:
Hi,
I recently had a somewhat odd system failure (poorly configured software
RAID) that lead to a *very* old set of BackupPC
On 3/20/2013 7:57 PM, Adam Goryachev wrote:
On 21/03/13 10:41, Phil Kennedy wrote:
Self-replying to add a little detail here;
The system that failed is a Red Hat Enterprise system (5.9 at the
moment.) The system has the backuppc (3.2.0) pool living on a Promise
vTrak system in a Software
On 3/20/2013 9:12 PM, Holger Parplies wrote:
Hi,
I've had that happen (except that I noticed before a drive broke) at least
once, and I remember that Les has also. From what I remember of his
explanation (please correct me if I'm wrong), two physical disks concurrently
positioning their
What does df say about your backuppc server's partition usage? IIRC the
usage % is only calculated once a day. Is it possible that your backuppc
installation came across somebody's ripped DVD library / warez
collection / VM server and filled the pool?
~Phil
On 9/12/2011 11:22 AM, Ward...
I ran into something sorta similar. Is your pool stored on an NAS or NFS
share? In our case, RRDTool was unable to get a lock on files in the
pool over the share, and would hang and hang. Sometimes it would time
out, very rarely it would catch the page and load. Backuppc otherwise
worked fine
14 matches
Mail list logo
