Skip to main content

The last attempt to update cPanel & WHM was blocked.

PCZero
When I logged onto WHM today I saw the error message "The last attempt to update cPanel & WHM was blocked.". When I view the current disk usage in WHM I see this... /dev/sda3 9.8G 6.9G 2.4G 75% /usr How do I rectify this situation so I can continue to get updates? I did search the forums and saw a related thread from a year or o back but it did not offer any help to me.

Comments

52 comments

Date Votes
  • Metro2
    Thank you!
    0
  • cPanelChrisD
    ]Would you please post the steps to the solution that Chris provided for you?

    Please keep in mind that this should be considered a last resort to get things going. The long-term goal should be to provision a new server with an appropriate disk partitioning scheme and migrate. Here's the steps that I provided, slightly modified for further clarification: Moving /usr/local/cpanel to another location 1) Ensure that there are no "immutable" files under /usr/local/cpanel that will cause the directory move to fail. The cPanel software does not require or use immutable file attributes:
    chattr -f -R -i -a /usr/local/cpanel
    2) Ensure that you don't have any SSH or console terminals open that have a current working directory under /usr/local/cpanel. If there are, simply change the shell to use another working directory, such as "cd /root". 3) Shut down all WHM/cPanel services and the cron service. We do not want any services to automatically start that may open a file under /usr/local/cpanel:
    service cpanel stop service crond stop service exim stop service httpd stop killall leechprotect
    4) At this point, if your server isn't running any unusual services, no processes should have a file open under the /usr/local/cpanel path, which can be verified by running "lsof | grep /usr/local/cpanel" and it should return no output:
    lsof | grep /usr/local/cpanel
    If it does print anything then you'll want to stop the service or kill the process listed. Some third-party software may also keep files open under this path and those services would need to be stopped. 5) Create the new base path where you're going to move the cpanel directory:
    mkdir -p /home/usr/local
    6) Run lsof one more time to make sure it doesn't print anything and then move the directory:
    lsof | grep /usr/local/cpanel mv /usr/local/cpanel /home/usr/local/cpanel
    7) Ensure that the move completed without errors and that the "/usr/local/cpanel" directory no longer exists. 8) Create an empty /usr/local/cpanel directory with correct permissions:
    mkdir /usr/local/cpanel chmod 711 /usr/local/cpanel
    9) Make a backup of /etc/fstab, and then add a bind-mount entry to mount /home/usr/local/cpanel on /usr/local/cpanel:
    cp /etc/fstab /etc/fstab.bak echo "/home/usr/local/cpanel /usr/local/cpanel none rw,bind 0 0" >> /etc/fstab
    10) Check /etc/fstab and compare it to the backup, you should see the original /etc/fstab contents with the following line added at the bottom:
    /home/usr/local/cpanel /usr/local/cpanel none rw,bind 0 0
    11) Mount the directory, then perform a directory listing to make sure you see the usual contents of /usr/local/cpanel there:
    mount /usr/local/cpanel ls /usr/local/cpanel
    12) Reboot the server. This will ensure that any stale CageFS or VirtFS filesystem mounts are cleared, restarts any services that were stopped, and most importantly will test the /etc/fstab entry during the boot process to make sure it will work, so that there will not be any surprises in the future. Be prepared to perform maintenance via the server console if a problem with /etc/fstab causes the boot process to fail. That's it. Continue to reference "/usr/local/cpanel" in any custom code you may write (pretend "/home/usr/local/cpanel" doesn't exist). The use of a bind-mount rather than a symlink should ensure that everything works as if the files were located under the original path.
    0
  • kernow
    It seems one of our servers now has this problem, thanks for the info cPanelChrisD :cool:
    0
  • kejebe
    So has anyone tried the solution to this problem provided by cPanelChrisD? There was a flurry of posts about this issue up till he posted his solution and then nothing (crickets). So does it work or did everyone just give up?
    0
  • kernow
    We will be doing this work on one server early on Monday 15th and will post here after completion. (hopefully with a smile)
    0
  • customtacos
    We've experienced this on a few of our servers, too (SoftLayer provisioned), and have been pretty frustrated with this change. A couple of things that may help: 1. I've found that a simple reboot will sometimes clear up some disk space on /usr 2. Sometimes CPanel dums core files and simply removing these may get you enough free space. See instructions here: /http://www.rackaid.com/blog/cpanel-disk-space-warning/ 3. Instead of symlinking the /usr/local/cpanel folder, what about symlinking the /usr/local/apache/logs or domlogs folder over to /home? Just a couple of thoughts. Hope they help someone.
    0
  • kernow
    Well, we got errors at the first command so decided not to continue. Can we ignore these or not? Below is just a selection of the thousands that appear:
    chattr -R -i -a /usr/local/cpanel chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/filemanager/doupload-ajax.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/filemanager/languages chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/filemanager/codepress chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/mailscanner/mailscanner chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/mail/img chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/locale_css/cs.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/locale_css/zh_tw.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/locale_css/fi.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/locale_css/vi.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/locale_css/pl.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/locale_css/fil.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/css2/ssl/list-certs.css.gz chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/css2/ssl/list-certs.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/angular-ui-bootstrap chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/ckeditor chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/jquery chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/fontawesome chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/bootstrap chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/jquery-ui-themes chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/angularjs/current chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/underscorejs chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/chosen chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/requirejs chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/elfinder chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/jquery-ui chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/ui-fonts chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/bootstrap-rtl chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/err/codepress chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/cjt/cldr chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ftp/list_ftp.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ftp/ftp_set.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ftp/sessions.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/delete_csr.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/upload_key.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/list_csrs.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/manage_share.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/delete_cert.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/delete_key.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3/.locale.help/es/ssl/index.tt chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/ja.css.gz chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/bn.css.gz chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/es.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/zh.css.gz chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/ar.css.gz chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/pt.css.gz chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/french-utf8.css chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/langcss/fr.css hattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/top-header-bg.jpg chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/help_on.gif chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/top-billboard.jpg chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/help_off.gif chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/top-header.jpg chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/preview.jpg chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/home_on.gif chattr: Operation not supported while reading flags on /usr/local/cpanel/base/frontend/x3mail/branding/servers/previewsm.jpg chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/save.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/security-questions.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/delaccessip.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/reset.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/accessip.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/addaccessip.html chattr: Operation not supported while reading flags on /usr/local/cpanel/base/webmail/x3/security/answers.html
    0
  • RandallJ
    Will try this tonight I hope..
    0
  • cPanelChrisD
    ]Well, we got errors at the first command so decided not to continue. Can we ignore these or not?

    All of the files that you listed are symlinks which do not support attributes. I see 1518 symlinks under /usr/local/cpanel on my test system so there are going to be quite a few of those messages which can be ignored. # lsattr /usr/local/cpanel/base/frontend/x3/3rdparty/bootstrap lsattr: Operation not supported While reading flags on /usr/local/cpanel/base/frontend/x3/3rdparty/bootstrap # ls -l /usr/local/cpanel/base/frontend/x3/3rdparty/bootstrap lrwxrwxrwx 1 root root 36 Oct 9 13:08 /usr/local/cpanel/base/frontend/x3/3rdparty/bootstrap -> ../../../../3rdparty/share/bootstrap/ I will update the original post to add the "-f" option for chattr which prevents it from printing these types of messages.
    0
  • kernow
    cPanelChrisD Thanks and Happy Christmas / Holidays. The move completed without errors :)
    0
  • kernow
    Ah, we spoke too soon :( local emails getting delivered but an auto response is saying the delivery failed because of missing libraries:
    The following text was generated during the delivery attempt: ------ pipe to |/usr/local/cpanel/bin/autorespond madeline@xxx.org /home/xxxxx/.autorespond generated by madeline@xxxx.org ------ /usr/local/cpanel/bin/autorespond: error while loading shared libraries: /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/5.14.4/x86_64-linux-64int/auto/attributes/attributes.so: cannot open shared object file: No such file or directory
    Also, a cron job is having errors:
    repquota: Cannot resolve mountpoint path (deleted)/home/cagefs-skeleton/usr/local/cpanel/Cpanel: No such file or directory repquota: Cannot resolve mountpoint path (deleted)/home/cagefs-skeleton/usr/local/cpanel/3rdparty/perl: No such file or directory repquota: Cannot resolve mountpoint path (deleted)/home/cagefs-skeleton/usr/local/cpanel/3rdparty/lib: No such file or directory repquota: Cannot resolve mountpoint path (deleted)/home/cagefs-skeleton/usr/local/cpanel/3rdparty/share: No such file or directory repquota: Cannot resolve mountpoint path (deleted)/home/cagefs-skeleton/usr/local/cpanel/3rdparty/php: No such file or directory repquota: Cannot resolve mountpoint path (deleted)/home/cagefs-skeleton/usr/local/cpanel/whostmgr/docroot/cgi/softaculous: No such file or directory
    0
  • cPanelChrisD
    ]Ah, we spoke too soon :(

    Those errors are due to the CloudLinux CageFS mounts not being updated for the new /usr/local/cpanel mount, so any processes running inside of CageFS would have this problem. I was able to replicate and resolve the problem on a CloudLinux test server and the solution is to re-mount CageFS for all users:
    /usr/sbin/cagefsctl --remount-all
    I actually think it would be best to reboot the server at the end. This would take care of restarting services and also clean up any stale filesystem mounts with CageFS or VirtFS, and also tests the new /etc/fstab entry to ensure the system will boot properly so that there are no surprises later.
    0
  • kernow
    Hi, Are you saying this is also the possible cause of the missing libraries in the mail delivery error? BTW the files are there of course. reboot a server this close to Christmas? eek! far too scary !
    0
  • cPanelChrisD
    ]Hi, Are you saying this is also the possible cause of the missing libraries in the mail delivery error? BTW the files are there of course. reboot a server this close to Christmas? eek! far too scary !

    Yes. The 'missing' libraries are also under the /usr/local/cpanel path, so the stale CageFS mounts would also cause this. Rebooting the server now and resolving any problems that you might find is better than having a reboot happen at an unexpected time due to a crash or power-outage at the worst possible time and then finding there is a boot problem.
    0
  • joshstein
    How much space does cPanel really need? The full 3GB? This is very disappointing that this change was made when some of the largest hosting providers partitioned in a certain way that now would require a OS reload. Its not as easy getting new servers and just transferring accounts. These days there is a lot of security work needed before a server is brought online and those guys charge a pretty penny! We have servers that are impacted (from Softlayer and running Cloudlinux) and I've been a long-time cPanel customer. I hope someone at cPanel can come up with a reliable solution even if that means those impacted manually changing a setting somewhere to require less than 3GB if the full 3GB really isn't needed.
    0
  • cPanelMichael
    ]I hope someone at cPanel can come up with a reliable solution even if that means those impacted manually changing a setting somewhere to require less than 3GB if the full 3GB really isn't needed.

    You can review the previous posts to this thread for a workaround if you don't have sufficient space. As far as a native feature, you could open a feature request for that via: Submit A Feature Request Thank you.
    0
  • kernow
    Our cpanel move to /home as detailed earlier was a success. The errors we had after the move were also fixed after running;
    /usr/sbin/cagefsctl --remount-all
    ( for CloudLinux servers ) Note, although we expect no reboot errors we have not rebooted yet. We have a planned maintenance window shortly after Christmas for this particular server and so will reboot it then. Doing so now with so many eCommerce sites would cause complaints from clients at this their busiest time of year, should anything go wrong with a reboot.
    0
  • PCZero
    Michale I started a request. Foir some reason it is marked as being 'on moderation'... ALL USERS PLEASE VOTE FOR THIS! - Removed -
    0
  • Infopro
    ]Foir some reason it is marked as being 'on moderation'... ...

    All Feature Requests are moderated: cPanel Feature Requests System Login & Introduction Page
    0
  • PCZero
    Re: The last attempt to update cPanel & WHM was blocked. 1st I missed that there is a VERY short term work around for this issue before posting my ticket. 2nd The suggestion that the real fox is to 'just get a new server' is asinine. It would cost me a MINIMUM of $75 a month for a new server. I should not have to pay $900 a year simply because the programmers at cPanel have a 'screw the long term customers' attitude and and are so cavalier and flippant about their poor programming practices. 3rd Will we be getting a REAL fix for this issue any time soon? Simply saying 'too bad get a new server' is not a legitimate fix. As soon as a new update comes out we will have to go through this whole mess again. 4th I am EXTREMELY dyslexic and reading through 4 pages of posts to see what the final edited version of how to (temporarily) fix this is all but impossible. Is it possible to get a clean version of the steps posted in a single post or if that already exists a pointer to that post? [COLOR="silver">- - - Updated - - - OK quick question here... It was suggested that we start a ticket about this issue which I did. I then let people know about the ticket by posting a link to it. For some reason one of the fine cPanel mods deem that inappropriate and deleted the link. So my question is exactly how in the hell are others users supposed to know about the ticket and find it fi you remove the link. Kind of looks like you guys do not want people to know it is there and vote for it... SMH!
    0
  • PCZero
    ]SoftLayer doesn't offer that sort of Partition Template any longer, not sure if they ever did.

    They absolutely 100% did when YOU GUYS had that as your RECOMMENDED set up. Please stop trying to dodge the fact that there servers were set up to YOUR specifications.
    ] An OS reload doesn't make any sense unless you're trying to stay at the same level service as that old server you're on. Setting up a new server and moving over to it, does make sense. Not for this particular situation exactly of course, but hardware gets old.

    Just because hardware is old does not mean it does not function 100% up to need. You do not replace something just because it is old. There is a cost involved is replacing a server in both time and dollars. In my case, a new server is almost $75 a month more than what I am currently paying. Are you willing to cover that for me?
    ]Grabbing a new server, setting up DNS Clustering, moving accounts over to it, is easier than you might know about. Yes you're going to spend a few bucks in the setup process, but you'll be on a new-er server.

    If it is all that easy then you do it for all of us and have it is we do not have to pay any additional amount for the new servers.
    ]The reason these sorts of changes are made to cPanel are due to this comment, exactly. Not to beat you over the head with, or sell more servers for SoftLayer, the reason these changes are made is to keep cPanel easy to use for all of us.

    How exactly is making us get new servers and set up things 100% form scratch supposed to be keeping things easy?
    ]Most Hosting Providers understand the concept of moving to newer hardware every few years. I've always gone with the bare metal server minimal partitioning setup. I'm not sure offhand how many servers I've gone thru, moving to newer hardware over the past 10 years or so. But it's not that tough to do. And was always worth the trouble. I'm pretty sure this isn't an option you're interested in, or even reading about, I'm just giving another side of all this.

    I have no idea in hell what that all is supposed to mean. I move to a new server when the current one no longer meets my needs, not when a software company decides to flippantly change requirements.
    0
  • Infopro
    Your posts are always so exciting. The best answer for those looking for a workaround has been copied out of this thread and into its own, now located here: The last attempt to update cPanel & WHM was blocked - Workaround - cPanel Forums This thread has served its purpose and is now closed.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post