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!

Backup completes with error

Discussion in 'Data Protection' started by kalexan, May 13, 2018.

  1. kalexan

    kalexan Member
    PartnerNOC

    Joined:
    Jul 28, 2005
    Messages:
    9
    Likes Received:
    1
    Trophy Points:
    153
    Hello

    Backup complete with errors, regarding a file that does not exist at one of the server's accounts (replaced with ACCOUNTNAME, see bellow):
    Code:
    [2018-05-13 03:48:50 +0300] WARN: Warnings(s) encountered in tar during archiving:
    [2018-05-13 03:48:50 +0300] b_find(): /backup/2018-05-13/accounts/ACCOUNTNAME/htaccess/_home_ACCOUNTNAME_public_html_.htaccess: No such file or directory
    [2018-05-13 03:48:50 +0300] b_find(): /backup/2018-05-13/accounts/ACCOUNTNAME/htaccess/_home_ACCOUNTNAME_public_html_.htaccess: No such file or directory
    [2018-05-13 03:48:50 +0300] ERROR: The subprocess “Archive::Tar::Builder” reported error number 2 when it ended.: b_find(): /backup/2018-05-13/accounts/ACCOUNTNAME/htaccess/_home_ACCOUNTNAME_public_html_.htaccess: No such file or directory
    [2018-05-13 03:48:50 +0300] b_find(): /backup/2018-05-13/accounts/ACCOUNTNAME/htaccess/_home_ACCOUNTNAME_public_html_.htaccess: No such file or directory at /usr/local/cpanel/Cpanel/IO/Tarball.pm line 324.
    [2018-05-13 03:48:50 +0300] warn [backup] (XID u2avfd) “/usr/local/cpanel/bin/pkgacct” reported error code “1” when it ended:  at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 230.
        Cpanel::Backup::Utility::__ANON__(Cpanel::Exception::ProcessFailed::Error=HASH(0x2929fb8)) called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 120
        Try::Tiny::try(CODE(0x28c1620), Try::Tiny::Catch=REF(0x28e27e0), Try::Tiny::Finally=REF(0x28dc390)) called at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 240
        Cpanel::Backup::Utility::cpusystem(Cpanel::Backup::Utility=HASH(0x2754e30), "pkgacct", "ACCOUNTNAME", "/backup/2018-05-13/accounts", "backup") called at /usr/local/cpanel/bin/backup line 1679
        bin::backup::backup_accounts("/backup/2018-05-13/accounts") called at /usr/local/cpanel/bin/backup line 888
        bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 895
        bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 99
        eval {...} called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 90
        Try::Tiny::try(CODE(0x28a85e8), Try::Tiny::Catch=REF(0x28dd7e0)) called at /usr/local/cpanel/bin/backup line 905
        bin::backup::_process_backups(HASH(0x269d980)) called at /usr/local/cpanel/bin/backup line 379
        bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 120
    [2018-05-13 03:48:50 +0300] warn [backup] (XID u2avfd) “/usr/local/cpanel/bin/pkgacct” reported error code “1” when it ended:
    [2018-05-13 03:48:50 +0300] warn [backup] Failed to back up account “ACCOUNTNAME”. at /usr/local/cpanel/bin/backup line 1683.
        bin::backup::backup_accounts("/backup/2018-05-13/accounts") called at /usr/local/cpanel/bin/backup line 888
        bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 895
        bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 99
        eval {...} called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 90
        Try::Tiny::try(CODE(0x28a85e8), Try::Tiny::Catch=REF(0x28dd7e0)) called at /usr/local/cpanel/bin/backup line 905
        bin::backup::_process_backups(HASH(0x269d980)) called at /usr/local/cpanel/bin/backup line 379
        bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 120
    [2018-05-13 03:48:50 +0300] warn [backup] Failed to back up account “ACCOUNTNAME”.
    
    Any suggestions for a fix would be really appreciated.
     
    #1 kalexan, May 13, 2018
    Last edited by a moderator: May 13, 2018
  2. cPanelLauren

    cPanelLauren Forums Analyst II
    Staff Member

    Joined:
    Nov 14, 2017
    Messages:
    3,552
    Likes Received:
    253
    Trophy Points:
    193
    Location:
    Houston
    cPanel Access Level:
    DataCenter Provider
    HI @kalexan

    Does the path being noted in the error actually exist and have the correct permissions/ownership?

    Code:
     /backup/2018-05-13/accounts/ACCOUNTNAME/htaccess/_home_ACCOUNTNAME_public_html_.htaccess
    Thanks!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. kalexan

    kalexan Member
    PartnerNOC

    Joined:
    Jul 28, 2005
    Messages:
    9
    Likes Received:
    1
    Trophy Points:
    153
    I understand that
    /backup/2018-05-13/accounts/ACCOUNTNAME
    folder is created during backup, then it gets tar.gz-iped. There is no folder htaccess/ anywhere in the account fodler (in /home/ACCOUNTNAME), nor file _home_ACCOUNTNAME_public_html_.htaccess
     
  4. cPanelLauren

    cPanelLauren Forums Analyst II
    Staff Member

    Joined:
    Nov 14, 2017
    Messages:
    3,552
    Likes Received:
    253
    Trophy Points:
    193
    Location:
    Houston
    cPanel Access Level:
    DataCenter Provider
    Hi @kalexan

    Yes, it should be created during the backup (the /backup/date/accounts/accountname/ folder that is) but the htaccess folder and _home_ACCOUNTNAME_public_html_.htaccess bit is a bit strange without some customization being present. Could you please use the link in my signature and open a ticket for us to take a closer look? Once it's open please post the ticket ID here so that we can update this thread with the outcome.


    Thanks!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
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