Skip to main content

cPanel update says completed, then says cannot update

mvandemar
I just ran the updates on my client's cpanel, but I am not understanding the last few lines of the output: [2018-07-04 02:31:42 -0400] Processing: Updating plugins data cache [2018-07-04 02:31:42 -0400] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache` [2018-07-04 02:31:43 -0400] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.412 seconds [2018-07-04 02:31:43 -0400] 95% complete => Log closed Wed Jul 4 02:31:43 2018 ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (22032) at Wed Jul 4 02:31:43 2018 [2018-07-04 02:31:43 -0400] Pre Maintenance completed successfully [2018-07-04 02:31:46 -0400] 95% complete [2018-07-04 02:31:46 -0400] Running Standardized hooks [2018-07-04 02:31:46 -0400] 100% complete [2018-07-04 02:31:46 -0400] [2018-07-04 02:31:46 -0400] cPanel update completed [2018-07-04 02:31:46 -0400] A log of this update is available at /var/cpanel/updatelogs/update.1530684687.log [2018-07-04 02:31:46 -0400] Removing upcp pidfile [2018-07-04 02:31:46 -0400] W NOTE: A system upgrade was not possible due to the following blockers: [2018-07-04 02:31:46 -0400] W [FATAL] - Downgrades to a previous major release are not permitted. => Log closed Wed Jul 4 02:31:46 2018
Why would it tell me that I can't downgrade when I was trying to run updates? Did it finish successfully, or did the update ultimately fail? Any idea why it would be trying to downgrade? The cpanel version is 70.0.51. Thanks. -Michael

Comments

6 comments

Date Votes
  • 24x7server
    Hi, Please go through the below document for more information on the issue you have faced.. Upgrade Blockers - Version 68 Documentation - cPanel Documentation
    0
  • cPanelLauren
    Hi @mvandemar This just indicates that maintenance completed and then when attempting to update the update failed because it believes you're trying to downgrade. Can you tell me what is present in the following: cat /etc/cpupdate.conf
    and what the output is when you run: cat /usr/local/cpanel/version
    0
  • mvandemar
    Hi @mvandemar This just indicates that maintenance completed and then when attempting to update the update failed because it believes you're trying to downgrade. Can you tell me what is present in the following: cat /etc/cpupdate.conf
    and what the output is when you run: cat /usr/local/cpanel/version

    @cPanelLauren thank you, output below: # cat /etc/cpupdate.conf CPANEL=11.68 RPMUP=daily SARULESUP=daily STAGING_DIR=/usr/local/cpanel UPDATES=daily
    # cat /usr/local/cpanel/version 11.70.0.51
    Looks like they don't match, would that be the issue? The version displayed in whm is the second one. Edit: The client just got an email this morning that said this, not sure if it's related or not: warning: erase unlink of /lib/modules/2.6.32-696.18.7.el6.x86_64/modules.order failed: No such file or directory warning: erase unlink of /lib/modules/2.6.32-696.18.7.el6.x86_64/modules.networking failed: No such file or directory warning: erase unlink of /lib/modules/2.6.32-696.18.7.el6.x86_64/modules.modesetting failed: No such file or directory warning: erase unlink of /lib/modules/2.6.32-696.18.7.el6.x86_64/modules.drm failed: No such file or directory warning: erase unlink of /lib/modules/2.6.32-696.18.7.el6.x86_64/modules.block failed: No such file or directory
    Just including in case it helps diagnose. -Michael
    0
  • cPanelLauren
    Hi @mvandemar Yea you're running version 70 of cPanel but the update is trying to move you to version 68 per the cpupdate.conf. If you want to update to the RELEASE version of cPanel automatically from here on you can just modify the CPANEL line of the cpupdate.conf to display as follows: CPANEL=release
    0
  • mvandemar
    Hi @mvandemar Yea you're running version 70 of cPanel but the update is trying to move you to version 68 per the cpupdate.conf. If you want to update to the RELEASE version of cPanel automatically from here on you can just modify the CPANEL line of the cpupdate.conf to display as follows: CPANEL=release

    Looks like it worked, thanks! => Log opened from /usr/local/cpanel/scripts/updatenow (22104) at Wed Jul 4 15:56:55 2018 [2018-07-04 15:56:55 -0400] Detected version '11.72.0.7' from version file. [2018-07-04 15:56:55 -0400] Running version '11.72.0.7' of updatenow. [2018-07-04 15:56:55 -0400] Target version set to '11.72.0.7' [2018-07-04 15:56:55 -0400] Up to date (11.72.0.7) => Log closed Wed Jul 4 15:56:55 2018 ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (19324) at Wed Jul 4 15:56:55 2018 [2018-07-04 15:56:56 -0400] 95% complete [2018-07-04 15:56:56 -0400] Running Standardized hooks [2018-07-04 15:56:56 -0400] 100% complete [2018-07-04 15:56:56 -0400] [2018-07-04 15:56:56 -0400] cPanel update completed [2018-07-04 15:56:56 -0400] A log of this update is available at /var/cpanel/updatelogs/update.1530733026.log [2018-07-04 15:56:56 -0400] Removing upcp pidfile [2018-07-04 15:56:56 -0400] [2018-07-04 15:56:56 -0400] Completed all updates => Log closed Wed Jul 4 15:56:56 2018
    -Michael
    0
  • cPanelLauren
    Hi Michael, Great to hear! Thanks for letting us know and I'm glad it's all sorted for you now ;)
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post