Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

The perl module Safe::Hole could not be installed

Discussion in 'General Discussion' started by bizzy, Jan 5, 2011.

  1. bizzy

    bizzy Member

    Joined:
    Nov 30, 2006
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    151
    Being having this message several times over a couple of months. It seems to be installing the latest version but then not finding it. Bewildered.

    The email report contains these lines:


    Test Run
    ==============
    Safe::Hole object version 0.10 does not match bootstrap parameter 0.13 at /usr/lib/perl5/5.8.8/i386-linux-thread-multi/DynaLoader.pm line 253.
    Compilation failed in require at - line 1.
    BEGIN failed--compilation aborted at - line 1.


    Installer Run
    ==============
    < ....>

    Manifying blib/man3/Safe::Hole.3pm
    /usr/bin/make -- OK
    Running make install
    Manifying blib/man3/Safe::Hole.3pm
    Appending installation info to /usr/lib/perl5/5.8.8/i386-linux-thread-multi/perllocal.pod
    /usr/bin/make install UNINST=1 -- OK
    perlmod--Install done
     
  2. cPanelJared

    cPanelJared Technical Analyst

    Joined:
    Feb 25, 2010
    Messages:
    1,835
    Likes Received:
    20
    Trophy Points:
    143
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Make sure that you do not have two different Perl binary files installed at /usr/bin/perl and /usr/local/bin/perl. One should be a binary file, and one should be a symlink to the binary. It does not matter which is which, so long as they are not both binary files.

    Code:
    # ls -alh /usr/bin/perl
    -rwxr-xr-x 2 root root 15K Nov  8  2007 /usr/bin/perl*
    # ls -alh /usr/local/bin/perl
    lrwxrwxrwx 1 root root 13 May 30  2008 /usr/local/bin/perl -> /usr/bin/perl*
    If both happen to be binary files, move one and create a symlink to the remaining binary file in its place. Then run the following command:

    Code:
    # /scripts/checkperlmodules --full
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. bizzy

    bizzy Member

    Joined:
    Nov 30, 2006
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    151
    Thank you for your response but no luck. Here is the result of your file check:


    root@v4 [/usr/bin]# ls -alh /usr/bin/perl
    -rwxr-xr-x 2 root root 15K Apr 3 2009 /usr/bin/perl*
    root@v4 [/usr/bin]# ls -alh /usr/local/bin/perl
    lrwxrwxrwx 1 root root 13 Aug 5 2009 /usr/local/bin/perl -> /usr/bin/perl*


    Which presumably shows I only have one binary and it is old (03/04/09)
    The checkperlmodules generates the same failure.
     
  4. cPanelJared

    cPanelJared Technical Analyst

    Joined:
    Feb 25, 2010
    Messages:
    1,835
    Likes Received:
    20
    Trophy Points:
    143
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    That looks good. Does /scripts/checkperlmodules report any failures? Run this command:

    Code:
    # /scripts/checkperlmodules --full
    The output will be very verbose. Near the end there will be a line like this:

    Code:
    Tested 137, 137 ok, 0 failed.
    The exact number may vary, but is the number for "failed" higher than 0?

    Diagnosing problems with Perl modules can be very involved, because dependencies are often a factor. I recommend submitting a ticket so that we may investigate this directly, especially since you indicated that this has been an ongoing issue.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice