Skip to main content

The process has run for “14 hours, 46 minutes, and 22.74 seconds”.

Comments

7 comments

  • cPanelMichael
    Hello, The system stores backup logs and backup error logs in the /usr/local/cpanel/logs/cpbackup/ directory. The log filenames correspond to the second at which the system created them. Could you review the most recent log and verify if you notice any output regarding the backup pausing due to the server's CPU usage? Thank you.
    0
  • fullfatdesigns
    Looking at the process log, it looks like this part is the problem; ~~~ /bin/gtar --use-compress-program/usr/local/cpanel/bin/gzip-wrapper --create --preserve-permissions --file /backup/2017-03-13/system/dirs/_var_cpanel.tar.gz --excludelastrun/ ~~~ Is this what you meant?
    0
  • cPanelMichael
    Hello, That's showing the compression of the system files. I'm referring to the backup logs in general, as that's the best way to help determine why the backup process isn't completing. What's the most recent activity in the logs? Thank you.
    0
  • fullfatdesigns
    Is that possible in the WHM interface? As I can't find it??
    0
  • cPanelMichael
    You can access the backup logs via the command line, through SSH: SSH Access - Documentation - cPanel Documentation Or, if you prefer, feel free to open a support ticket using the link in my signature and we can take a closer look at the backup logs for you. Post the ticket number here if you decide to open a ticket. Thanks!
    0
  • fullfatdesigns
    Thanks cPanelMichael I've opened a ticket (#8300971) Regards
    0
  • cPanelMichael
    Hello, To update, it looks like the process was running for an extended period of time due to the server reaching the load threshold. You may want to consider increasing the following value under the "Stats and Logs" tab in "WHM >> Tweak Settings": Extra CPUs for server load Per it's description: The load average above the number of CPUs at which cpuwatch, cpanellogd, backups, and CPU stats consider the system to be in a critical load state. For example, a server with 4 physical CPUs and a value of 2 in this field will be considered "critical" in these cases once the load reaches 6. This option pauses the backup process if the load average reaches the set value. Thank you.
    0

Please sign in to leave a comment.