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
13 matches
Mail list logo
