/home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 1799.

[4u123]

The permissions on /home/username/.cagefs are root:root 0701

Attempt to package account results in...

One or more files in the home directory were not readable and were not copied. Please review the home directory upon completion of transfer

Error(s) encountered in tar during archiving:
/home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 1799.

Attempt to copy account from another server fails because of the above.

CLOUDLINUX 5.10 x86_64 standard - WHM 11.40.0 (build 19)


Has anyone else experienced this issue?

 

[iseletsk]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

This is fixed in beta version of CageFS:
Beta: cagefs 5.2-1, liblve 1.2-1.4, python-cllib 1-3
.cagefs will be created under end-user ownership

 

[4u123]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

HI, I'm glad that you've identified the problem, but currently this issue breaks the functionality of the transfer account process because it fails and will not continue.

The account transfer fails with the following error...

tar process 1018533 exited with status 13: /home/username/.cagefs: Unable to open directory: Permission denied at /usr/local/cpanel/scripts/pkgacct line 1786.
Delayed nonzero exit status at /usr/local/cpanel/scripts/pkgacct line 1787. at /usr/local/cpanel/Cpanel/IO/Tarball.pm line 198.

I've got 200 accounts I need to move to a new server as a matter of urgency and I'm not prepared to do each of those manually.

Can you suggest a workaround?

 

[4u123]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

Here is the solution I found...

Before running the account copies, run the following command from /home ...

find . -type d -name '.cagefs' -exec chmod -R +xr {} +

Adding read and execute permissions allows the directory to be added to the archive. The transfer process won't re-create the .cagefs directory at the other end, but simply removing the users from CageFS and adding them back in via WHM seems to fix that.

 

[iseletsk]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

We didn't just identified the issue, we fixed the issue. You can upgrade to beta, and the issue would be gone.

 

[4u123]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

We didn't just identified the issue, we fixed the issue. You can upgrade to beta, and the issue would be gone.

Who upgrades to a BETA in a production environment?

You realize, beta is for testing, right?

 

[iseletsk]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

If you don't mind, I will ignore your first question.

Now, when I decided how to name our releases at CloudLinux, I used this definition of beta:

A development status given to a program or application that contains most of the major features, but is not yet complete. Sometimes these versions are released only to a select group of people, or to the general public. ...
beta version - Wiktionary

If you think that beta versions never used in production, than I would like to remind you of Gmail, that was in beta for 5 years, and used by millions of people -- before it was "upgraded" from that status.

The way we, at CloudLinux define beta: releases that were tested internally, but not yet ready to be automatically upgraded on all production servers. They are given specifically so customers who have large deployments can test it on a handful of production servers -- prior to rolling out to all their servers, and so that people who need latest feature or bug fix could update their production server manually.

In cPanel release terms, I would say that cPanel's CURRENT tier corresponds to our beta, while our stable corresponds to cPanel's RELEASE tier.

Anyway -- you can always wait for it become stable.

 

[4u123]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

The fact is simply that software in beta is unfinished and will contain bugs. It is still in testing. Your stable release software contains bugs, which doesn't give your customers much confidence in your testing process. I'm unlikely to put my customers under further risk by upgrading to your beta build when you stable release doesn't work correctly.

You can't compare your software to Gmail - that's free webmail software for end users. Your software is not free and carries a far greater risk to the customer than a webmail platform. Businesses rely upon it to run their servers.

 

[bejbi]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

If you don't mind, I will ignore your first question.

Now, when I decided how to name our releases at CloudLinux, I used this definition of beta:

In cPanel release terms, I would say that cPanel's CURRENT tier corresponds to our beta, while our stable corresponds to cPanel's RELEASE tier.

Anyway -- you can always wait for it become stable.

If the account transfer is broken it should be urgently corrected. This is NOT new feature which will be tested and you can wait on it when it goes to stable.

It is a bug.

I'm using on my all servers only RELEASE version. Never CURRENT! So i'm always waiting on Your STABLE versions, never using BETA.
Beta is for testing and contains new features.

I'm a little confused on Your answer ... I transfer users from CentOS to CL so I don't have such problems, but I'm a little scared of the future ...

Wojciech

 

[kernow]

Re: /home/username/.cagefs: Unable to open directory: Permission denied at /scripts/pkgacct line 179

The beta release does fix the problem so it would make sense to use it until the stable release is available, probably in a few days. I guess the problem here is people's perception of what a beta is. Some software company's beta's are more "stable" than others...................
Our own experience with CL is that they are very quick to acknowledge and fix bugs, far quicker in fact than cpanel