Fix RPM Issues Script Timeout

pzavar

• September 10, 2019 23:40

[2019-09-08 23:42:27 -0500] E [/usr/local/cpanel/scripts/find_and_fix_rpm_issues] The "/usr/local/cpanel/scripts/find_and_fix_rpm_issues" command (process 25083) ended prematurely because it received the "TERM" (15) signal. The process was aborted because it reached the timeout of 3,600 seconds. ... [2019-09-09 00:42:27 -0500] E [/usr/local/cpanel/scripts/rpmup] The "/usr/local/cpanel/scripts/rpmup" command (process 354) ended prematurely because it received the "TERM" (15) signal. The process was aborted because it reached the timeout of 3,600 seconds.

• 

  cPanelMichael

  • September 11, 2019 16:54

  Hello @pzavar, Can you run the command below on the affected server and let us know the output? /usr/local/cpanel/scripts/find_and_fix_rpm_issues --findonly
  Note: You must run this script as the root user. Thank you.

  0
• 

  Michael-Inet

  • April 28, 2020 14:49

  A VPS a non-profit I help keeps getting these timeouts, which breaks the fix-cpanel-perl; upcp --cron root cron script and generates a "cPanel & WHM update failure in upcp script" email. Panic ensues... VPS: CentOS 7, 8GB RAM, 2 CPU The last two are: E [/usr/local/cpanel/scripts/find_outdated_services] The "/usr/local/cpanel/scripts/find_outdated_services --auto" command (process 25041) ended prematurely because it received the "TERM" (15) signal. The system aborted the subprocess because it reached the timeout of 3,600 seconds. E [/usr/local/cpanel/scripts/rpmup] The "/usr/local/cpanel/scripts/rpmup" command (process 25973) ended prematurely because it received the "TERM" (15) signal. The system aborted the subprocess because it reached the timeout of 3,600 seconds.
  Obviously the VPS taking an hour to run an update is a bit much, so the timeout is probably warranted. But it seems to be causing other issues as well that aren"t getting cleaned up properly. [/usr/local/cpanel/scripts/rpmup] There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help) # /usr/local/cpanel/scripts/find_outdated_services --auto Looking for outdated services " The system found 15 outdated services:
  I cleaned all that up and rebooted for good measure, but the VPS does not show any "strain" during the cron run: 12:00:01 AM CPU %user %nice %system %iowait %steal %idle 02:20:01 AM all 2.68 0.01 0.63 0.03 0.00 96.64
  with 6GB free RAM this morning and no "High Load" type emails. Any suggestions? Thanks, Michael

  0

Please sign in to leave a comment.