Update to 11.80.18 not completing
Hello,
I'm trying to hwlp a client upgrade their older WHM server, server details:
However it seems its stuck trying to do the 11.80 upgrade, and I cna't even access WHM at all anymore:
I've whitelisted my IP to make sure CPHULKD wasn't the source of blocking WHM, and even went so far as to disable it in case that was an issue, but still no access to the WHM web interface. It seems to be stuck on the updatenow function:
Any thoughts on how to proceed are appreciated.
root@con [/var/cpanel/updatelogs]# grep '' /etc/redhat-release /usr/local/cpanel/version /var/cpanel/envtype ; grep CPANEL= /etc/cpupdate.conf
/etc/redhat-release:CentOS release 6.10 (Final)
/usr/local/cpanel/version:11.78.0.30
/var/cpanel/envtype:kvm
CPANEL=releaseHowever it seems its stuck trying to do the 11.80 upgrade, and I cna't even access WHM at all anymore:
root@con [/var/cpanel/updatelogs]# ps aux | grep upcp
root 910 0.0 0.1 138704 6548 ? Ss 10:53 0:00 cPanel Update (upcp) - Slave
root 912 0.0 0.7 97244 30372 ? S 10:53 0:00 /usr/local/cpanel/3rdparty/bin/perl /usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1561388036.log
root 2320 0.0 0.0 103324 884 pts/0 S+ 11:26 0:00 grep upcp
root@con [/var/cpanel/updatelogs]# service cpanel status
cpsrvd (pid 578) is running...
I've whitelisted my IP to make sure CPHULKD wasn't the source of blocking WHM, and even went so far as to disable it in case that was an issue, but still no access to the WHM web interface. It seems to be stuck on the updatenow function:
root@con [/var/cpanel/updatelogs]# tail update.1561388036.log
----------------------------------------------------------------------------------------------------
=> Log opened from /usr/local/cpanel/scripts/updatenow (912) at Mon Jun 24 10:53:57 2019
[2019-06-24 10:53:57 -0400] Running version '11.78.0.30' of updatenow.
[2019-06-24 10:53:57 -0400] Retrieved public key from vendor: cpanel, category: release, url: https://securedownloads.cpanel.net/cPanelPublicKey.asc
[2019-06-24 10:53:58 -0400] Retrieved public key from vendor: cpanel, category: development, url: https://securedownloads.cpanel.net/cPanelDevelopmentKey.asc
[2019-06-24 10:53:58 -0400] Retrieved public key from vendor: cpanel, category: development-sts, url: https://securedownloads.cpanel.net/STSTestKey.asc
[2019-06-24 10:53:58 -0400] Detected version '11.78.0.30' from version file.
[2019-06-24 10:54:05 -0400] Target version set to '11.80.0.18'
[2019-06-24 10:54:05 -0400] Switching to version 11.80.0.18 of updatenow to determine if we can reach that version without failure.
Any thoughts on how to proceed are appreciated.
-
So I got a little farther with this yesterday. I found that the server hard drive was practically full. So I'm currently getting rid of older backups from the cpbackups folder. Hopefully when that's complete I can get the update to run proper. I still am unable to access the WHM web interface even though the process is running? I'm hoping kicking the update through will fix that issue, but if any one has any idea's please let me know. 0 -
So I'm currently getting rid of older backups from the cpbackups folder.
The server donot have a separate backup drive? What's the error when you access WHM?0 -
So I finally got this working by killing every rpm related process. This had the unintended side effect of leaving an .rpm.lock file so I had to remove that. Then I did a rebuild of the rpm db mkdir /root/old_rpm_dbs/ mv /var/lib/rpm/__db* /root/old_rpm_dbs/ rpm --rebuilddb
Then I ran a check on the cpanel rpm's to make sure they were ok/usr/local/cpanel/scripts/check_cpanel_rpms --fix /scripts/autorepair fix_duplicate_cpanel_rpms
Once that was done I made sure there were no upcp process still running, then ran the update to completion, and now my WHM web interface is back.0 -
The server donot have a separate backup drive? What's the error when you access WHM?
Unfortunately it does not have a separate drive. I'm prepping recommendations for the client for ongoing maintenance. They need to get off centos 6 before next year anyway, so hopefully I can get them to solve that issue then. As for the WHM error, there wasn't one really, I was getting the generic cannot connect error from the browser.0 -
I'm really glad to see you were able to get this working for your client and thanks for letting us know how you resolved the issue. 0
Please sign in to leave a comment.
Comments
5 comments