Skip to main content

cPanel & WHM update failure in upcp script

Comments

16 comments

  • cPRex Jurassic Moderator
    Hey there! If you manually run "/scripts/rdate" on the server, do you receive any errors?
    0
  • rekoo20
    Hey there! If you manually run "/scripts/rdate" on the server, do you receive any errors?

    nothing happens when I type /scripts/rdate using Terminal via WHM //root user [QUOTE] [root@vps ~]# /scripts/rdate [root@vps ~]
    0
  • cPRex Jurassic Moderator
    Thanks for that - if you for the cPanel update now, does that also not give you any errors? I'm wondering if there was a temporary issue with the system that led to this, as that tool just checks the time and the system and makes sure that is in place.
    0
  • Heyckel
    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/modsec_vendor". Review the update logs to determine why the update failed.
    Update log preview:
    ... ... [2022-10-30 03:18:08 +0100] E [/usr/local/cpanel/scripts/modsec_vendor] The "/usr/local/cpanel/scripts/modsec_vendor update --auto" command (process 8629) reported error number 1 when it ended. ... [2022-10-30 03:18:11 +0100] - Processing command `/usr/local/cpanel/bin/cloudlinux_update` [2022-10-30 03:18:11 +0100] - Finished command `/usr/local/cpanel/bin/cloudlinux_update` in 0.086 seconds [2022-10-30 03:18:11 +0100] Processing: Updating plugins data cache [2022-10-30 03:18:11 +0100] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache` [2022-10-30 03:18:11 +0100] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.028 seconds [2022-10-30 03:18:11 +0100] Processing: Ensuring SSL certificate information for CCS is up to date. [2022-10-30 03:18:11 +0100] - Processing command `/usr/local/cpanel/scripts/ccs-check --run --ssl` [2022-10-30 03:18:11 +0100] [/usr/local/cpanel/scripts/ccs-check] SSL information updated. [2022-10-30 03:18:11 +0100] - Finished command `/usr/local/cpanel/scripts/ccs-check --run --ssl` in 0.066 seconds [2022-10-30 03:18:11 +0100] Processing: Ensure cpanel-plugins yum repo exists [2022-10-30 03:18:11 +0100] - Finished in 0.569 seconds [2022-10-30 03:18:11 +0100] Processing: Checking Addon Licenses [2022-10-30 03:18:11 +0100] - Finished in 0.006 seconds [2022-10-30 03:18:11 +0100] Processing: Updating Public Suffix List [2022-10-30 03:18:11 +0100] Processing: Checking End Of Life for current version. [2022-10-30 03:18:12 +0100] - Finished in 0.223 seconds [2022-10-30 03:18:12 +0100] Processing: [2022-10-30 03:18:12 +0100] Maintenance complete. => Log closed Sun Oct 30 03:18:12 2022 ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (7015) at Sun Oct 30 03:18:12 2022
    The system generated this notice on Sunday, October 30, 2022 at 2:18:12 AM UTC. "cPanel Update Failures" notifications are currently configured to have an importance of "High". You can change the importance or disable this type of notification in WHM"s Contact Manager at:
    0
  • cPRex Jurassic Moderator
    @Heyckel - can you run the "/usr/local/cpanel/scripts/modsec_vendor update --auto" command by itself and see if that gives you any additional errors?
    0
  • Heyckel
    Hello, i run the commande i have only this : info [modsec_vendor] Updates are in progress for all of the installed ModSecurity vendors with automatic updates enabled. info [modsec_vendor] Restored modsec_cpanel_conf_datastore backup info [modsec_vendor] The vendor "imunify360-full-apache" is already up to date.
    0
  • cPRex Jurassic Moderator
    Thanks for that output. It sounds like this could have just been a temporary glitch with the update. Can you try running a full "/scripts/upcp --force" to see if that also is working well now?
    0
  • Heyckel
    Please [root@mail2 ~]# /scripts/upcp --force [2022-10-31 17:15:37 +0100] Detected cron=0 (--force passed on command line) ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (31032) at Mon Oct 31 17:15:37 2022 [2022-10-31 17:15:37 +0100] Detected cron=0 (--force passed on command line) [2022-10-31 17:15:37 +0100] 1% complete [2022-10-31 17:15:37 +0100] Running Standardized hooks [2022-10-31 17:15:37 +0100] 2% complete [2022-10-31 17:15:37 +0100] mtime on upcp is 1662329728 (Mon Sep 5 00:15:28 2022) ---------------------------------------------------------------------------------------------------- => Log opened from /usr/local/cpanel/scripts/updatenow (31034) at Mon Oct 31 17:15:37 2022 [2022-10-31 17:15:37 +0100] Running version '11.106.0.9' of updatenow. [2022-10-31 17:15:37 +0100] Detected version '11.106.0.9' from version file. [2022-10-31 17:15:37 +0100] --force passed on command line. Upgrade will disregard update config settings. [2022-10-31 17:15:37 +0100] Target version set to '11.106.0.9' [2022-10-31 17:15:37 +0100] Checking license [2022-10-31 17:15:38 +0100] License file check complete [2022-10-31 17:15:38 +0100] glibc-2.17-326.el7_9.x86_64 [2022-10-31 17:15:38 +0100] Testing if rpm_is_working RPM is installed [2022-10-31 17:15:38 +0100] Testing if it's possible to install a simple RPM [2022-10-31 17:15:38 +0100] Preparing... ######################################## [2022-10-31 17:15:38 +0100] Updating / installing... [2022-10-31 17:15:38 +0100] rpm_is_working-1.0-0 ######################################## [2022-10-31 17:15:38 +0100] Ensuring required distro packages are installed. [2022-10-31 17:15:38 +0100] Staging 11.106.0.9 cpanelsync files prior to updating /usr/local/cpanel [2022-10-31 17:15:38 +0100] Staging cpanel changes [2022-10-31 17:15:38 +0100] checkyum version 22.3 (excludes: bind-chroot) [2022-10-31 17:15:38 +0100] Retrieving and staging /cpanelsync/11.106.0.9/binaries/linux-c7-x86_64/.cpanelsync.bz2 [2022-10-31 17:15:38 +0100] Using mirror '201.159.169.169' for host 'httpupdate.cpanel.net'. [2022-10-31 17:15:39 +0100] All Needed Packages are already installed. => Log closed Mon Oct 31 17:15:39 2022
    0
  • cPRex Jurassic Moderator
    Is there no more output after the Log closed" line? That's where it should start the forced update.
    0
  • Heyckel
    cPanel Update (upcp) is already running. Please wait for the previous upcp (PID 31032, log file "/var/cpanel/updatelogs/update.31032.91888054.1666314056.log") to complete, then try again. You can use the command 'ps --pid 31032' to check if the process is running. You may wish to use '--force'.
    0
  • cPRex Jurassic Moderator
    There you go - it looks like it's already running in the background so you'll need to let that finish first.
    0
  • Heyckel
    Ok thanks CPRex for your help i will post soon when it's finish
    0
  • Heyckel
    Hello i have same probleme :
    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/rdate". Review the update logs to determine why the update failed.
    Update log preview:
    ... ... [2022-12-26 03:15:22 +0100] E [/usr/local/cpanel/scripts/rdate] Failed to run due to the 10 second timeout being exceeded. [2022-12-26 03:15:22 +0100] E [/usr/local/cpanel/scripts/rdate] The "/usr/local/cpanel/scripts/rdate" command (process 28493) reported error number 4 when it ended. ... [2022-12-26 03:18:02 +0100] - Finished command `/usr/local/cpanel/bin/cloudlinux_update` in 0.163 seconds [2022-12-26 03:18:02 +0100] Processing: Updating plugins data cache [2022-12-26 03:18:02 +0100] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache` [2022-12-26 03:18:02 +0100] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.146 seconds [2022-12-26 03:18:02 +0100] Processing: Ensuring SSL certificate information for CCS is up to date. [2022-12-26 03:18:02 +0100] - Processing command `/usr/local/cpanel/scripts/ccs-check --run --ssl` [2022-12-26 03:18:02 +0100] [/usr/local/cpanel/scripts/ccs-check] SSL information updated. [2022-12-26 03:18:02 +0100] - Finished command `/usr/local/cpanel/scripts/ccs-check --run --ssl` in 0.219 seconds [2022-12-26 03:18:02 +0100] Processing: Ensure cpanel-plugins yum repo exists [2022-12-26 03:18:03 +0100] - Finished in 0.606 seconds [2022-12-26 03:18:03 +0100] Processing: Checking Addon Licenses [2022-12-26 03:18:03 +0100] - Finished in 0.021 seconds [2022-12-26 03:18:03 +0100] Processing: Updating Public Suffix List [2022-12-26 03:18:03 +0100] Processing: Checking End Of Life for current version. [2022-12-26 03:18:03 +0100] - Finished in 0.306 seconds [2022-12-26 03:18:03 +0100] Processing: [2022-12-26 03:18:03 +0100] Maintenance complete. => Log closed Mon Dec 26 03:18:03 2022 ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (28278) at Mon Dec 26 03:18:03 2022
    The system generated this notice on Monday, December 26, 2022 at 2:18:04 AM UTC. "cPanel Update Failures" notifications are currently configured to have an importance of "High". You can change the importance or disable this type of notification in WHM"s Contact Manager at:
    0
  • cPRex Jurassic Moderator
    @Heyckel - what happens if you manually run the rdate command from the error on the machine? Are there any issues with the time on the server?
    0
  • Heyckel
    [root@mail2 ~]# rdate Usage: rdate [-s] [-p] [-u] [-l] [-t sec] ... [root@mail2 ~]# date Thu Dec 29 01:18:56 CET 2022 [root@mail2 ~]# rdate -s rdate.cpanel.net [root@mail2 ~]# date Thu Dec 29 01:19:18 CET 2022 [root@mail2 ~]# No problem
    0
  • cPRex Jurassic Moderator
    I'm not sure what the issue may be, then. Did you receive another update failure this morning? If not, it's possible this was just a one-time event.
    0

Please sign in to leave a comment.