juhenriquez has asked for the wisdom of the Perl Monks concerning the following question:

Kind of in a bind here, since I heard about the bash bugs last night I decided on upgrading all off my server, not just the packages but the complete OS, it worked fine on all my servers, except my mail server, which was running Ubuntu 12.04 and I upgrade to 14.04. Everything seem running correctly but when I try to get the Zimbra service running I get the Following:
Perl API version v5.14.0 of Socket does not match v5.18.0 at /usr/shar +e/perl/5.18/XSLoader.pm line 92. Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line + 10. BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm +line 10. Compilation failed in require at /opt/zimbra/zimbramon/lib/Zimbra/Mon/ +Logger.pm line 21. BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/Zimbra/ +Mon/Logger.pm line 21. Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27. BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27 +.
I was kind of guessing it was problems with my Perl Version, So I downloaded perlbrew, but when I try to change the version from 5.18.0 to 5.14.0 I get the following:
Perl API version v5.14.0 of List::Util does not match v5.18.0 at /usr/ +share/perl/5.18/XSLoader.pm line 92. Compilation failed in require at /usr/local/share/perl/5.18.2/App/perl +brew.pm line 22. BEGIN failed--compilation aborted at /usr/local/share/perl/5.18.2/App/ +perlbrew.pm line 22. Compilation failed in require at /usr/local/bin/perlbrew line 6. BEGIN failed--compilation aborted at /usr/local/bin/perlbrew line 6.
Quite the large bind for me, any help would be appreciated.

Replies are listed 'Best First'.
Re: Ubuntu Upgrade Broke my Perl Dependant Apps
by salva (Canon) on Sep 26, 2014 at 06:31 UTC
    The new perl 5.18 is trying to load the modules compiled for the old one, 5.14.

    Check your environment variables (/PERL5.*/), they may be telling perl to do that.

Re: Ubuntu Upgrade Broke my Perl Dependant Apps
by karlgoethebier (Abbot) on Sep 26, 2014 at 10:55 UTC
    "I heard about the bash bugs last night I decided on upgrading all off my server... it worked fine on all my servers, except my mail server..."

    Pretty fearless! Seems like you had luck ;-)

    But why did you do an upgrade? Wasn't there a working Shellshock fix for Ubuntu?

    Regards, Karl

    «The Crux of the Biscuit is the Apostrophe»

      Is the Ubuntu fix is complete?

      The Register (as of AM 2014-09-26 if I read and recall correctly) suggested it's incomplete and only addresses the primary bug, not the entire problem.




      Quis custodiet ipsos custodes. Juvenal, Satires

        "...fix is complete?"

        It seems so but 'm not really shure :-( Need to read more about this crap. Here is what i just did:

        root@ubuntu:~# env var='() { ignore this;}; echo vulnerable' bash -c +/bin/true vulnerable root@ubuntu:~# aptitude install bash -s The following packages will be upgraded: bash 1 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded +. Need to get 641 kB of archives. After unpacking 0 B will be used. Do you want to continue? [Y/n/?] y Would download/install/remove packages. root@ubuntu:~# aptitude install bash The following packages will be upgraded: bash 1 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded +. Need to get 641 kB of archives. After unpacking 0 B will be used. Do you want to continue? [Y/n/?] y Get: 1 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main bash +amd64 4.2-2ubuntu2.3 [641 kB] Fetched 641 kB in 0s (729 kB/s) (Reading database ... 80529 files and directories currently installed. +) Preparing to replace bash 4.2-2ubuntu2.1 (using .../bash_4.2-2ubuntu2. +3_amd64.deb) ... Unpacking replacement bash ... Processing triggers for man-db ... Setting up bash (4.2-2ubuntu2.3) ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to p +rovide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode +. Current status: 4 updates [-1]. root@ubuntu:~# env var='() { ignore this;}; echo vulnerable' bash -c +/bin/true bash: warning: var: ignoring function definition attempt bash: error importing function definition for `var'

        Update: FYI: Yesterday evening i tried this fix on Mac OS X Lion. Didn't work.

        Regards, Karl

        «The Crux of the Biscuit is the Apostrophe»