Skip to main content

Backup problem after upgrading to cPanel ver 84

Comments

8 comments

  • nickgr67
    I forgot to mention the fact that these two servers are in the current release tier (Release Candidate) while all our other servers are in the release release tier (General Availability). I assume that this issue is not wide spread and is only affecting a few servers but it will become an issue once version 84 becomes "general availability"
    0
  • cPanelAaronH
    Hey nickgr67, I'm sorry to hear you're having some issues with the update and backups. Have you opened a ticket with our support team by chance? If not, would you mind doing so and providing access so we can take a closer look at this issue?
    0
  • nickgr67
    Hello Your Support Request ID is: 13517533
    0
  • natenate19
    I'm also seeing the same behavior after updating to cPanel 84, with only 1 account on 1 server, 2 nights in a row after updating to this version. Was this isolated to anything specific in the above cPanel ticket? Invoking pkgacct on the relevant account produces the same issue: [2019-10-12 02:56:58 -0400] Creating Archive .... ERROR: The subprocess "Archive::Tar::Builder" ended prematurely because it received the "ABRT" (6) signal. at /usr/local/cpanel/Cpanel/IO/Tarball.pm line 326.
    Moderator note: removed full backtrace output. This particular account was converted from an Addon Domain using the WHM functionality. There is nothing else unusual about it aside from perhaps the short username, and it's only ~2G in size on disk. Actually in looking further back in the logs, this has only been occurring since updating to 84.0.1. There was one backup run on 84.0.0, and this account backed up fine at that time. So perhaps some regression in 84.0.1 specifically.
    0
  • mtindor
    I have the same issue on one server, possibly two (in the process of checking second one now). No problems until after the servers updated to 11.84. Do I get to open a ticket as well ? :) Mike
    0
  • IanD
    Same here. It's fine for all my accounts except one - which I would guess bears a relation to it being the largest (~5.5GB). The second largest account is ~4GB and packages fine.
    0
  • mtindor
    In my case, on one server it's failing to back up an account because for whatever reason it can't do something with a mysql database during the pkgaccount stuff. On another account, there is some email in one of the directories of one of the email accounts on the server that is causing an Exception. That count doesn't get backed up either. And, when even one account doesn't get backed up and all of the rest do, the pruning (daily/weekly/monthly) does not take place and the old backups just continue to sit on the backup until the backup fills up. And all of this started happening with WHM 84. mike
    0
  • IanD
    This issue now appears to be resolved for me after WHM updated to v84.0.2. I should clarify in slight difference to the other posters that with me the issue was only present with v84.0.1 and not v84.0.0.
    0

Please sign in to leave a comment.