Why Not Upgrade Perl I Thought
About a month ago I started receiving emails from my server about the installed version of PERL being too old and needing to be upgraded. Since my server uses WHM and cPanel, and thinking that upgrading PERL would have some pretty nasty consequences if something went wrong, I held off until I could familiarize myself with the ins and outs of what this was all about. Now that I’ve done the upgrade I’m not sure it was really so worth the wait and worry.
The first thing you want to do is backup all your installed CPAN modules. These are basically the library of functionality your system relies on to work. Pretty important stuff in there. It’s a pretty simple command though:
perl -MCPAN -e 'autobundle'
The above will create a “bundle” of all the CPAN modules you have installed to be used after the upgrade. Make a note of the bundle location though; you’ll need it later.
The instructions to do the actual installation were included in the email and is geared specifically towards cPanel servers:
cd /root wget http://layer1.cpanel.net/perl588installer.tar.gz tar -zxf perl588installer.tar.gz cd perl588installer ./install -optimize-memory
This parts pretty simple, but time consuming. The whole process is automated and should take about an hour or three. When you come back you’re going to want to install the autobundle you created earlier. To do that you’ll need this command:
perl -MCPAN -e 'install Bundle::NAME_OF_BUNDLE_YOU_CREATED_EARLER'
This is where things started getting difficult. This process is going to require all sorts of input from you. It’ll, thankfully, give you default options but the install will sit there until you enter something. All told, this process took me about 4 hours; just sitting there watching the process.
Definitely a pain but not upgrading PERL would have been worse. If you have to do it be sure to set aside an afternoon though.
Email
Twitter