Skip to main content

cPanel & WHM update failure in upcp script

Comments

10 comments

  • andrew.n
    Could you paste the full log here? thanks
    0
  • splaquet
    I"m pretty much in an identical scenario. The cPanel & WHM update process failed for the following reason: Maintenance ended; however, it did not exit cleanly (256). The following events were logged: "scripts/find_outdated_services". Review the update logs to determine why the update failed. Update log preview: ... ... [2022-01-09 00:33:51 -0500] E [/usr/local/cpanel/scripts/find_outdated_services] STDOUT: This system is receiving updates from CloudLinux Network server. [2022-01-09 00:33:51 -0500] E [/usr/local/cpanel/scripts/find_outdated_services] [2022-01-09 00:33:51 -0500] E [/usr/local/cpanel/scripts/find_outdated_services] [2022-01-09 00:33:51 -0500] E [/usr/local/cpanel/scripts/find_outdated_services] STDERR: [Errno 2] No such file or directory: '/proc/2607906/stat' ... [2022-01-09 00:35:27 -0500] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache` [2022-01-09 00:35:27 -0500] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.144 seconds [2022-01-09 00:35:27 -0500] Processing: Ensuring SSL certificate information for CCS is up to date. [2022-01-09 00:35:27 -0500] - Processing command `/usr/local/cpanel/scripts/ccs-check --run --ssl` [2022-01-09 00:35:27 -0500] [/usr/local/cpanel/scripts/ccs-check] SSL information updated. [2022-01-09 00:35:27 -0500] - Finished command `/usr/local/cpanel/scripts/ccs-check --run --ssl` in 0.184 seconds [2022-01-09 00:35:27 -0500] Processing: Ensure cpanel-plugins yum repo exists [2022-01-09 00:35:28 -0500] - Finished in 0.204 seconds [2022-01-09 00:35:28 -0500] Processing: Checking Addon Licenses [2022-01-09 00:35:28 -0500] - Finished in 0.026 seconds [2022-01-09 00:35:28 -0500] Processing: Updating Public Suffix List [2022-01-09 00:35:28 -0500] Processing: Checking End Of Life for current version. [2022-01-09 00:35:28 -0500] - Finished in 0.206 seconds [2022-01-09 00:35:28 -0500] Processing: [2022-01-09 00:35:28 -0500] Maintenance complete. => Log closed Sun Jan 9 00:35:28 2022 ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (2605003) at Sun Jan 9 00:35:28 2022
    0
  • andrew.n
    full log please
    0
  • eLIANT
    mine's a little simpler, I think. Running 100.0.5 Cron output email Subject contains: (/usr/local/cpanel/scripts/fix-cpanel-perl; /etc/upcp_control) and email body is: [QUOTE]updates Updating target version in cpupdate.conf to 11.86 cannot find /var/cpanel/sysinfo.config
    0
  • andrew.n
    Interesting that file doesn't exist on a few of my systems either. If you execute these commands manually do you get the same? /usr/local/cpanel/scripts/fix-cpanel-perl if yes then can you try to create that file and see how it works? touch /var/cpanel/sysinfo.config
    0
  • cPRex Jurassic Moderator
    @eLIANT - if you're already on version 100, it seems odd the updater would mention version 86. I'm wondering if there is an issue with the /etc/cpupdate.conf file on your machine. I pulled this from a system running the Current tier: # cat /etc/cpupdate.conf CPANEL=current RPMUP=daily SARULESUP=daily STAGING_DIR=/usr/local/cpanel UPDATES=daily
    so can you see if your file is similar to that?
    0
  • eLIANT
    was CPANEL=11.86 I changed it to CURRENT Waiting to see if updates work correctly.
    0
  • cPRex Jurassic Moderator
    I would expect things to work better after that value is changed to Current. Let me know if you still run into any issues!
    0
  • eLIANT
    Hmmm.... Got another email: says the same thing. CPANEL=11.86 visited /etc/cpupdate.conf and sure enough, it was set for 11.86. Either I failed miserably, or ... what? There is no "or". I failed. I've re-enter "CURRENT" and saved the file, double-checked. Now I wait. Again.
    0
  • cPRex Jurassic Moderator
    Just for fun, could you try lower-case letters? There's no reason to wait - you can run "/scripts/upcp --force" to start the update now. It'll still follow the settings in that file.
    0

Please sign in to leave a comment.