The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

upcp cron to 11.44 fails to upgrade

Discussion in 'General Discussion' started by kernow, Jun 18, 2014.

  1. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    The cron /upcp failed to update to 11.44
    snip.........
    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:
    So we will just wait I guess........
     
    #1 kernow, Jun 18, 2014
    Last edited: Jun 18, 2014
  2. 24x7server

    24x7server Well-Known Member

    Joined:
    Apr 17, 2013
    Messages:
    1,146
    Likes Received:
    34
    Trophy Points:
    48
    Location:
    India
    cPanel Access Level:
    Root Administrator
    Hello,

    Have you tried to update cPanel with --force ?

    Code:
    /scripts/upcp --force 
     
  3. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Haven't used the --force option. There's nothing in the update were desperate for so we can wait.
     
  4. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    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.
     
  5. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Fixed, a 16 character username (set up in 2008) was the problem.
     
  6. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Would you be willing to share more details?
     
  7. atomiccomputers

    atomiccomputers Registered

    Joined:
    Mar 25, 2008
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    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.
     
  8. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    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.
     
    #8 kernow, Jun 20, 2014
    Last edited: Jun 20, 2014
  9. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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.
     
  10. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Well we did submit a ticket #[cPanel tickets ID# 5115091 however the ticket was closed after shortening the username
     
Loading...

Share This Page