Backup rsync kill
Hi,
I'm force backup because i receive error after finish backup. I already mount the nas and able to see on OS level.
This server got high load due to shared hosting using cpanel. This the error:
Is it because of high load, it send kill signal? Advice needed. Thanks.
[2016-06-21 09:11:25 +0800] info [backup] Detected "/backup" in /etc/fstab
[2016-06-21 09:11:25 +0800] info [backup] Mount found: 10.0.28.15:/mnt/msa60-2tb/sdg1/sv2.domain.net on /backup type nfs (rw,vers=4,addr=10.0.28.15,clientaddr=10.0.28.70)
[2016-06-21 09:11:26 +0800] info [backup] Setting I/O priority to reduce system load: none: prio 0
lstat() on filehandle $_[...] at /usr/local/cpanel/Cpanel/Autodie.pm line 417.
[2016-06-21 09:11:26 +0800] info [backup] Hard Linking available on "/backup"
[2016-06-21 09:11:26 +0800] info [backup] Running dir & file backup with target : /backup/incremental/system
cpuwatch (Tue Jun 21 09:11:29 2016): System load is currently 5.49; waiting for it to go down to 3.50 to continue "
cpuwatch (Tue Jun 21 09:14:04 2016): System load is currently 3.45, which is below the threshold of 3.50. Continuing "
cpuwatch (Tue Jun 21 09:14:19 2016): System load is currently 3.51; waiting for it to go down to 3.50 to continue "
cpuwatch (Tue Jun 21 09:51:14 2016): System load is currently 3.33, which is below the threshold of 3.50. Continuing "
cpuwatch (Tue Jun 21 09:51:19 2016): System load is currently 3.87; waiting for it to go down to 3.50 to continue "
cpuwatch (Tue Jun 21 09:52:14 2016): System load is currently 3.46, which is below the threshold of 3.50. Continuing "
cpuwatch (Tue Jun 21 09:52:24 2016): System load is currently 3.55; waiting for it to go down to 3.50 to continue "
cpuwatch (Tue Jun 21 09:52:56 2016): System load is currently 3.18, which is below the threshold of 3.50. Continuing "
cpuwatch (Tue Jun 21 09:52:59 2016): System load is currently 3.81; waiting for it to go down to 3.50 to continue "
cpuwatch (Tue Jun 21 09:53:30 2016): System load is currently 3.01, which is below the threshold of 3.50. Continuing "
cpuwatch (Tue Jun 21 09:54:19 2016): System load is currently 4.95; waiting for it to go down to 3.50 to continue "
cpuwatch (Tue Jun 21 10:05:19 2016): System load is currently 3.44, which is below the threshold of 3.50. Continuing "
cpuwatch (Tue Jun 21 10:05:24 2016): System load is currently 4.13; waiting for it to go down to 3.50 to continue "
[2016-06-21 10:25:11 +0800] warn [backup] (XID br4vq8) "/usr/bin/rsync" ended prematurely because it received the "KILL" (9) signal. at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 219.
Cpanel::Backup::Utility::__ANON__(Cpanel::Exception::ProcessFailed::Signal=HASH(0x1bab880)) called at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Try/Tiny.pm line 103
Try::Tiny::try(CODE(0x33b42c8), Try::Tiny::Catch=REF(0x33b4400), Try::Tiny::Finally=REF(0x33d5858)) called at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 229
Cpanel::Backup::Utility::cpusystem(Cpanel::Backup::Utility=HASH(0x3247e50), "rsync", "-rlptD", "--exclude=lastrun/*", "--exclude=bwusagecache/*", "--exclude=serviceauth/*", "--exclude=dnsrequests_db/*", "--exclude=configs.cache/*", "--delete", ...) called at ./backup line 1001
bin::backup::backup_system_files("/backup/incremental/system") called at ./backup line 583
bin::backup::__ANON__() called at ./backup line 591
bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Try/Tiny.pm line 80
eval {...} called at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Try/Tiny.pm line 71
Try::Tiny::try(CODE(0x30d8168), Try::Tiny::Catch=REF(0x33b1b68)) called at ./backup line 601
bin::backup::_process_backups(HASH(0x31dbd48)) called at ./backup line 323
bin::backup::run("bin::backup", "--force") called at ./backup line 102
[2016-06-21 10:25:11 +0800] warn [backup] Failed to perform incremental backup of "/var/cpanel/" to "/backup/incremental/system/dirs/_var_cpanel". at ./backup line 1004.
bin::backup::backup_system_files("/backup/incremental/system") called at ./backup line 583
bin::backup::__ANON__() called at ./backup line 591
bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Try/Tiny.pm line 80
eval {...} called at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Try/Tiny.pm line 71
Try::Tiny::try(CODE(0x30d8168), Try::Tiny::Catch=REF(0x33b1b68)) called at ./backup line 601
bin::backup::_process_backups(HASH(0x31dbd48)) called at ./backup line 323
bin::backup::run("bin::backup", "--force") called at ./backup line 102
cpuwatch (Tue Jun 21 10:25:11 2016): System load is currently 4.97; waiting for it to go down to 3.50 to continue "
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(546) [sender=3.0.6]
rsync: writefd_unbuffered failed to write 77 bytes to socket [receiver]: Broken pipe (32)
[2016-06-21 10:25:19 +0800] info [backup] Final state is Backup::PartialFailure (TERM)
[2016-06-21 10:25:20 +0800] info [backup] Sent Backup::PartialFailure notification.
Is it because of high load, it send kill signal? Advice needed. Thanks.
-
Hello, You can change the threshold setting through WHM. Go to "Main >> Server Configuration >> Tweak Settings" and change setting "threshold " to the load you want, this will make the cpanel backup to run under the load limit you've just set. 0 -
Hello, Yes, as mentioned, you can alter the load average at which backups are suspended via the "Extra CPUs for server load" option under the "Stats and Logs" tab in "WHM >> Tweak Settings". Per it's description: This setting allows you to specify a value to add to the number of physical CPUs in your server. The sum of these two numbers becomes the value at which the cpuwatch, cpanellogd, backups, and CPU statistics daemons consider the system to be in a critical load state. This setting defaults to 0.
Or, if that's an unusual load average, you can find information on troubleshooting the load itself at: Troubleshooting high server loads on Linux servers Thank you.0
Please sign in to leave a comment.
Comments
2 comments