Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

cpuwatch failed to report errors to the status file.

Discussion in 'Data Protection' started by amstel, Apr 1, 2019.

  1. amstel

    amstel Member

    Joined:
    Nov 18, 2015
    Messages:
    24
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    UK
    cPanel Access Level:
    Root Administrator
    Hi all,

    Please could you advise why I cannot make a full backup and sent it to a remote destination?
    Please see the backup config and log:

    Code:
    cat /var/cpanel/backups/config
    ---
    BACKUPACCTS: 'yes'
    BACKUPBWDATA: 'no'
    BACKUPDAYS: 0,1,2,3,4,5
    BACKUPDIR: /backup
    BACKUPENABLE: 'yes'
    BACKUPFILES: 'yes'
    BACKUPLOGS: 'yes'
    BACKUPMOUNT: 'no'
    BACKUPSUSPENDEDACCTS: 'no'
    BACKUPTYPE: compressed
    BACKUP_DAILY_ENABLE: 'yes'
    BACKUP_DAILY_RETENTION: 1
    BACKUP_MONTHLY_DATES: 1
    BACKUP_MONTHLY_ENABLE: 'no'
    BACKUP_MONTHLY_RETENTION: 1
    BACKUP_WEEKLY_DAY: 6
    BACKUP_WEEKLY_ENABLE: 'yes'
    BACKUP_WEEKLY_RETENTION: 2
    CHECK_MIN_FREE_SPACE: 1
    DISABLE_METADATA: 'no'
    ERRORTHRESHHOLD: 3
    FORCE_PRUNE_DAILY: 1
    FORCE_PRUNE_MONTHLY: 0
    FORCE_PRUNE_WEEKLY: 1
    GZIPRSYNCOPTS: --rsyncable
    KEEPLOCAL: 1
    LINKDEST: 0
    LOCALZONESONLY: 'no'
    MAXIMUM_RESTORE_TIMEOUT: 41600
    MAXIMUM_TIMEOUT: 50000
    MIN_FREE_SPACE: 15
    MIN_FREE_SPACE_UNIT: percent
    MYSQLBACKUP: accounts
    POSTBACKUP: 'no'
    PREBACKUP: -1
    PSQLBACKUP: 'no'
    Code:
    ....................cpuwatch (Mon Apr  1 04:41:04 2019): System load is currently 2.66; waiting for it t                                         o go down below 2.62 to continue …
    cpuwatch (Mon Apr  1 04:41:35 2019): System load is currently 1.66, which is below the threshold of 2.62                                         . Continuing …
    ............................................................
    ................................................................................
    [2019-04-01 04:48:06 +0100] Done
    [2019-04-01 04:48:06 +0100] pkgacctfile is: /backup/2019-04-01/accounts/privacy.tar.gz
    [2019-04-01 04:48:06 +0100]
    [2019-04-01 04:48:06 +0100] size is: 35719950175
    [2019-04-01 04:48:06 +0100]
    [2019-04-01 04:48:06 +0100] homesize is: 55281803264
    [2019-04-01 04:48:06 +0100]
    [2019-04-01 04:48:06 +0100] homefiles is: 380377
    [2019-04-01 04:48:06 +0100] pkgacct completed
    [2019-04-01 04:48:07 +0100] warn [backup] (XID 3zkshh) The command “/usr/local/cpanel/bin/cpuwatch” fail                                         ed to report errors to the status file. at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 230.
            Cpanel::Backup::Utility::__ANON__(Cpanel::Exception=HASH(0x37aca08)) called at /usr/local/cpanel                                         /3rdparty/perl/528/lib/perl5/cpanel_lib/Try/Tiny.pm line 118
            Try::Tiny::try(CODE(0x354f998), Try::Tiny::Catch=REF(0x37fbd28), Try::Tiny::Finally=REF(0x37f314                                         8)) called at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 240
            Cpanel::Backup::Utility::cpusystem(Cpanel::Backup::Utility=HASH(0x355a8b0), "pkgacct", "croydond                                         ", "/backup/2019-04-01/accounts", "backup") called at /usr/local/cpanel/bin/backup line 1698
            bin::backup::backup_accounts("/backup/2019-04-01/accounts") called at /usr/local/cpanel/bin/back                                         up line 916
            bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 923
            bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/Try/T                                         iny.pm line 97
            eval {...} called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/Try/Tiny.pm line 8                                         8
            Try::Tiny::try(CODE(0x2d34740), Try::Tiny::Catch=REF(0x36f74f0)) called at /usr/local/cpanel/bin                                         /backup line 933
            bin::backup::_process_backups(HASH(0x3499b88)) called at /usr/local/cpanel/bin/backup line 380
            bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 122
    [2019-04-01 04:48:07 +0100] warn [backup] Failed to back up account “privacy”. at /usr/local/cpanel/bin                                         /backup line 1702.
            bin::backup::backup_accounts("/backup/2019-04-01/accounts") called at /usr/local/cpanel/bin/back                                         up line 916
            bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 923
            bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/Try/T                                         iny.pm line 97
            eval {...} called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/Try/Tiny.pm line 8                                         8
            Try::Tiny::try(CODE(0x2d34740), Try::Tiny::Catch=REF(0x36f74f0)) called at /usr/local/cpanel/bin                                         /backup line 933
            bin::backup::_process_backups(HASH(0x3499b88)) called at /usr/local/cpanel/bin/backup line 380
            bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 122
    [2019-04-01 04:48:07 +0100] info [backup] Queuing transport of meta file: /backup/2019-04-01/accounts/.m                                         aster.meta
    [2019-04-01 04:48:07 +0100] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:1814
    [2019-04-01 04:48:09 +0100] info [backup] leaving queue_backup_transport_item
    [2019-04-01 04:48:09 +0100] info [backup] Queuing transport of file: /backup/2019-04-01/backup_incomplet                                         e
    [2019-04-01 04:48:09 +0100] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:1815
    [2019-04-01 04:48:09 +0100] info [backup] leaving queue_backup_transport_item
    [2019-04-01 04:48:09 +0100] info [backup] Pruning backup directory: /backup/2019-03-31
    [2019-04-01 04:48:13 +0100] info [backup] Queuing prune operation for remote destination daily backups
    [2019-04-01 04:48:13 +0100] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:1816
    [2019-04-01 04:48:13 +0100] info [backup] leaving queue_backup_transport_item
    [2019-04-01 04:48:13 +0100] info [backup] Scheduling backup metadata vacuum
    [2019-04-01 04:48:14 +0100] info [backup] Queuing transport reporter
    [2019-04-01 04:48:14 +0100] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:1817
    [2019-04-01 04:48:14 +0100] info [backup] leaving queue_backup_transport_item
    [2019-04-01 04:48:14 +0100] info [backup] Completed at Mon Apr  1 04:48:14 2019
    [2019-04-01 04:48:14 +0100] info [backup] Final state is Backup::PartialFailure (0)
    [2019-04-01 04:48:14 +0100] info [backup] Sent Backup::PartialFailure notification.
     
  2. cPanelLauren

    cPanelLauren Forums Analyst II Staff Member

    Joined:
    Nov 14, 2017
    Messages:
    6,473
    Likes Received:
    505
    Trophy Points:
    263
    Location:
    Houston
    cPanel Access Level:
    DataCenter Provider
    Hi @amstel

    Looking through our ticket system for examples of this issue, in every case we have present it notes that during the backup process the disk became full which is what lead to the inability for the status file to be updated:

    Code:
    warn [backup] (XID 3zkshh) The command “/usr/local/cpanel/bin/cpuwatch” failed to report errors to the status file.
    Is it possible this occurred on the server?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    amstel likes this.
  3. amstel

    amstel Member

    Joined:
    Nov 18, 2015
    Messages:
    24
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    UK
    cPanel Access Level:
    Root Administrator
    Hi Lauren,

    Thank you for your reply.

    My problem was caused by an entry in root's cron:
    /var/spool/cron/root

    0 * * * * /usr/sbin/tmpwatch --mtime --all 1 /tmp

    tmpwatch is a 3rd party tool and does not come with cPanel.
     
    cPanelLauren likes this.
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice