Third-party Perl scripts not working in 11.36

Gene Steinberg

Well-Known Member
May 26, 2007
163
3
168
Ah, be careful what you wish for. Once installed, my Perl scripts were broken. Mailscanner and CSF were fixed by the publishers by issuing a force update script. Other Perl scripts, including Dadamail (a mailing list manager that's been around for quite a while), give error messages on reinstallation (there are others, but this is one example).

Software error:

Could not find a suitable Params::Validate implementation: Can't locate loadable object for module Params::Validate::XS in @INC (@INC contains: ../../ ../../DADA/perllib ./lib ../ ../DADA/perllib /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8) at ../DADA/perllib/Module/Runtime.pm line 313
Compilation failed in require at ../DADA/perllib/Module/Runtime.pm line 313.
Undefined subroutine &Scalar::Util::blessed called at /usr/lib/perl5/5.8.8/overload.pm line 89.
Compilation failed in require at ../DADA/perllib/Module/Runtime.pm line 313.
at ../DADA/perllib/Params/Validate.pm line 66
Compilation failed in require at ..//DADA/App/Guts.pm line 12.
BEGIN failed--compilation aborted at ..//DADA/App/Guts.pm line 12.
Compilation failed in require at lib/DadaMailInstaller.pm line 229.
BEGIN failed--compilation aborted at lib/DadaMailInstaller.pm line 229.
Compilation failed in require at install.cgi line 18.
BEGIN failed--compilation aborted at install.cgi line 18.
I filed a ticket, but cPanel wants to blame the third-party rather than something they did. If it was one script, I might agree. But not all.

I even tried the Reinstall function on some of the Perl modules listed in WHM, and several of them failed too. Sent response messages to support.

Peace,
Gene
 
Last edited:

Infopro

Well-Known Member
May 20, 2003
17,075
524
613
Pennsylvania
cPanel Access Level
Root Administrator
Twitter
Re: When will 11.36 move to current tier?

If a 3rd party script wants to work properly with cPanel the authors need to test against the EDGE tier, in advance. This has always been the case. ConfigServer updated his scripts in advance of this rollout of 11.36. If you didn't update them, he has released a script to bring them all up to date. Sounds like you need to contact dada mail to me.

That's not blaming anyone, thats a message to get you going in the right direction.


ALL 3rd party addon scripts will need to be updated, cPanel changed how its system works.
 

CitizenK

Well-Known Member
Jun 5, 2012
64
1
58
On The Road
cPanel Access Level
Root Administrator
The update to 11.36 introduced a major change in how we handle perl on cpanel servers. cPanel now has it's own perl installation that is independent of the operating system's installation of perl. Because of this update, older perl scripts are looking to the wrong paths for perl.

You may be able to fix these scripts by updating the shebang line for perl. There is more information about this at the following urls:

cPanel & WHM 11.36 Release Notes
Prepare Your Perl Scripts for 11.36
 

Gene Steinberg

Well-Known Member
May 26, 2007
163
3
168
I got Dadamail to function that way, by revising its mail.cgi file to incorporate that line. So we're making progress.

There are still other issues that the tech is investigating.

But this is one piece of information that needs greater emphasis. That it's available doesn't mean it will be readily noticed. I sent the link to the author of Dadamail.

Peace,
Gene
 

SageBrian

Well-Known Member
Jun 1, 2002
413
2
318
NY/CT (US)
cPanel Access Level
Root Administrator
I agree that there should be a bit more warning about the dangers of updating to 11.36.
'Danger' is a strong word, but it really should be more clear that there are significant changes.

And these warnings should be on any upgrade page, whether its the 'update cpanel version' or the EasyApache page.

It would certainly help with keeping the amount of support tickets down for cpanel. :)
 

CitizenK

Well-Known Member
Jun 5, 2012
64
1
58
On The Road
cPanel Access Level
Root Administrator
An autofixer has been published to repair some third party scrips and the mod_security plugin. You can run the autofixer from the following url, replacing server.hostname.tld with your server's ip or hostname.

https://server.hostname.tld:2087/scripts/autorepair_fix_shebangs

This script will update the shebang lines as mentioned in Prepare Your Perl Scripts for 11.36
 

jimhermann

Well-Known Member
Jan 20, 2008
76
3
58
The update to 11.36 introduced a major change in how we handle perl on cpanel servers. cPanel now has it's own perl installation that is independent of the operating system's installation of perl. Because of this update, older perl scripts are looking to the wrong paths for perl.

You may be able to fix these scripts by updating the shebang line for perl. There is more information about this at the following urls:

cPanel & WHM 11.36 Release Notes
Prepare Your Perl Scripts for 11.36
cpCitizenK,

What about the Perl Scripts that are used by Squirrelmail?

Why can't I get the standard version of perl to work with existing perl scripts?

Thanks.

Jim
 

CitizenK

Well-Known Member
Jun 5, 2012
64
1
58
On The Road
cPanel Access Level
Root Administrator
Hello jimhermann,

Can you please elaborate on the issue you're having with Squirrelmail?

Regarding Perl, cPanel uses its own version of Perl and it is now located inside cPanel. This means that you can have your system standard Perl installed. cPanel's Perl will be configured with modules specially design for cPanel and its plugins. You will want to update your cPanel scripts to this version of Perl.

Please refer to the Release Notes and the Preparing your Scripts guide for more information.

Thanks!
 

jimhermann

Well-Known Member
Jan 20, 2008
76
3
58
Hello jimhermann,

Can you please elaborate on the issue you're having with Squirrelmail?
Sorry, Squirrelmail is working fine.

I misunderstood the directions. I thought that all Perl Scripts had to be updated.

Thanks.

Jim