Hello,
We started having trouble with cPanel backups on multiple servers. Because of this error, the backup directories don't get pruned (although I know that can be controlled, but I don't want to change it, as that might leave only corrupted backups for some users). Looking at the logs, I see the following:
This error now appears on multiple servers. Is there something that I should check for the specific users that are getting this error during the backup process?
Thank you.
We started having trouble with cPanel backups on multiple servers. Because of this error, the backup directories don't get pruned (although I know that can be controlled, but I don't want to change it, as that might leave only corrupted backups for some users). Looking at the logs, I see the following:
Code:
[2017-10-28 09:12:28 +0300] info [backup] checking backup for my_cpanel_user
[2017-10-28 09:12:28 +0300] info [backup] Backups ARE enabled for my_cpanel_user
[2017-10-28 09:12:28 +0300] info [backup] Calling pkgacct under cpuwatch to backup user “my_cpanel_user”
[2017-10-28 09:12:28 +0300] pkgacct started.
[2017-10-28 09:12:28 +0300] pkgacct version 10 - user : my_cpanel_user - tarball: 1 - target mysql : default - split: 0 - incremental: 0 - homedir: 1 - mailman: 1 - backup: 1 - archive version: 3 - running with uid 0
[2017-10-28 09:12:28 +0300] pkgacct using '/usr/local/cpanel/3rdparty/bin/pigz -1 --processes 4 --blocksize 4096 --rsyncable' to compress archives
[2017-10-28 09:12:28 +0300] pkgacct working dir : /backup/2017-10-28/accounts/my_cpanel_user
[2017-10-28 09:12:28 +0300] Copying Reseller Config...[2017-10-28 09:12:28 +0300] Done
[2017-10-28 09:12:28 +0300] Copying Suspension Info (if needed)...[2017-10-28 09:12:28 +0300] Done
[2017-10-28 09:12:28 +0300] Copying SSL certificates, CSRs, and keys...[2017-10-28 09:12:45 +0300]
[2017-10-28 09:12:45 +0300] warn [backup] (XID cy6gu3) “/usr/local/cpanel/bin/pkgacct” reported error code “1” when it ended: at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 225.
Cpanel::Backup::Utility::__ANON__(Cpanel::Exception::ProcessFailed::Error=HASH(0x1813ee8)) called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 119
Try::Tiny::try(CODE(0x18177b0), Try::Tiny::Catch=REF(0x1817f18), Try::Tiny::Finally=REF(0x1813bd0)) called at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 235
Cpanel::Backup::Utility::cpusystem(Cpanel::Backup::Utility=HASH(0x23cfa88), "pkgacct", "my_cpanel_user", "/backup/2017-10-28/accounts", "backup") called at /usr/local/cpanel/bin/backup line 1530
bin::backup::backup_accounts("/backup/2017-10-28/accounts") called at /usr/local/cpanel/bin/backup line 770
bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 777
bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 98
eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 89
Try::Tiny::try(CODE(0x2493438), Try::Tiny::Catch=REF(0x24e3d38)) called at /usr/local/cpanel/bin/backup line 787
bin::backup::_process_backups(HASH(0x231a0b0)) called at /usr/local/cpanel/bin/backup line 329
bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 108
[2017-10-28 09:12:45 +0300] warn [backup] Failed to back up account “my_cpanel_user”. at /usr/local/cpanel/bin/backup line 1534.
bin::backup::backup_accounts("/backup/2017-10-28/accounts") called at /usr/local/cpanel/bin/backup line 770
bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 777
bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 98
eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 89
Try::Tiny::try(CODE(0x2493438), Try::Tiny::Catch=REF(0x24e3d38)) called at /usr/local/cpanel/bin/backup line 787
bin::backup::_process_backups(HASH(0x231a0b0)) called at /usr/local/cpanel/bin/backup line 329
bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 108
This error now appears on multiple servers. Is there something that I should check for the specific users that are getting this error during the backup process?
Thank you.