SOLVED cpbackup Process Will Not Stop

[CorpComm]

Earlier this week, I began receiving load error messages for our cPanel installation and when I investigated, I found that the backups were not completing correctly. We keep one day's worth in the backup directory but there were now multiple folders. After clearing those out, I checked the Process Manager to see if one of the sites got stuck. I began killing each backup process for each site but noticed that they would keep coming back. I disabled the backups and rebooted the server, but found that the backup was still running. I left it for a day to see if it would clear out itself but that didn't happen. I ran a killall command through the command prompt but when I check the processes again, I see cpbackup is still running. In fact I can't kill them at all because the ID# changes immediately.

root 8439 0.0 0.0 12140 1128 pts/0 S+ 09:54 0:00 grep --color=auto cpbackup

root 8448 0.0 0.0 12140 1048 pts/0 S+ 09:54 0:00 grep --color=auto cpbackup

Any ideas on how to stop a runnaway cpbackup? As far as I can tell, no actual backkups are being created but the script is still running. I'm keeping backups disabled for now. I also disabled WordPress Toolkit as I suspected that was part of the problem.

 

[cPRex]

Hey there! Can you check the cPanel backup logs at /usr/local/cpanel/logs/cpbackup to see if there are issues that are keeping it from completing in a normal time? High load on the server, or frequent errors, could cause the backup to run longer than 24 hours, leading to confusion in the backup system when the next run tries to start before the previous run has finished.

 

[CorpComm]

I suppose that's it as I'm seeing a lot of the following in the latest log files.

cpuwatch (Fri May 27 08:13:30 2022): System load is currently 2.94, which is below the threshold of 3.50. Continuing …
..........cpuwatch (Fri May 27 08:14:01 2022): System load is currently 3.55; waiting for it to go down below 3.50 to continue …
cpuwatch (Fri May 27 08:59:42 2022): System load is currently 3.47, which is below the threshold of 3.50. Continuing …
cpuwatch (Fri May 27 08:59:47 2022): System load is currently 3.68; waiting for it to go down below 3.50 to continue …
cpuwatch (Fri May 27 09:18:25 2022): System load is currently 3.43, which is below the threshold of 3.50. Continuing …

I looked at earlier log files before this started and didn't see those messages. So it seems cpbackup is constantly checking to see if the load is low enough to continue. Also explains why the backups weren't cleared since the previous one didn't finish. I'm going to stagger the backups to run every other day until I can determine what's causing the load.

Thanks for the help!

 

[cPRex]

I'm glad that pointed you in the right direction!

 

[CorpComm]

A quick follow up; looks like it was PHP memory limit. I thought I had set to 256MB for each PHP version but the default 128MB was set instead. Increasing the memory has already reduced the CPU down quite a bit. It's just one of those settings that sometimes gets overlooked.