WHM/cPanel upgrade/install blocker revert back to 1.6GB from 3GB
Since the recent change in the cPanel upgrade/install blocker free space requirement from 1.6GB to 3GB many administrators like me with 10GB "/usr" partition can't upgrade to the latest WHM/cPanel.
Apparently, the only option to rectify this problem is to do OS Reload and repartition "/usr" directory with the recommended partition size of 16GB. It would take many hours for a server with dozens of accounts to migrate, test, and deploy all the accounts.
Please implement a non-destructive way for us who are stuck with 10GB "/usr" partition to upgrade our WHM/cPanel installations.
Reference: http://forums.cpanel.net/f5/last-attempt-update-cpanel-whm-blocked-439582.html
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
This issue has been resolved for all release tiers. Case 167909.
Documentation for this is available at:
https://documentation.cpanel.net/display/ALD/Update+Preferences
This issue has been resolved for all release tiers. Case 167909.
Documentation for this is available at:
https://documentation.cpanel.net/display/ALD/Update+Preferences
This issue has been resolved for all release tiers. Case 167909.
Documentation for this is available at:
https://documentation.cpanel.net/display/ALD/Update+Preferences
This issue has been resolved for all release tiers. Case 167909.
Documentation for this is available at:
https://documentation.cpanel.net/display/ALD/Update+Preferences
Hi psm,
My team is currently working on a solution for this issue. It would create a staging directory for updates that would exist on a partition that does have more disk space. The update would be then performed from there instead of inside the /usr directory. It would automatically choose the best fit directory for you, but include an option in Update Preferences for you to set your desired directory.
I hope this helps.
Travis
Hi psm,
My team is currently working on a solution for this issue. It would create a staging directory for updates that would exist on a partition that does have more disk space. The update would be then performed from there instead of inside the /usr directory. It would automatically choose the best fit directory for you, but include an option in Update Preferences for you to set your desired directory.
I hope this helps.
Travis
Great to hear a fix is in the works.
Just a reminder to not forget to ensure cleaning up the the staging directories after the update completes.
Great to hear a fix is in the works.
Just a reminder to not forget to ensure cleaning up the the staging directories after the update completes.
Are we going to need to update in order to take advantage of this new feature?
or will there be a way to crowbar this in to the existing installation so that it can then update?
Are we going to need to update in order to take advantage of this new feature?
or will there be a way to crowbar this in to the existing installation so that it can then update?
Hi,
PPNSteve: We will clean out the files in the directories, but keep the directory structure in place.
jeffstu: You will be able to take advantage of this on existing systems. They will have a 11.44 update once to add the system in place, then perform the new update once upcp runs again.
Hi,
PPNSteve: We will clean out the files in the directories, but keep the directory structure in place.
jeffstu: You will be able to take advantage of this on existing systems. They will have a 11.44 update once to add the system in place, then perform the new update once upcp runs again.
As the end of February has passed... is there any update on this?
Thanks for your help.
As the end of February has passed... is there any update on this?
Thanks for your help.
I'm keen to know if there are any updates with this request which was planned for the end of February ?
March is quickly slipping away from us.
I'm keen to know if there are any updates with this request which was planned for the end of February ?
March is quickly slipping away from us.
Hello,
We just merged this into the actual codebase, so the development work is done. We are finishing QA right now and forecast a release for next week. This should allow update stage directories in home dirs for 11.44, 11.46, and 11.48.
Hello,
We just merged this into the actual codebase, so the development work is done. We are finishing QA right now and forecast a release for next week. This should allow update stage directories in home dirs for 11.44, 11.46, and 11.48.
Thanks for the update Travis - look forward to the release.
Thanks for the update Travis - look forward to the release.
Got this email notice after latest upcp:
space in the staging directory, "/usr/local/cpanel". The system
requires 3 GB to update; this directory only has 2.70 GB available.
staging directory. All update data will be stored here. If you take no action,
the system will continue to use this directory for future updates. To change
the location of the staging directory, use https://serverurl.com:2087/scripts2/updateconf
.
not sure if it's ready / working as I reran the update and got the same error.
Got this email notice after latest upcp:
space in the staging directory, "/usr/local/cpanel". The system
requires 3 GB to update; this directory only has 2.70 GB available.
staging directory. All update data will be stored here. If you take no action,
the system will continue to use this directory for future updates. To change
the location of the staging directory, use https://serverurl.com:2087/scripts2/updateconf
.
not sure if it's ready / working as I reran the update and got the same error.
Any update on this? Still stuck on 11.46.0 and need to get this updated.
Any update on this? Still stuck on 11.46.0 and need to get this updated.
Hi. If you are still getting an error on this please open a ticket. We have a simple solution, but at this point it should be channeled through support.
Hi. If you are still getting an error on this please open a ticket. We have a simple solution, but at this point it should be channeled through support.
Metro2,
I see you opened a ticket and we were able to help solve the issue. If anyone else runs into this issue please open a ticket.
Metro2,
I see you opened a ticket and we were able to help solve the issue. If anyone else runs into this issue please open a ticket.
will also open a ticket.. lets get this resolved and everything moving forward.
will also open a ticket.. lets get this resolved and everything moving forward.
Replies have been locked on this page!