Redis EA - Can't locate cPstrict.pm in

Naila

Active Member
Jun 20, 2017
26
0
51
Indonesia
cPanel Access Level
Root Administrator
Hi,

I have followed from this guide Redis via Containers | cPanel & WHM Documentation but i get error

[[email protected] ~]$ /usr/local/cpanel/scripts/ea-podman available

Can't locate cPstrict.pm in @INC (you may need to install the cPstrict module) (@INC contains: /usr/local/cpanel /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/x86_64-linux-64int /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib /usr/local/cpanel/3rdparty/perl/532/lib/perl5/532/x86_64-linux-64int /usr/local/cpanel/3rdparty/perl/532/lib/perl5/532 /opt/cpanel/perl5/532/site_lib/x86_64-linux-64int /opt/cpanel/perl5/532/site_lib) at /usr/local/cpanel/Cpanel/Server/Type.pm line 8.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/Server/Type.pm line 8.
Compilation failed in require at /usr/local/cpanel/Cpanel/Config/LoadUserDomains.pm line 13.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/Config/LoadUserDomains.pm line 13.
Compilation failed in require at /usr/local/cpanel/Cpanel/Config/Users.pm line 9.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/Config/Users.pm line 9.
Compilation failed in require at /usr/local/cpanel/scripts/ea-podman line 39.
BEGIN failed--compilation aborted at /usr/local/cpanel/scripts/ea-podman line 39.
 

HostNoc

Well-Known Member
Feb 20, 2020
155
38
28
Ontario
cPanel Access Level
Root Administrator

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
13,259
2,086
363
cPanel Access Level
Root Administrator
@Naila - I wasn't able to reproduce this error after following the guide at Redis via Containers | cPanel & WHM Documentation as the code worked for me. Here is the output from the cptest user:

Code:
[cptest home]$ /usr/local/cpanel/scripts/ea-podman containers
{
   "ea-redis62.cptest.01" : {
      "container_name" : "ea-redis62.cptest.01",
      "image" : "redis:6.2.7",
      "pkg" : "ea-redis62",
      "pkg_version" : "6.2.7-1",
      "user" : "cptest"
   }
}
Could you submit a ticket to our team so we can investigate that directly on your machine?