Have been working this on the BackupPC users mailing list, but it's looking more like a general problem in F33's Samba utility, 'smbclient.'
BackupPC is a backup server package that uses Samba, rsync, and other protocols to backup clients, including Windows PC's. Basically, it runs a command like this for a SMB backup of a PC:
/usr/bin/smbclient \\new-pelican\C$ -U backup -E -d 2 -c tarmode\ full -Tc -
Output is piped to BackupPC utilities that unpack and index the backup, and do other housekeeping
My backups have consistently failed since my upgrade to F33 (were working without problems for years before, and most recently on F32).
Looking closely, it appears 'smbclient' is crashing after passing exactly 47 files. (BackupPC then quits after data stops coming in.)
I've run this command at the command-line; it runs for a few seconds then reports a core dump. Gnome shell then prompted me to file a bugzilla, which I have done.
https://bugzilla.redhat.com/show_bug.cgi?id=1900232 "[abrt] samba-client: remove_do_list_queue_head(): smbclient killed by SIGSEGV")
Anybody have further suggestions, please?
On Sun, 22 Nov 2020 13:47:47 -0500 Tim Evans tkevans@tkevans.com wrote:
My backups have consistently failed since my upgrade to F33 (were working without problems for years before, and most recently on F32).
Anybody have further suggestions, please?
I don't know is this is relevant, but ssh in F33 stopped allowing crypto algorithms that are deemed insecure. You can see another thread about this on this list, Re: Post F32->F33 upgrade rsync w ssh fails If smbclient is using ssh, then it could be having the same problem. Here is one workaround.
""" In the meantime, for the sake of expediency, I've issued the following command on the client F33 machines as root: update-crypto-policies --set LEGACY """
See that other thread for more workarounds and fixes.
On Mon, 23 Nov 2020 08:13:27 -0700 stan upaitag@zoho.com wrote:
On Sun, 22 Nov 2020 13:47:47 -0500 Tim Evans tkevans@tkevans.com wrote:
My backups have consistently failed since my upgrade to F33 (were working without problems for years before, and most recently on F32).
Anybody have further suggestions, please?
If smbclient is using ssh, then it could be having the same problem. Here is one workaround.
""" In the meantime, for the sake of expediency, I've issued the following command on the client F33 machines as root: update-crypto-policies --set LEGACY """
PS If this turns out to be your problem, then the cryptographic algorithm you are using is considered insecure enough to be disabled. It might be enough to discourage script kiddies, but any sophisticated attacker will probably be able to access your data (if they want to expend the resources).
On 11/23/20 7:13 AM, stan via users wrote:
On Sun, 22 Nov 2020 13:47:47 -0500 Tim Evans tkevans@tkevans.com wrote:
My backups have consistently failed since my upgrade to F33 (were working without problems for years before, and most recently on F32).
Anybody have further suggestions, please?
I don't know is this is relevant, but ssh in F33 stopped allowing crypto algorithms that are deemed insecure. You can see another thread about this on this list, Re: Post F32->F33 upgrade rsync w ssh fails If smbclient is using ssh, then it could be having the same problem. Here is one workaround.
SMBclient uses the SMB protocol, nothing to do with ssh or crypto algorithms.
-
Samuel Sieb -
stan -
Tim Evans