Skip to main content

upcp cron to 11.44 fails to upgrade

kernow
The cron /upcp failed to update to 11.44 snip......... [QUOTE][20140618.063212] Testing if rpm_is_working RPM is installed [20140618.063212] package rpm_is_working is not installed [20140618.063212] Testing if it's possible to install a simple RPM [20140618.063212] Preparing... ################################################## [20140618.063212] rpm_is_working ################################################## => Log closed Wed Jun 18 06:32:13 2014 [20140618.063213] 17% complete [20140618.063213] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1403073130.log` failed, exited with code 2 (signal = 0)
Tried a couple time manually but still fails, maybe mirror is down? EDIT. Hmmm... well the above was run on some dedi servers but on a couple of VPS we get a more detailed message from the cron job: [QUOTE]E Blocker found: Upgrade to the next LTS is blocked until Monday Jun 23, 2014 in order to distribute upgrades over a four day period. If you wish to upgrade now, you can do so now with the force option.
So we will just wait I guess........

Comments

9 comments

Date Votes
  • 24x7server
    Hello, Have you tried to update cPanel with --force ? /scripts/upcp --force
    0
  • kernow
    Haven't used the --force option. There's nothing in the update were desperate for so we can wait.
    0
  • cPanelKenneth
    kernow, the first log output you post looks to be an actual problem on your system(s). If there is no further information in the update logs (/var/cpanel/updatelogs), I suggest you open a ticket. The second message is from the deferred upgrade system we introduced in 11.40. As it states, you can manually bypass the deferral by running upcp with the --force option.
    0
  • kernow
    Fixed, a 16 character username (set up in 2008) was the problem.
    0
  • cPanelKenneth
    [quote="kernow, post: 1667422">Fixed, a 16 character username (set up in 2008) was the problem.
    Would you be willing to share more details?
    0
  • atomiccomputers
    This was indeed the issue. We had 3 usernames that were 16 characters long when viewing the account list. Changing the account usernames to shorter usernames fixed the issue. We also have several 15 character usernames and did not need to change these, so it seems the limit is 15 for valid username lengths for the upgrade.
    0
  • kernow
    [quote="cPanelKenneth, post: 1667462">Would you be willing to share more details?
    The error thrown up was by mysql, saying more than 16 characters was not allowed for a database name however this client didn't have any databases ( luckily as it would have caused more errors) but their username was more than 16 characters. Shortening it fixed the problem. Note as I mentioned earlier, this account was created in 2008 yet upgrades since then did not pick up a problem with the length of characters.
    0
  • cPanelMichael
    Hello :) The username and database name length changes with version 11.44 are documented in the release notes here: 11.44 - Release Notes However, I don't believe it should result in the update process failing (and if so it should issue a proper notification). Please open a bug report for that issue via: Submit A Bug Report You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • kernow
    Well we did submit a ticket #[cPanel tickets ID# 5115091 however the ticket was closed after shortening the username
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post