Skip to main content

cPanel update hanging

Comments

3 comments

  • mvandemar
    Further testing: I noticed that /usr/local/cpanel/scripts/maintenance was also something that failed when the disk was full, so I just tried running that manually to see if it might fix some issues. That is also hanging when it gets to the point of "updatesigningkey":
    [~]# /usr/local/cpanel/scripts/maintenance [2017-04-18 00:45:09 -0500] Purging cpupdate.conf of invalid entries [2017-04-18 00:45:09 -0500] Purging upcp logs older than 45 days. [2017-04-18 00:45:11 -0500] Processing: Assuring needed symlinks in 3rdparty/bin are in place. [2017-04-18 00:45:11 -0500] - Processing command `/usr/local/cpanel/scripts/link_3rdparty_binaries` [2017-04-18 00:45:11 -0500] Processing: Setting clock [2017-04-18 00:45:11 -0500] - Processing command `/usr/local/cpanel/scripts/rdate` [2017-04-18 00:45:11 -0500] [9682] Virtual environment detected - rdate skipped [2017-04-18 00:45:11 -0500] Processing: Updating cPanel signing keys. [2017-04-18 00:45:11 -0500] - Processing command `/usr/local/cpanel/scripts/updatesigningkey`
    Note that this did cause all of the log files in /var/cpanel/updatelogs to be deleted, even the ones not older than 45 days, but aside from that it just appears to be sitting there. Edit: I am also attempting to run "/usr/local/cpanel/scripts/check_cpanel_rpms --fix", but this as well appears to just be hanging and not doing anything. -Michael
    0
  • mvandemar
    Update: I noticed that the last server restart was from before the crash in Feb, so I restarted the server. I was then able to run the /usr/local/cpanel/scripts/maintenance script, and now "upcp --force" appears to be running fine. -Michael
    0
  • cPanelMichael
    Update: I noticed that the last server restart was from before the crash in Feb, so I restarted the server. I was then able to run the /usr/local/cpanel/scripts/maintenance script, and now "upcp --force" appears to be running fine. -Michael

    Hello, I'm happy to see the issue is now addressed. It seems like there may have been some hanging processes that needed to be killed (the restart would have killed any hanging processes). Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.