v4.4.2 has been released for inclusion in building apache/php on cPanel servers. I’ve upgraded all of our servers with it and it appears to be working well. From the php site:
Anyone with an EV1 server running RHE will probably find that up2date isn’t working. This is as a result of upgrades that EV1 have just performed on their RHN mirrors. There is a simple fix:
More details in the EV1 Forum thread.
A new version of mod_security has been released hereChanges:
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.
There is a new release of the MailScanner script:
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: