Skip to main content

Backup process errors

Comments

10 comments

  • cPanelMichael
    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:
    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.
    0
  • Misiek
    Nothing there. Tried to do it manual via /scripts/pkgacct but this is the result
    .................... [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.
    0
  • cPanelMichael
    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.
    0
  • Misiek
    Dear Michael, I did as requested.
    Support Request ID is: 8355317
    Regards,
    0
  • cPanelMichael
    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.
    0
  • Misiek
    No faults in RAM. Problem Stil exists and is connected to specific files.
    0
  • cPanelMichael
    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.
    0
  • Misiek
    No disc errors: -----------------%<----------------- HDDTEST Z1X0YSGK: Ok HDDTEST Z1X0YSEP: Ok -----------------%<----------------- The test was full diagnosis of both HDD
    0
  • cPanelMichael
    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.
    0
  • cPanelMichael
    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.
    0

Please sign in to leave a comment.