Skip to main content
Sign in

CloudLinux Knowledge Base

  1. CloudLinux
  2. CloudLinux OS
  3. Known Issues

Common `cldiag --all` Errors & Fixes

Taha Ali
  • Updated

Issue

This article serves as a troubleshooting hub for various errors that may be reported by the cldiag --all diagnostic command.

cldiag is a command-line utility included in CloudLinux OS, used to automatically detect and report misconfigurations or service issues that may affect system performance, LVE limits, PHP Selector, CageFS, and other components.

This guide helps identify the most common warnings and failures triggered by cldiag, offering actionable solutions and links to relevant documentation or commands for fixing each issue.

Solution

1. Check service `lvestats` is present

Check service `lvestats` is present, enabled and active: 
FAILED: Service is not active. The server can't collect and send statistics to Centralized Monitoring if service lvestats isn't present, enabled and active. 
Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue. 
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-lvestats-service"
  • Restart the node_exporter service by running:
service cl_node_exporter restart
service lvestats restart
  • You may disable the cron checker using:
cldiag --disable-cron-checkers check-lvestats-service

––––––––––––––––––––––––––––––––––––––––––––––––––––

2. Check existing JWT token

Check existing JWT token: 
FAILED: JWT token expired. Please check for JWT token in path "/etc/sysconfig/rhn/jwt.token". Try running "rhn_check" for getting a new token if it is absent. Server can't collect and send statistics to Centralized Monitoring if you don't have a correct JWT token. 
Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. 
Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue. 
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-jwt-token"

The cldiag utility checks server for the valid JWT token required for the X-Ray. With no CloudLinux OS Shared Pro license, one may experience this error message. 

a. CloudLinux Shared Pro

Check if there is a valid CloudLinux OS Shared Pro license:

# /opt/alt/python37/bin/python3 -c "from clcommon.lib.jwt_token import jwt_token_check; print(jwt_token_check())" # cldiag --check-jwt-token
  • If the result is negative, disable the cron checker with the following command:
cldiag --disable-cron-checkers check-jwt-token
  • If the result is positive, run the following command to update the license status:
rhn_check

b. CloudLinux OS Shared (NOT Shared Pro)

With the CloudLinux OS Shared edition, the JWT token issue can be ignored.

The cldiag utility checks server for the valid JWT token required for the X-Ray. With no CloudLinux OS Shared Pro license, one may experience this error message.

If the server has an IP license:

Use the following commands to update the server registration and the JWT token:

/usr/sbin/clnreg_ks --force
rhn_check

Disable the cron checker with the following command:

cldiag --disable-cron-checkers check-jwt-token

 Update cPanel using:

/scripts/upcp --force

c. In case the root cause of this error was a faulty DNS service:

# service named status 
Redirecting to /bin/systemctl status named.service 
● named.service - Berkeley Internet Name Domain (DNS) 
Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled) 
Drop-In: /etc/systemd/system/named.service.d 
└─cpanel.conf 
Active: failed (Result: exit-code) since Tue 2024-03-05 13:07:13 AEDT; 4s ago 
Process: 1614603 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, s> 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone ibrc.com.au/IN: loaded serial 2024011117 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone rcvrme.com.au/IN: loaded serial 2024012905 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone sakpainting.com.au/IN: loaded serial 2024021009 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone tuffwash.com.au/IN: loaded serial 2024020916 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone absoluteorganic.digitaljunction.com.au/IN: loaded serial 2024021505 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone crm8.alna.net.au/IN: loaded serial 2024022103 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com bash[1614604]: zone chatswoodpublicpandc.digitaljunction.com.au/IN: loaded serial 2024030405 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com systemd[1]: named.service: Control process exited, code=exited status=1 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com systemd[1]: named.service: Failed with result 'exit-code'. 
Mar 05 13:07:13 cp-10-syd2.inodecluster.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).

This issue is not related to CloudLinux or its components. You need to contact your service provider for the correct DNS servers information.

––––––––––––––––––––––––––––––––––––––––––––––––––––

3. Invalid LVE limits on server

Check the validity of LVE limits on server: 
FAILED: Invalid LVE limits on server. See doc: https://docs.cloudlinux.com/lve-limits-validation.html 
NPROC limit must be greater than EP + 15 limit, because number of processes and threads within LVE includes also Apache processes/threads, SSH sessions and etc, which enter into LVE. 
User(s): 
10267 (Both validated limits (EP, NPROC) inheritance from different sources: package and global), 
10250 (Both validated limits (EP, NPROC) inheritance from different sources: package and global), 
10320 (Both validated limits (EP, NPROC) inheritance from different sources: package and global), 
10460 (Both validated limits (EP, NPROC) inheritance from different sources: package and global), 
10253 (Both validated limits (EP, NPROC) inheritance from different sources: package and global) 
Package(s): Unlimited (NPROC is inherited from Hoster)

The automatic validation using the cldiag utility by cron job is enabled on a server by default. Users with incorrect values:

  • 10267
  • 10250
  • 10320
  • 10460
  • 10253

These users have the following limits: EP=100 and NPROC=100.

  • Fix your limits, ensuring that the NPROC limit must be greater than EP + 15. Use the lvectl command line utility: lvectl Documentation
  • For example:
lvectl set 10267 --nproc=115or lvectl set 10267 --ep=85

Pay attention to these articles:

––––––––––––––––––––––––––––––––––––––––––––––––––––

4. Check cagefs mount points exists: FAILED: There are missing mount points

Check cagefs mount points exists: 
FAILED: There are missing mount points: ['/usr/local/psa/admin/plib/modules/site-import/backend/lib/python/parallels/core/extras/ftp-migrator', '/usr/local/psa/admin/plib/modules/site-import/backend/lib/python/parallels/core/extras/web-stream-downloader', '/usr/local/psa/admin/plib/modules/site-import/backend/lib/python/parallels/core/extras/cacert']
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-cagefs-mount-points-exist"

Remove (or comment out) the mentioned mount point from /etc/cagefs/cagefs.mp
Then update and remount CageFS:

cagefsctl --force-update && cagefsctl -M

Run `cldiag --all` command to check if the problem persists. You can disable this checker using the following command:

cldiag --disable-cron-checkers check-cagefs-mount-points-exist

––––––––––––––––––––––––––––––––––––––––––––––––––––

5. Checking if /var/cagefs is located on partition with disk quota enabled

Checking if /var/cagefs is located on partition with disk quota enabled: 
FAILED: Details: /var/cagefs located on partition with quota disabled. 
Please, activate quota for /var/cagefs for better security. 
See details: https://docs.cloudlinux.com/cloudlinux_os_components/#installation-and-update-2 
Command for disabling this cron checker: 
"cldiag --disable-cron-checkers check_cagefs_partition_disk_quota"
Checking if /var/cagefs is located on partition with disk quota enabled:
FAILED: Quotas seems unworkable on this server. Please correctly setup quotas to run this checker

The message implies that the /var/cagefs directory is located on a partition without quotas configured, please check your fstab file. 

You may try the following command to remount the root partition (it shouldn't cause any disruption of service):

mount -o remount /


If you wish to enable them, you may follow these guides for cPanel servers:

It's worth noting that enabling quotas on /var/cagefs is not critical for the server's operation.

  • If you continue to receive the alert even after enabling quotas, you may choose to disable this cron checker using the following command:
cldiag --disable-cron-checkers check_cagefs_partition_disk_quota
  • Use the following command to check if the quota was disabled:
# quotaon -p / 
group quota on / (/dev/mapper/S58-root) is off 
user quota on / (/dev/mapper/S58-root) is off
  • Then check the quotas on the partition:
# quotacheck -cmug / 
#

An empty answer means that the quota is disabled.

  • Enable quota and check:
# quotaon -vug / 
/dev/mapper/S58-root [/]: user quotas turned on 

# quotaon -p / 
group quota on / (/dev/mapper/S58-root) is off 
user quota on / (/dev/mapper/S58-root) is on 
#

# quotacheck -cmug /
quotacheck: Quota for users is enabled on mountpoint / so quotacheck might damage the file.
Please turn quotas off or use -f to force checking.
#

––––––––––––––––––––––––––––––––––––––––––––––––––––

6. FAILED: Found some nonexistent user's packages. List of "user: package" separated by semicolon

Check existence of all user's packages:
FAILED: Found some nonexistent user's packages. List of "user: package" separated by semicolon: user1:package1 package; user2:package2 Package. If you want to apply package limits for those users - assign existing packages to them, otherwise limits will be applied incorrectly or not applied at all.
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-cpanel-packages"

The recommended approach is to assign the users mentioned in the warning message to packages via the cPanel interface:

  • Reassign any existing packages to these accounts. Note that this action must be performed from the control panel.
  • Modify the users and select the appropriate existing package.
  • Check the /var/cpanel/users folder and either move or delete their folder as needed.

These users and packages are:

User : Package 
user1 : package1; 
user2 : package2

You can also disable this check using the command below:

cldiag --disable-cron-checkers check-cpanel-packages

––––––––––––––––––––––––––––––––––––––––––––––––––––

7. Centralized Monitoring errors

Check service `cl_plus_sender` is present, enabled and active:
FAILED: Service is not present. Service is not enabled. Service is not active. The server can't collect and send statistics to Centralized Monitoring if service cl_plus_sender isn't present, enabled and active. Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue.
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-cl-plus-sender-service"
Check service `node_exporter` is present, enabled and active:
FAILED: Service is not present. Service is not enabled. Service is not active. The server can't collect and send statistics to Centralized Monitoring if service node_exporter isn't present, enabled and active. Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue.
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-node-exporter-service"

Check that the server has the minimal required packages for correct working of Centralized Monitoring:
FAILED: System doesn't have the package "cl-end-server-tools". It's required for Centralized Monitoring feature to work and it usually installed automatically by cron. Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue.
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-cmt-packages"

 Relaunch the activation script:

/usr/share/cloudlinux/cl_plus/manage_clplus enable

––––––––––––––––––––––––––––––––––––––––––––––––––––

8. Check service `cl_plus_sender` is present, enabled and active

Check service `cl_plus_sender` is present, enabled and active:
FAILED: Service is not present. Service is not enabled. Service is not active. The server can't collect and send statistics to Centralized Monitoring if service cl_plus_sender isn't present, enabled and active. Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue.
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-cl-plus-sender-service"
  • Restart the service and check its status:
service cl_plus_sender restart
service cl_plus_sender status
  • If it doesn't help, reinstall this package:
yum reinstall cl-end-server-tools
  • You can check if the problem persists with this command:
cldiag -a

––––––––––––––––––––––––––––––––––––––––––––––––––––

9. Check service `node_exporter` is present, enabled and active:

Check service `node_exporter` is present, enabled and active: 
FAILED: Service is not present. Service is not enabled. Service is not active. The server can't collect and send statistics to Centralized Monitoring if service cl_node_exporter isn't present, enabled and active. Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. 
Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue. 
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-node-exporter-service"Command for disabling this cron checker: "cldiag --disable-cron-checkers check-node-exporter-service"
Check service `node_exporter` is present, enabled and active: 
FAILED: Service is not active. The server can't collect and send statistics to Centralized Monitoring if service cl_node_exporter isn't present, enabled and active. Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. 
Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue. 
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-node-exporter-service"
  •  Restart the node_exporter service by running the following commands:
service cl_node_exporter restart 
service lvestats start
  • Recheck with:
cldiag --check-cm-all

––––––––––––––––––––––––––––––––––––––––––––––––––––

10. Check that the server has the minimal required packages for correct working of Centralized Monitoring

Check that the server has the minimal required packages for correct working of Centralized Monitoring: 
FAILED: System doesn't have the package "cl-end-server-tools". It's required for Centralized Monitoring feature to work and it usually installed automatically by cron. 
Link to FAQ and troubleshooting https://docs.cloudlinux.com/cloudlinux-os-plus/#faq-2. 
Please write to support https://cloudlinux.zendesk.com/ if you can't resolve the issue. 
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-cmt-packages"

Relaunch the activation script:

/usr/share/cloudlinux/cl_plus/manage_clplus enable

––––––––––––––––––––––––––––––––––––––––––––––––––––

11. Check user's low PMEM limits

Check user's low PMEM limits: 
FAILED: Some user(s) on server has low PMEM LVE limit (lower than 512 MB). 
See doc: https://docs.cloudlinux.com/limits/#limits-validation

The above warning is due to the LVE limit of a user having a PMEM value lower than 512 MB.

This warning can be ignored, as this refers to the amount of memory set for some users being too low, and while we recommend setting a value larger than 512, it is not mandatory.

You can increase the PMEM limit to at least 512M for the users. PMEM limit can be set via CloudLinux Manager > Users. More details here: 

Command for disabling this cron checker:

cldiag --disable-cron-checkers check_low_pmem_limits

––––––––––––––––––––––––––––––––––––––––––––––––––––

12. pam_lve configuration is not found

Check cagefs users can enter cagefs: 
FAILED: pam_lve configuration is not found in /etc/pam.d/su config file 
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-users-can-enter-cagefs"

The warning can be corrected by adding the necessary entries to the /etc/pam.d/su file. We can do so by running:

echo "session required pam_lve.so 500 1" >> /etc/pam.d/su
cagefsctl --force-update

To disable this cron checker:

cldiag --disable-cron-checkers check-users-can-enter-cagefs

––––––––––––––––––––––––––––––––––––––––––––––––––––

13. Check fs.enforce_symlinksifowner is correctly enabled in sysctl conf

Check fs.enforce_symlinksifowner is correctly enabled in sysctl conf: 
INTERNAL_TEST_ERROR: ValueError("invalid literal for int() with base 10: ''")
  • Check if the server's kernel is an LVE kernel.
  • The solution is to reinstall the core LVE components:
yum reinstall lvemanager lve-utils cagefs alt-python27-cllib

––––––––––––––––––––––––––––––––––––––––––––––––––––

14. FAILED: Can't read GID from /proc/sys/fs/symlinkown_gid with error

Check fs.symlinkown_gid: 
FAILED: Can't read GID from /proc/sys/fs/symlinkown_gid with error: 
[Errno 2] No such file or directory: '/proc/sys/fs/symlinkown_gid'

KernelCare patches were not loaded properly. To reload KernelCare patches:

kcarectl --unload 
kcarectl --update

If KernelCare is not installed:

a. Check if kmodlve is NOT loaded, and load it:

lsmod | grep kmodlve

b. If kmodlve is already loaded, update and remount CageFS:

cagefsctl --force-update
cagefsctl --remount-all

––––––––––––––––––––––––––––––––––––––––––––––––––––

15. FAILED: Looks like your PHP handler doesn't support CloudLinux PHP Selector

Check compatibility for PHP Selector: 
FAILED: Looks like your PHP handler doesn't support CloudLinux PHP Selector and as a result does not work http://docs.cloudlinux.com/index.html?compatiblity_matrix.html [It looks like you use mod_ruid. CloudLinux PHP Selector doesn't work properly with it. How to delete mod_ruid and install mod_suexec in cPanel https://docs.cloudlinux.com/cloudlinux_os_components/#installation-5] 
Please, see: https://docs.cloudlinux.com/command-line_tools/#check-phpselector and try to fix issue to have working selector
  1.  
    1. Make sure that the System PHP Version is set to one of the ea-phpXX ones. Attention: Selecting the alt-phpXX (as a “System PHP Version”) will break the PHP Selector.
    2. Switch the PHP-FPM to Off; the PHP Selector is not compatible with it. Note: If you have PHP-FPM enabled for existing websites, you need to disable it for them.
    3. Last but not least, make sure that the domains/accounts (where you'd like to use the PHP Selector) use the Inherited version. You need to do that because MultiPHP Manager has a higher priority than PHP Selector. So, if any other PHP version is set in this menu, it will overwrite the PHP version selected in PHP Selector for that domain.
  • If mod_RUID2 enabled, and mod_SUEXEC is NOT enabled – run the following commands to resolve these issues:
yum remove ea-apache24-mod_ruid2
yum install ea-apache24-mod_suexec

––––––––––––––––––––––––––––––––––––––––––––––––––––

16. FAILED: Choose one of ea-php versions instead of alt-php in cPanel MultiPHP Manager for PHP Selector to start working

Check MultiPHP system default php version:
FAILED: Choose one of ea-php versions instead of alt-php in cPanel MultiPHP Manager for PHP Selector to start working.

It appears that this issue is related to the PHP Selector feature settings on your server. Refer to this guidance: PHP Selector Integration with cPanel

First thing you need to do is to verify that your accounts has PHP-FPM disabled on WHM > MultiPHP Manager page (locally for account and globally on the whole server) because PHP-FPM is incompatible with Cloudlinux components such as stated here: https://docs.cloudlinux.com/shared/limits/#compatibility-matrix 

Second thing - verify that accounts has PHP Version set to "Inherited" on WHM > MultiPHP Manager page such as stated here: https://docs.cloudlinux.com/php_selector/#cpanel 
Please note that PHP Selector does not work when alt-php version is selected as system default in MultiPHP Manager. Only ea-php versions should be selected there.

Third thing - make sure that EasyApache4 profile is installed from CloudLinux. If you are not sure - just select any from the list available on WHM > EasyApache4 page and provision it.
Then: CageFS > Enable All:

# /usr/sbin/cagefsctl --enable-all

––––––––––––––––––––––––––––––––––––––––––––––––––––

17. FAILED: Web-server user 'nobody' is not in protected group specified in /proc/sys/fs/symlinkown_gid

1. Change the GID of processes that cannot follow a symlink (according to the output of this command):

id nobody

2. Edit the /etc/sysctl.conf file, add or edit the line:

fs.symlinkown_gid = XX

3. Then execute:

sysctl -p

Cause:

  • On a standard RPM Apache installation, Apache is usually running under GID 48.
  • On cPanel servers, Apache is running under user nobody, GID 99.
  • Most likely, in this case, the fs.symlinkown_gid parameter is defined incorrectly in the /etc/sysctl.conf or not defined at all.

––––––––––––––––––––––––––––––––––––––––––––––––––––

18. FAILED: Command 'unset BASH_ENV;

Check cagefs users can enter cagefs:
FAILED: Command 'unset BASH_ENV; su 'cylas.tee' -s /bin/bash -c 'echo -n "Logged in as: $(whoami) - $(id -u) "; [ "$(id -u)" == "1041" ] && ls /var/.cagefs'' returned non-zero exit status 1.; Output was: "su: cannot open session: Cannot make/remove an entry for the specified session"
Command for disabling this cron checker: "cldiag --disable-cron-checkers check-users-can-enter-cagefs"

There is no need for concern regarding this warning.

  • Update and remount CageFS:
cagefsctl --force-update && cagefsctl -M
  • Disable the cron checker:
cldiag --disable-cron-checkers check-users-can-enter-cagefs

---------------------------------------------------------------------------------------------------------------------------

If the message also contains the following error:

"su: cannot create child process: Resource temporarily unavailable"

For example:

Check cagefs users can enter cagefs:
    FAILED: Command 'unset BASH_ENV; su 'timetunn' -s /bin/bash -c 'echo -n "Logged in as: $(whoami) - $(id -u) "; [ "$(id -u)" == "1008" ] && ls /var/.cagefs'' returned non-zero exit status 1.; Output was: "su: cannot create child process: Resource temporarily unavailable"
Command for disabling this cron checker:  "cldiag --disable-cron-checkers check-users-can-enter-cagefs"

The error message suggests that there was a resource issue when trying to create a child process. This can happen if the system is under heavy load or if there are limits being reached.

Check user limits:

lveinfo -d --period=1d --by-fault=any --limit=30 --show-columns="ID,lCPU,CPUf,lPMem,PMemF,lEP,EPf,lNPROC,NPROCf,lIO,IOf,lIOPS,IOPSf"

You may need to check one of the following solutions:

1- The LVE limits may be upraised in UI (Cloudlinux Manager -> Users - click on pencil on the right side) or with a CLI tool lvectl.

2- Updating and remount CageFS may resolve the issue as per the above command.

3- This error often arises because the maximum number of processes (or threads) that a user can create has been reached. Linux systems have limits set to prevent any single user from exhausting all system resources.
You can view and modify these limits using the ulimit command. For the user in question, you can check the current limit by switching to the user and running:

ulimit -u

The above command shows the maximum number of processes available to the user. To temporarily change this limit for testing purposes, you can run:

ulimit -u <new_limit>

Replace <new_limit> with a higher value. To make permanent changes, you will need to edit the /etc/security/limits.conf file.

––––––––––––––––––––––––––––––––––––––––––––––––––––

19. Check suexec has cagefs jail

The following can be seen in PHP selector interface and cldiag:

Check suexec has cagefs jail:
    FAILED: Binary without CageFS jail  Fix that issue to be sure that users run their sites inside CageFS and provide stable work of sites that are using apache suexec module. This may improve server security
See details: https://docs.cloudlinux.com/command-line_tools/#check-suexec

There are 1 errors found.

Solution:

For DirectAdmin:

cd /usr/local/directadmin/custombuild
./build update
./build apache

For cPanel:

# cd ~; wget https://repo.cloudlinux.com/cloudlinux/sources/cloudlinux_ea3_to_ea4; sh cloudlinux_ea3_to_ea4 --convert

For CloudLinux 10 + cPanel:

Update the package ea-apache24-mod_suexec and its dependencies:

# yum update ea-apache24-mod_suexec --enablerepo=cl*

Recheck:

# cldiag --check-suexec

––––––––––––––––––––––––––––––––––––––––––––––––––––

20- Check mount with hidepid=2 option

heck mount with hidepid=2 option:
    FAILED: Details: hidepid protection disabled.
Please, mount system with hidepid=2 for better security.
Read more about hidepid option here: https://docs.cloudlinux.com/cloudlinux_os_kernel/#remounting-procfs-with-hidepid-option

1. To disable hidepid, add the following to the /etc/fstab:

proc /proc proc defaults,hidepid=0,gid=0 0 0

2. Or you can specify the desired hidepid and gid values explicitly:

proc /proc proc defaults,hidepid=2,gid=clsupergid 0 0

3. You should execute the following:

mount -o remount /proc

4. In some cases it is necessary to remount fully manually:

mount -o remount,defaults,hidepid=2,gid=clsupergid /proc

Reference:

21- FAILED: error getting user's packages:

Check existence of all user's packages:
    FAILED: error getting user's packages: 
Command for disabling this cron checker:  "cldiag --disable-cron-checkers check-cpanel-packages"

The solution is to assign the users listed in the warning message to packages using the cPanel interface.

In this situation, you will need to reassign any existing packages to these accounts. Note that this must be done from the control panel side. Please modify the users and select existing package. Looks like its old package was removed. Also if user was also removed please check /var/cpanel/users folder and move outside or delete his folder.
 
You can also disable this check using the command below:

cldiag --disable-cron-checkers check-cpanel-packages

 

Useful Links

 

 

 

Comments

0 comments

Please sign in to leave a comment.

Related articles