When running /scripts/perlinstaller you might be seeing this error:
This is being caused by the renaming of a function call in CPAN.pm which cPanel relies upon. Although there now appears to be a fix in the EDGE tree from the report I logged in bugzilla:http://bugzilla.cpanel.net/show_bug.cgi?id=3710There is a new version of CPAN.pm release at cpan.org this morning that addresses the issue.To manually upgrade to this fixed version do the following:
That should resolve the issue.
Changes in this new release to the script are:v2.29 – New version of MailScanner 4.49.7Upgrades can be done by following upgrade instructions.Details of the MailScanner Changes:
We have had a lot of reports about MailScanner failing with perl module errors. We’re finding that this has nothing to do with MailScanner at all. It’s because clients are not excluding perl updates from their OS providers update utility (e.g. yum or up2date). There was a recent update to RH based OS’s with a new iteration of perl which fixes some security bugs. Most likely this has downgraded installed version of perl (perhaps v5.8.7) to v5.8.0 which won’t contain all the perl modules needed to run many things including MailScanner, cPanel and it will almost definitely break cPanel stats.The fix is fairly simple:
establish which version of perl you should be using:
Check it’s correct with:
Check that /usr/local/bin/perl is a symlink to /usr/bin/perl. Then stop and restart MailScanner, cPanel and any other daemons running through the perl interpreter.
Well, with the advent of courier-imap and multi-session login for IMAP now available we’ve decided to move our email@example.com joint mailbox from POP3 access using Public ShareFolder to using an IMAP account on our local server. I’ve moved over to Thunderbird and am enjoying using it. There are some important functions from Outlook that I miss, especially having it remember frequently used folders to move mail items to, though there is a workaround. I am enjoying being able to view emails in the format they arrived in rather than the bastardised format that Outlook stores email – it still amazes me how an email client can both store email bodies in a different format to which they were delivered and to also ruin email headers to make them next to useless. Unfortunately, Outlook is a well featured email client, but I’m not sad to see the back of it.The move was important to us. We keep all email, going back to before 1998 when we started this business and so it needs to be a robust solution. The main gotcha was that courier-imap doesn’t like you using either a slash or a dot in folder names, which meant for a lot of renaming for some parts of our folder structure. Other than that, the only real issue with Thunderbird/IMAP is the somewhat flaky new email detection, but I’m getting used to it 😉
Due to popular demand, I have added a mailing list for this blog. It’s for announcement of new blog entries only and emails will be a simple title and link to the new blog entry. Access to the list is always available from the menu on the right or here.
There is a new release of the MailScanner script:
I upgraded to Firefox v1.5 yesterday without any problems. Quite a few extensions were disabled, but either upgrading or simply reinstalling them fixed them all up except for the excellent googlebar. Since they no longer seem to be developing it anymore, I decided to hack the XPI file and it works just fine in v1.5 of firefox now.For those that are desperate for their Googlbar, you can download my hacked version of googlebar-0.9.12.01-fx.xpi. Just install it and then restart Firefox.
There’s a new version of mod_security that has just been released. Here are the details:
With a wide range of experience in dealing with issues and problems caused either directly or indirectly by APF, I’ve come to the conclusion that the antidos (AD) feature of APF is much more trouble than it is worth. With it enabled, it’s apparent that the iptables rules can very quickly become dangerously full. This can lead to at least two issues:
- Ethernet traffic is slowed down due to the large number of lookup checks required
- A server can be rendered unbootable
That last point is the most dangerous. I’ve seen several servers with around 1000 IP addresses in the firewall preventing a server from booting. IIRC, this happens because APF is taking so long to load up the iptables rules, the boot sequence basically stalls and goes no further.Details on disabling antidos if you have it enabled follow…Steps to disable AD: