FIX FOR 'The last attempt to update cPanel & WHM was blocked'
In one of the latest updates top cPanel, you have changed the minimum size of various partitions in order for updates to proceed. Many of us are now stuck with systems that unless you devise a fix will require a destructive repartitioning of our hard drives and reestablishing of all server set ups, user accounts, etc. This is extremely time consuming and can easily cause lengthy down time for all accounts and web sites involved.
We all have servers that are 100% complaint with the requirements that were established at the time they were set up. You have chosen to change these parameters without regard to those of us who are your long term customers and now we are stuck. It is your responsibility when you make changes such as these, to ensure that they are compatible with all current users.
Please devise a non-destructive upgrade path for users who are stuck with this issue.
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 request is a duplicate. It appears the attempt to merge the two requests didn't work properly.
We are working on a solution for the change in disk space requirements. Please direct your attention to the following feature request: http://features.cpanel.net/responses/whm-cpanel-upgrade-install-blocker-revert-back-to-16gb-from-3gb_3
This request is a duplicate. It appears the attempt to merge the two requests didn't work properly.
We are working on a solution for the change in disk space requirements. Please direct your attention to the following feature request: http://features.cpanel.net/responses/whm-cpanel-upgrade-install-blocker-revert-back-to-16gb-from-3gb_3
Time by time, new features are added and it requires from space then the initial release. cPanel can reduce disk limit but it may break the entire server and there is a risk of free disk.
Time by time, new features are added and it requires from space then the initial release. cPanel can reduce disk limit but it may break the entire server and there is a risk of free disk.
We all understand that programs change over time, however when a change is made to a major requirement of a system, the development team needs to devise a plan for ALL customers to be able to meet the new standards without substantial outlays of time and dollars. I agree that reducing the disk limit that si actually required just to avoid the error condition is not a fix, but that does not mena that cPanel does not need to come up with a fix that won't impact the day to day operations of us who have this issue. Some have suggested that the fix i simply to get a new server which is highly impractical and cost prohibitive for many.
We all understand that programs change over time, however when a change is made to a major requirement of a system, the development team needs to devise a plan for ALL customers to be able to meet the new standards without substantial outlays of time and dollars. I agree that reducing the disk limit that si actually required just to avoid the error condition is not a fix, but that does not mena that cPanel does not need to come up with a fix that won't impact the day to day operations of us who have this issue. Some have suggested that the fix i simply to get a new server which is highly impractical and cost prohibitive for many.
Can we please get an update on the status of this. There are a LOT of us out here who are stuck with older version of WHM/cPanel because of the short sided nature of the changes made by the development team.
Can we please get an update on the status of this. There are a LOT of us out here who are stuck with older version of WHM/cPanel because of the short sided nature of the changes made by the development team.
Now running into this on a server that is a couple years old.. had 12GB partitioned for /usr but apparently its still not enough.
Would like some way to manage and make this update work without resorting to an OS reload or purchasing a new server.
now on version: WHM 11.48.0 (build 11)
Now running into this on a server that is a couple years old.. had 12GB partitioned for /usr but apparently its still not enough.
Would like some way to manage and make this update work without resorting to an OS reload or purchasing a new server.
now on version: WHM 11.48.0 (build 11)
This request is a duplicate. It appears the attempt to merge the two requests didn't work properly.
We are working on a solution for the change in disk space requirements. Please direct your attention to the following feature request: http://features.cpanel.net/responses/whm-cpanel-upgrade-install-blocker-revert-back-to-16gb-from-3gb_3
This request is a duplicate. It appears the attempt to merge the two requests didn't work properly.
We are working on a solution for the change in disk space requirements. Please direct your attention to the following feature request: http://features.cpanel.net/responses/whm-cpanel-upgrade-install-blocker-revert-back-to-16gb-from-3gb_3
Replies have been locked on this page!