On 19/10/2018 18:53, Craig Barratt wrote:
I'd recommend temporarily removing $Conf{DumpPostUserCmd}, and also reducing the smbclient debug
level ("-d 5") to 1 ("-d 1") in $Conf{SmbClientFullCmd} and
$Conf{SmbClientIncrCmd}.
Hello Craig,
Alas, it's getting worse...
The following hosts had
>
> Here you go... it could be the net shutdown command failing perhaps?
My initial reaction was yes, but a bad exit status from DumpPostUserCmd
will only cause the backup to be considered bad
if $Conf{UserCmdCheckStatus} is non-zero. If it were, there should be an
error message saying so. Can
On 18/10/2018 16:56, Craig Barratt wrote:
It seems the XferLOG file is very short. Can you just send the whole thing
please?
Here you go... it could be the net shutdown command failing perhaps?
Running: /usr/bin/smbclient 192.168.0.101\\BackupPC-Test -U XX -E -d 5
-c tarmode\ full
It seems the XferLOG file is very short. Can you just send the whole thing
please?
It appears just one 63 byte file gets transferred. Is Test.txt the only
file in the BackupPC-Test share?
BackupPC 3.3.1 with smb transfers checks for either of these two strings:
"tar_process done, err = 0" and
On 18/10/2018 14:13, Paul Littlefield wrote:
Ah, logged in and this is the samba smbclient command line...
and this is the end of the XferLOG file...
Domain=[PC] OS=[Windows 7 Home Premium 7601 Service Pack 1] Server=[Windows 7
Home Premium 6.1]
session setup ok
tconx ok
tar:316 tarmode
On 18/10/2018 13:50, Paul Littlefield wrote:
I cannot read any of the XferLOG files, there are in .z format
Ah, logged in and this is the samba smbclient command line...
Running: /usr/bin/smbclient 192.168.0.101\\BackupPC-Test -U User -E -d 5 -c
tarmode\ full -Tc -
full backup started
On 13/10/2018 18:20, Craig Barratt wrote:
Paul,
Sorry, I really misinterpreted the error message ("tar_process done, err = 0")
you sent. It's from smbclient, not tar.
What version of smbclient are you running? What is the smbclient command line
(near the top of the XferLOG file)? What are
On 13/10/2018 18:20, Craig Barratt wrote:
Paul,
Sorry, I really misinterpreted the error message ("tar_process done, err = 0")
you sent. It's from smbclient, not tar.
What version of smbclient are you running? What is the smbclient command line
(near the top of the XferLOG file)? What are
entFullCmd} and $Conf{SmbClientIncrCmd}? Do both
incremental and full backups fail with the same error?
Craig
On Fri, Oct 12, 2018 at 5:46 AM Holger Parplies wrote:
> Hi,
>
> Paul Littlefield wrote on 2018-10-12 12:22:48 +0000 [Re: [BackupPC-users]
> fatal error during xfer (tar:632)]:
&
Hi,
Paul Littlefield wrote on 2018-10-12 12:22:48 + [Re: [BackupPC-users] fatal
error during xfer (tar:632)]:
> On 11/10/2018 23:44, Craig Barratt wrote:
> >[...]
> >What version of tar are you using? Can you run gnu tar instead (that's the
> >default under cygwin)
On 11/10/2018 23:44, Craig Barratt wrote:
Paul,
BackupPC looks at the status / summary messages from tar to determine if the
transfer completed successfully. That means it depends on the type and version
of tar you are using.
It's reporting that the last output line from tar was "632
Paul,
BackupPC looks at the status / summary messages from tar to determine if
the transfer completed successfully. That means it depends on the type and
version of tar you are using.
It's reporting that the last output line from tar was "632 tar_process
done, err = 0". I don't think that's a
Hello List,
I am getting this error during backup from a Windows 7 Professional PC...
2018-10-08 20:31:03 Got fatal error during xfer (tar:632 tar_process done, err
= 0)
2018-10-08 20:31:08 Backup aborted (tar:632 tar_process done, err = 0)
...is anything wrong?
Thanks,
Paul
Ubuntu Linux
so I'll answer my own question:
the problem was the option --dry-run.
When the files are actually being copied, no such error occurs.
A.
On 04.12.2013 22:29, Andrzej wrote:
Hello,
I have a BackupPC installation (v.3.2.1) on a Debian Wheezy and I'm
trying to backup a bunch of files from
Hello,
I have a BackupPC installation (v.3.2.1) on a Debian Wheezy and I'm
trying to backup a bunch of files from Windows 2008 server.
There is a 64bit cwRsync installed on the Windows side, running as a
service.
When I start the test run of the full backup, it breaks after a while,
showing an
I had been using backuppc for about a year without any problems. I upgraded to
karmic from jaunty and I started having problems. I have been fighting with
this for weeks and today I completely removed backuppc along with the config
files and reinstalled. I am still running into the same
Hi there,
I had been using backuppc for about a year without any problems. I
upgraded to karmic from jaunty and I started having problems. I have
been fighting with this for weeks and today I completely removed
backuppc along with the config files and reinstalled. I am still
running into the
I was able to get backuppc to work. I had forgotten to add /var/lib/backuppc to
my excluded files.
newsboy wrote:
I had been using backuppc for about a year without any problems. I upgraded
to karmic from jaunty and I started having problems. I have been fighting
with this for weeks and
Steve Blackwell wrote:
Adam Goryachev [EMAIL PROTECTED] wrote:
Set the full path to sudo eg /bin/sudo
Maybe that will help.
Regards,
Adam
Thanls for the suggestion but I still get the same error.
Is your sudo binary really /bin/sudo? On our CentOS machines 'which
sudo' returns
Well, I changed to use the correct full path for sudo and now I get this error:
Contents of file /media/disk/pc/steve/XferLOG.bad.z, modified 2008-07-29
12:25:04
Running: /usr/bin/sudo /bin/tar -c -v -f - -C / --totals --newer=2008-07-27\
17:56:09 .
incr backup started back to 2008-07-27
Steve wrote:
Well, I changed to use the correct full path for sudo and now I get
this error:
Contents of file /media/disk/pc/steve/XferLOG.bad.z, modified
2008-07-29
12:25:04
Running: /usr/bin/sudo /bin/tar -c -v -f - -C / --totals --
newer=2008-07-27\
17:56:09 .
incr backup
Steve wrote:
Well, I changed to use the correct full path for sudo and now I get
this error:
Contents of file /media/disk/pc/steve/XferLOG.bad.z, modified
2008-07-29
12:25:04
Running: /usr/bin/sudo /bin/tar -c -v -f - -C / --totals --
newer=2008-07-27\
17:56:09 .
incr backup
I just installed BackupPC and I started by attempting to backup just my
local machine which is also the BackupPC server.
Since this is a local machine I don't need ssh so I set my TarClientCmd
to $tarPath -c -v -f - -C $shareName+ --totals. This worked OK but
some directories were not backed up
Adam Goryachev [EMAIL PROTECTED] wrote:
Set the full path to sudo eg /bin/sudo
Maybe that will help.
Regards,
Adam
Thanls for the suggestion but I still get the same error.
Stev e.
Steve Blackwell wrote:
I just installed BackupPC and I started by attempting to backup
just
Steve writes:
Since this is a local machine I don't need ssh so I set my TarClientCmd
to $tarPath -c -v -f - -C $shareName+ --totals. This worked OK but
some directories were not backed up because the user, backuppc, doesn't
have root privileges. Next I set up sudo to allow backuppc to run
25 matches
Mail list logo
