glibc error from tar?

Just started seeing the below error and I noticed that the last successful backup was before glibc was updated by upcp on the 9th.

This is legacy backup w/ FTP (I tried switching to the new backup but apparently it works differently w/r/t staging the tar files and I ran out of diskspace).

I just reran the backup using --force and the same error occurred.

Note that the error only happens for one of the accounts on this system.

Code:

WARN: Warnings(s) encountered in tar during archiving:
*** glibc detected *** pkgacct - username - av: 3: double free or corruption (out): 0x000000001f178400 ***
======= Backtrace: =========
/lib64/libc.so.6[0x2b4174fc34af]
/lib64/libc.so.6(cfree+0x4b)[0x2b4174fc77ab]
/lib64/libc.so.6(closedir+0xd)[0x2b4174fe813d]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/x86_64-linux-64int/auto/Archive/Tar/Builder/Builder.so[0x2b417a381f52]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/x86_64-linux-64int/auto/Archive/Tar/Builder/Builder.so(b_stack_destroy+0x28)[0x2b417a382ccb]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/x86_64-linux-64int/auto/Archive/Tar/Builder/Builder.so(b_find+0x3bb)[0x2b417a382381]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/x86_64-linux-64int/auto/Archive/Tar/Builder/Builder.so[0x2b417a383725]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/5.14.4/x86_64-linux-64int/CORE/libperl.so(Perl_pp_entersub+0x8a1)[0x2b41741d9e36]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/5.14.4/x86_64-linux-64int/CORE/libperl.so(Perl_runops_standard+0x11)[0x2b41741d8641]
/usr/local/cpanel/3rdparty/perl/514/lib64/perl5/5.14.4/x86_64-linux-64int/CORE/libperl.so(perl_run+0x1c0)[0x2b417418acd6]
pkgacct - username - av: 3(main+0xa7)[0x400ddf]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2b4174f6f9f4]
pkgacct - username - av: 3[0x400c89]

 

Hi Michael,

Nothing unusual in /var/log/messages. /var/log/dmesg is empty.

This is a VPS but it's very lightly loaded, not even close to any memory limits, and there are much larger accounts before and after this one that are archived and backed up just fine.

FWIW - The recent update to 11.46.0 build 17 didn't seem to help.

Thanks.

 

Thanks Michael. Ticket 5779819 submitted.

 

The end user ended up deleting the folder in question. It is somewhat odd that the issue only recently surfaced and that folder's permissions have been set restrictive for years now. Also, other folders in other users are similarly restrictive and backup does not throw glibc errors for those users.

Anyway, backup is now successful and the user is happy.