<https://forums.cpanel.net/threads/cpanel-whm-update-failure-in-upcp-script-the-usr-local-cpanel-scripts-rpmup-command-reported-error-number-1.676937/>
<http://schema.org/articleBody>
"Hello,\n\nHi, this error came to me for the first time for me:\n\n--------------------------------------------------------------------------\n\nMaintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/rpmup”. Review the update logs to determine why the update failed.\n\nUpdate log preview:\n\n\n...\n...\n[2020-08-06 23:00:49 -0300] E [/usr/local/cpanel/scripts/rpmup] The “/usr/local/cpanel/scripts/rpmup” command (process 8318) reported error number 1 when it ended.\n...\n[2020-08-06 23:01:32 -0300] - Finished command `/usr/local/cpanel/scripts/check_mysql` in 0.082 seconds\n[2020-08-06 23:01:32 -0300] Processing: Checking CloudLinux installation\n[2020-08-06 23:01:32 -0300] - Processing command `/usr/local/cpanel/bin/cloudlinux_update`\n[2020-08-06 23:01:32 -0300] - Finished command `/usr/local/cpanel/bin/cloudlinux_update` in 0.036 seconds\n[2020-08-06 23:01:32 -0300] Processing: Updating plugins data cache\n[2020-08-06 23:01:32 -0300] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache`\n[2020-08-06 23:01:32 -0300] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.016 seconds\n[2020-08-06 23:01:32 -0300] Processing: Ensuring SSL certificate information for CCS is up to date.\n[2020-08-06 23:01:32 -0300] - Processing command `/usr/local/cpanel/scripts/ccs-check --run --ssl`\n[2020-08-06 23:01:32 -0300] - Finished command `/usr/local/cpanel/scripts/ccs-check --run --ssl` in 0.005 seconds\n[2020-08-06 23:01:32 -0300] Processing: Ensure cpanel-plugins yum repo exists\n[2020-08-06 23:01:33 -0300] - Finished in 0.275 seconds\n[2020-08-06 23:01:33 -0300] Processing: Checking Addon Licenses\n[2020-08-06 23:01:33 -0300] - Finished in 0.004 seconds\n[2020-08-06 23:01:33 -0300] Processing: Checking End Of Life for current version.\n[2020-08-06 23:01:33 -0300] - Finished in 0.062 seconds\n[2020-08-06 23:01:33 -0300] Processing:\n[2020-08-06 23:01:33 -0300] Maintenance complete.\n=> Log closed Thu Aug 6 23:01:33 2020\n----------------------------------------------------------------------------------------------------\n=> Log opened from cPanel Update (upcp) - Slave (8148) at Thu Aug 6 23:01:33 2020\n\n\n\nI manually ran the command \"/usr/local/cpanel/scripts/rpmup\" and in the end I get these two errors (bold):\n\n\n\ncheckyum version 22.3  (excludes: bind-chroot kernel ruby)\ninfo [rpmup] Starting yum execution “--assumeyes --color=never --config /etc/yum.conf update”.\nLoaded plugins: fastestmirror, universal-hooks\nLoading mirror speeds from cached hostfile\n* EA4: 104.254.183.20\n* cpanel-addons-production-feed: 104.254.183.20\n* cpanel-plugins: 104.254.183.20\nResolving Dependencies\n--> Running transaction check\n---> Package ai-bolit.x86_64 1:20.0619-1.el7 will be updated\n---> Package ai-bolit.x86_64 1:20.0717-1.el7 will be an update\n--> Finished Dependency Resolution\n\n\nTotal download size: 5.7 M\nDownloading packages:\nNo Presto metadata available for imunify360\nRunning transaction check\nRunning transaction test\nTransaction test succeeded\nRunning transaction\n  Updating   : 1:ai-bolit-20.0717-1.el7.x86_64                              1/2\nError unpacking rpm package 1:ai-bolit-20.0717-1.el7.x86_64\n\n1:ai-bolit-20.0619-1.el7.x86_64 was supposed to be removed but is not!\n  Verifying  : 1:ai-bolit-20.0619-1.el7.x86_64                              1/2\n   Verifying  : 1:ai-bolit-20.0717-1.el7.x86_64                              2/2\n\nComplete!\ninfo [rpmup] Completed yum execution “--assumeyes --color=never --config /etc/yum.conf update”: in 8.550 second(s).\n(XID ykhqkw) “/usr/bin/yum” reported error code “1” when it ended:\ncheckyum version 22.3  (excludes: bind-chroot ruby)\n\n\n\nWould anyone know how to help me solve this problem?"
<https://forums.cpanel.net/threads/cpanel-whm-update-failure-in-upcp-script-the-usr-local-cpanel-scripts-rpmup-command-reported-error-number-1.676937/>