Skip to main content
Sign in

CloudLinux Knowledge Base

  1. CloudLinux
  2. CloudLinux OS
  3. Python/Ruby/NodeJS Selectors

PHP Selector: "No selector dir for user XXX"

Misael Ramirez
  • Updated

Issue

The user is unable to use/access PHP Selector. Typically happens after an account migration. An error like the following is displayed when trying to access the PHP Selector:

Screenshot_20220424_102457.png

Environment

  • CageFS
  • PHP Selector

Solution

The solution is pretty straightforward, we just need to run the following commands:

# /usr/sbin/cagefsctl --rebuild-alt-php-ini $USER
# /usr/sbin/cagefsctl --force-update && /usr/sbin/cagefsctl -m $USER

If the issue is reproducible with every new account, please reinstall the following packages and reinitialize CageFS:

# yum reinstall lvemanager cagefs alt-python27-cllib
# cagefsctl -r

Cause

The issue is caused due to the lack of the .cl.selector directory in the user's home directory, which is vital for the correct operation of the Selector as it contains its main configuration files. 

 

 

Comments

3 comments

Date Votes
  • David Ferguson

    What causes it and how do we prevent it from happening again?

    0
  • Bogdan Shyshka

    David, most likely it's happening due to some manual interaction with .ini files by a user.

    Is this regularly happening to some users on your server? If so we would like to investigate and find the root cause. Consider creating a ticket next time.

    0
  • David Ferguson

    This started after an IP change on our server. I tracked it down to LiteSpeed not being active due to it detecting a license issue. After fixing that, the PHP selector seemed to right it self.

    I find a lot of documentation online seems lacking on hints as to what the cause to be, or lacking in steps to identify and rectify the issue.

    0

Please sign in to leave a comment.

Related articles