I received mail-The process “/usr/bin/pigz -f /home/backup/2025-09-15/system/files/_etc_apache2_conf_httpd.conf” stalled while it ran for user “root”.
Hello,
I have cPanel&WHM version 128.0.21. This mornig I received email
The process “/usr/bin/pigz -f /home/backup/2025-09-15/system/files/_etc_apache2_conf_httpd.conf” stalled while it ran for user “root”.
The process has run for “6 hours and 1.16 seconds”.
At the time that the system generated this notification, the process had a PID of “237777”, and it consumed 0.01% of the system’s memory and 0% of the system’s CPU time.
The server’s current health statistics are:
Notification Type stall 🚦
Server xxxx
Primary IP Address x.x.x.x
Service cpuwatch
Memory Information Used 3.35 GB
Available 19.92 GB
Installed 23.27 GB
I put xxxx for server name and ip address for security reason...
In backup logs I see
[root@xxxx cpbackup]# more 1757894402.log
[2025-09-15 02:00:02 +0200] info [backup] Setting I/O priority to reduce system load: best-effort: prio 6
[2025-09-15 02:00:06 +0200] info [backup] Pruning metadata for backup at /home/backup/2025-09-15
[2025-09-15 02:00:06 +0200] info [backup] Creating metadata index for backup at /home/backup/2025-09-15
[2025-09-15 02:00:06 +0200] info [backup] Hard Linking available on "/home/backup"
[2025-09-15 02:00:06 +0200] info [backup] Running dir & file backup with target : /home/backup/2025-09-15/system
cpuwatch (Mon Sep 15 02:00:06 2025): System load is currently 4.36; waiting for it to go down below 1.75 to continue …
Should I kill that process? Should I manually start the backup?
Best regards,
Elizabeta
-
Hey there! The backup is paused on your system because the server load is too high. You can read about how that value is calculated here:
https://support.cpanel.net/hc/en-us/articles/360049877314-Prevent-slow-backups-due-to-high-load
but once the load goes down the backups will continue as expected.
If this is higher than normal load for the machine I would recommend investigating that rather than killing the backup process as that would get to the root of the issue.
0 -
The backup process using pigz stalled likely due to high system load, as shown in the logs. Yes, you can safely kill the process and manually restart the backup once the load is lower.
0 -
Hello,
Thank you all for your answers. Now load is ok, and the backup is running normally.
Best regards,
Elizabeta0
Please sign in to leave a comment.
Comments
3 comments