Common Issues – Easyapache failing

Figured my “Common Issues” posts this week would be a little more specific and simple then the last few. This is an issue i’ve been noticing a new issue off and on with servers recently where easyapache will not work and fails with the following error:

root@server [~]# /scripts/easyapache
Acme::Spork version v0.0.8 required--this is only version v0.0.7  at /var/cpanel/perl/easy/Cpanel/Easy/Utils/BackGround.pm line 14.
BEGIN failed--compilation aborted at /var/cpanel/perl/easy/Cpanel/Easy/Utils/BackGround.pm line 14.
Compilation failed in require at (eval 18) line 3.
 ...propagated at /usr/lib/perl5/5.8.8/base.pm line 85.
 at (eval 16) line 3
 at /var/cpanel/perl/easy/Cpanel/Easy.pm line 15
BEGIN failed--compilation aborted at /var/cpanel/perl/easy/Cpanel/Easy.pm line 15.
Compilation failed in require at (eval 1) line 3.
 ...propagated at /usr/lib/perl5/5.8.8/base.pm line 85.
BEGIN failed--compilation aborted at /var/cpanel/perl/easy/Cpanel/Easy/Apache.pm line 8.
Compilation failed in require at /scripts/easyapache line 23.

In order to repair this, all you must do is install the Acme::Spork version v.0.0.8 that it requests. To do that just use the following commands:

root@server [~]# perl -MCPAN -e shell
cpan> install Acme::Spork

(Note: “cpan>” is a shell prompt, not part of the command)

This solves the issue with easyapache and allows you in. Please let me know if you have any issues with this solution, please post in the comments so all can benefit from any questions.

4 Replies to “Common Issues – Easyapache failing”

  1. This did not work as per below:

    cpan> install Acme::Spork
    CPAN: Storable loaded ok (v2.16)
    Going to read /home/.cpan/Metadata
    Database was generated on Mon, 13 Aug 2007 07:38:59 GMT
    Acme::Spork is up to date (0.0.7).

    We had to manually build Acme::Spork to fix.

    Cheers,

    Ben

  2. Hey Ben!

    Thanks for the comment. That’s odd it didn’t work for you. I’ve used this same method many times recently to resolve the same issue. Maybe your situation was a bit more unique. Sorry my post didn’t help!

Leave a Reply

Your email address will not be published. Required fields are marked *