On 11/17/20 2:09 PM, Tim Evans wrote:
On 11/15/20 1:37 PM, Tim Evans wrote:
Just upgraded my server to Fedora 33 from F32 via command-line upgrade
process.
Since then, SMB backups of my Windows 10 client are failing
consistently, with this in the log file:
2020-11-15 13:00:02 incr backup started back to 2020-11-14 08:13:18
(backup #845) for share C$
2020-11-15 13:00:05 Got fatal error during xfer (Non-zero exit status
from smbclient)
2020-11-15 13:00:10 Backup aborted (Non-zero exit status from smbclient)
2020-11-15 13:00:10 Removing empty backup #845
Yesterday morning's (prior to F33 upgrade) was successful:
Update from the OP here. Have tried multiple things, with no success,
including:
Upping log level for both BackupPC (BackupPC-4.4.0-2.fc33.x86_64) and
smbclient itself: the former provided loads of info, but nothing about
the *nearly instant* fatal error from 'smbclient' (as shown above, it
takes about 3 seconds)
Downgrading 'smbclient' on the server from
samba-client-4.13.2-1.fc33.x86_64. No change here.
Command-line basic testing of 'smbclient' works fine, BTW:
[root@osprey ~]# smbclient -U backup //new-pelican/c$
Enter backup's password:
Try "help" to get a list of possible commands.
smb: \>
I've also booted the server back to the last remaining F32 kernel.
Nothing changed.
On the Windows 10 client, the update "Feature update to Windows 10,
version 20H2" was installed several days *before* these failures
started, and FOUR successful backups, including a full, have run since
then. None since the F33 upgrade, though.
So, in sum, 'smbclient' is failing almost immediately on startup of a
backup, with no indication as to bad/expired password or other
authentication issue.
Anyone have additional suggestions? Thanks.
Further update from the original poster:
The Samba folks have released an update that purported to contain a fix
for the 'smbclient' crash. (See
https://bugzilla.samba.org/show_bug.cgi?id=14581), and it has been
released as a Fedora 33 update (see
https://bugzilla.redhat.com/show_bug.cgi?id=1892745).
While the seg fault that was occurring appears to have been fixed, I am
still not getting good backups via SMB. Full backups now run for
several hours--pretty much the length of time they were before--but
ultimately fail, with this in the log:
tarExtract: Unexpected end of tar archive (tot = 10993, num = 10240,
errno = , posn = )
tarExtract: Removing partial file
$Recycle.Bin/S-1-5-21-1479735809-3582899389-406748754-1003/$RYTAKUR.eml
[ skipped 60 lines ]
tarExtract: BackupPC_tarExtact aborting (Unexpected end of tar archive)
tarExtract: Done: 1 errors, 47 filesExist, 139478798 sizeExist,
137948090 sizeExistComp, 47 filesTotal, 139478798 sizeTotal, 0 filesNew,
0 sizeNew, 0 sizeNewComp, 10555998 inodeLast
BackupPC_tarExtract exited with fail status 256
Xfer PIDs are now
Got fatal error during xfer (BackupPC_tarExtract exited with fail status
256)
Backup aborted (BackupPC_tarExtract exited with fail status 256)
This seems to suggest many files were passed from smbclient, but
something goes wrong at the end of the process. Wondering if the Samba
fix may have changed something in 'smbclient's exit codes or such?
--
Tim Evans | 5 Chestnut Court
| Owings Mills, MD 21117
| 443-394-3864
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
