John Wigle reports : This email was sent out to all of those who directly purchase cPanel licenses, of course if you are like most people and do not directly own a license but get it through a datacenter you never got this email. I have pasted it below which also contains a fix for the perl problems which are causing a lot of trouble with just about everything, including email. I have corrected a few typo’s in the email so that just copy and pasting it will now work, it was not working for their version, and added a few more commands that I needed on some servers.
Here is the copy/paste version I created:
ls -alh /root/.gnupg
(just make sure it exists)
tar zxvf libwww-perl-5.805.tar.gz
tar zxvf CPAN-1.83.tar.gz
Here is the cPanel email:
The cPanel product for Linux and BSD is maturing nicely. We’ve made a long term commitment to improving its stability and performance.
However, as many of you are already aware, our software relies upon a number of third party applications and tools. We do our best to ensure compatibility, but on occasion problems can and do arise. We’ve recently experienced issues with Perl’s CPAN installer module which was updated on January 3rd. We have reported the issue to the maintainer of CPAN, and an update has been released to address the issue. However, it may take up to 48 hours for the update to reach all CPAN mirrors.
This issue should only be significant for new installations of Perl, including new installs of cPanel. We’ve introduced some changes to our Perl module installation routines to improve compatibility, and we are currently testing new code to prevent this issue from ever occurring again. Until then, these are a few of the steps that you can take to ensure continued normal operation of your cPanel server.
1. Ensure that the directory /root/.gnupg exists.
The latest versions of CPAN are using Module::Signature by default. This module will check the GPG signature of modules during their installation. If your server is using Module::Signature and this directory does not exist, then the signature check will fail and the module will not be installed or updated. This will be handled automatically in all builds dated January 4th or later.
2. Ensure that the Perl’s LWP is installed.
If LWP is not installed, and Net::FTP is not used (and it’s often skipped), CPAN will attempt to fetch the Perl module using one of the system applications, such as wget. In this case, the module will be saved without its proper extension and the installation will exit shortly after downloading the module. You can install LWP manually using the following commands:
tar zxvf libwww-perl-5.805.tar.gz
When running "perl MakeFile.PL" you will be asked several questions.
It’s safe to accept the default values.
3. Install the updated version of CPAN (1.82)
Updating CPAN will resolve both issues "1" and "2" for you as well as other issues. On productions systems (which almost always have a working LWP installed) this will occur automatically. To install CPAN manually, the steps are very similar to the above steps for LWP:
tar zxvf CPAN-1.82.tar.gz
If you experienced problems with any recent installations and resolved them, then it is recommended that you run the following command:
This command is ran automatically by our update system. Running this command on new installs will ensure a proper Perl setup, otherwise it is optional
Information Provided from http://www.eth0.us/cpanel-perl-fix