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 process errors

Discussion in 'Data Protection' started by Misiek, Apr 2, 2017.

Tags:
  1. Misiek

    Misiek Well-Known Member

    Joined:
    Feb 23, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    Dear all,
    Every backup has one error on the same user :

    Code:
    [2017-04-01 16:46:56 +0200] Creating Archive ....................................................................................
................................................................................
................................................................................
................................................................................
2017-04-01 17:33:26 +0200] ERROR: The subprocess “Archive::Tar::Builder” ended prematurely because it received the “SEGV” (11) signal. at /usr/local/cpanel/Cpanel/IO/Tarball.pm line 283.
[2017-04-01 17:33:26 +0200] warn [backup] (XID qgkxmu) “/usr/local/cpanel/bin/pkgacct” reported error code “1” when it ended:  at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 218.
   Cpanel::Backup::Utility::__ANON__(Cpanel::Exception::ProcessFailed::Error=HASH(0x2376fc8)) called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 122
   Try::Tiny::try(CODE(0x22f6700), Try::Tiny::Catch=REF(0x2377490), Try::Tiny::Finally=REF(0x2377268)) called at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 228
   Cpanel::Backup::Utility::cpusystem(Cpanel::Backup::Utility=HASH(0x20e2300), "pkgacct", "magik", "/home/backup/2017-04-01/accounts", "backup") called at /usr/local/cpanel/bin/backup line 1210
   bin::backup::backup_accounts("/home/backup/2017-04-01/accounts") called at /usr/local/cpanel/bin/backup line 616
   bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 623
   bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 101
   eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 92
   Try::Tiny::try(CODE(0x2286740), Try::Tiny::Catch=REF(0x2292898)) called at /usr/local/cpanel/bin/backup line 633
   bin::backup::_process_backups(HASH(0x2055298)) called at /usr/local/cpanel/bin/backup line 321
   bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 100
[2017-04-01 17:33:26 +0200] warn [backup] Failed to back up account “magik”. at /usr/local/cpanel/bin/backup line 1218.
   bin::backup::backup_accounts("/home/backup/2017-04-01/accounts") called at /usr/local/cpanel/bin/backup line 616
   bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 623
   bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 101
   eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 92
   Try::Tiny::try(CODE(0x2286740), Try::Tiny::Catch=REF(0x2292898)) called at /usr/local/cpanel/bin/backup line 633
   bin::backup::_process_backups(HASH(0x2055298)) called at /usr/local/cpanel/bin/backup line 321
   bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 100
    I have absolutley no idea how to inspect this issue.
    Can somebody help me ?
     
    #1 Misiek, Apr 2, 2017
  2. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,802
    Likes Received:
    1,896
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    Is CSF/LFD installed on this system? If so, check to see if LFD is killing the process by checking it's log file via the following command:

    Code:
    grep pkgacct /var/log/lfd.log
    If the logs show LFD is killing the process, then it likely relates to LFD's PT_USERKILL option. CSF does not recommend enabling that option in the configuration since it can cause unexpected behavior:

    csf PT_USERKILL Recommendation | ConfigServer Services Blog

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #2 cPanelMichael, Apr 3, 2017
  3. Misiek

    Misiek Well-Known Member

    Joined:
    Feb 23, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    Nothing there.
    Tried to do it manual via /scripts/pkgacct but this is the result
    Code:
    ....................
[2017-04-03 22:16:31 +0200] ERROR: The subprocess “Archive::Tar::Builder” ended prematurely because it received the “SEGV” (11) signal. at /usr/local/cpanel/Cpanel/IO/Tarball.pm line 283.
     
    #3 Misiek, Apr 3, 2017
  4. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,802
    Likes Received:
    1,896
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #4 cPanelMichael, Apr 4, 2017
  5. Misiek

    Misiek Well-Known Member

    Joined:
    Feb 23, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    Dear Michael,
    I did as requested.
    Code:
    Support Request ID is: 8355317
    Regards,
     
    #5 Misiek, Apr 4, 2017
  6. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,802
    Likes Received:
    1,896
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    To update, it looks like this is a hardware issue with the RAM installed on the system. The user was advised to report this to their data center or hosting provider.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #6 cPanelMichael, Apr 5, 2017
  7. Misiek

    Misiek Well-Known Member

    Joined:
    Feb 23, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    No faults in RAM.
    Problem Stil exists and is connected to specific files.
     
    #7 Misiek, Apr 8, 2017
  8. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,802
    Likes Received:
    1,896
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    Feel free to update the support ticket with your most recent findings (you mentioned checking the hard drives in your last ticket response).

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #8 cPanelMichael, Apr 11, 2017
  9. Misiek

    Misiek Well-Known Member

    Joined:
    Feb 23, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    No disc errors:

    -----------------%<-----------------

    HDDTEST Z1X0YSGK: Ok
    HDDTEST Z1X0YSEP: Ok


    -----------------%<-----------------

    The test was full diagnosis of both HDD
     
    #9 Misiek, Apr 12, 2017
  10. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,802
    Likes Received:
    1,896
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    To update, it looks like this relates to an internal case (CPANEL-12587) where backups can segfault when encountering a long path. I'll update this thread with more information on the status of this case as it becomes available. In the meantime, the temporary workaround is to remove the long path (or removing any script plugin that may have generated it).

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #10 cPanelMichael, Apr 12, 2017
  11. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,802
    Likes Received:
    1,896
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    To update, this is fixed as of cPanel version 64.0.17:

    Fixed case CPANEL-12587: Update cpanel-perl-524-Archive-Tar-Builder to 2.5002-1.cp1162.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #11 cPanelMichael, Apr 24, 2017
(You must log in or sign up to post here.)
Loading...
Similar Threads - Backup process errors
  1. dr_lucas

    The backup process completed, but 30 errors occurred.

    dr_lucas, Jul 16, 2018, in forum: Data Protection
    Replies:
    3
    Views:
    169
    cPanelLauren
    Jul 23, 2018
  2. Nirjonadda

    The backup process completed, but 2 errors occurred

    Nirjonadda, Apr 19, 2018, in forum: Data Protection
    Replies:
    5
    Views:
    160
    cPanelLauren
    Apr 20, 2018
  3. Havri

    The backup process completed, but 2 errors occurred.

    Havri, Oct 30, 2017, in forum: Data Protection
    Replies:
    1
    Views:
    414
    cPanelMichael
    Oct 31, 2017
  4. ttremain

    The backup process completed, but 6 errors occurred

    ttremain, Jan 7, 2017, in forum: Data Protection
    Replies:
    6
    Views:
    994
    cPanelMichael
    Jan 11, 2017
  5. craigedmonds

    Backup Process Errors due to MySQL DB being remotely hosted

    craigedmonds, Dec 22, 2016, in forum: Data Protection
    Replies:
    1
    Views:
    577
    cPanelMichael
    Dec 22, 2016

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.
    Accept Learn More...
    Dismiss Notice