perl issue in CentOS Linux release 7.8.2003 (Core)

Issues related to applications and software problems
Post Reply
wariyalvikas54
Posts: 3
Joined: 2020/09/16 09:49:28

perl issue in CentOS Linux release 7.8.2003 (Core)

Post by wariyalvikas54 » 2020/09/16 09:53:05

Hello Team

Facing below perl issue while running the fusioninventory-agent command for GLPI.

[root@del2lmsokbase ~]# fusioninventory-agent
/usr/bin/perl: symbol lookup error: /usr/local/lib64/perl5/auto/Storable/Storable.so: undefined symbol: Perl_Istack_sp_ptr

[root@del2lmsokbase ~]# rpm -qa | egrep -i 'dbi'
perl-DBIx-Simple-1.35-7.el7.noarch
libdbi-0.8.4-6.el7.x86_64
perl-DBI-1.627-4.el7.x86_64
[root@del2lmsokbase ~]# perl -v

This is perl 5, version 16, subversion 3 (v5.16.3) built for x86_64-linux-thread-multi
(with 40 registered patches, see perl -V for more detail)

Copyright 1987-2012, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

[root@del2lmsokbase ~]# cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)

Let me know if any further logs are required.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: perl issue in CentOS Linux release 7.8.2003 (Core)

Post by TrevorH » 2020/09/16 15:59:25

Your problem appears to be self-inflicted since nothing supplied by CentOS installs under /usr/local at all. That means that whatever it is that is complaining is something that you have built and installed there.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

wariyalvikas54
Posts: 3
Joined: 2020/09/16 09:49:28

Re: perl issue in CentOS Linux release 7.8.2003 (Core)

Post by wariyalvikas54 » 2020/09/18 13:07:23

That means that whatever it is that is complaining is something that you have built and installed there.

--> We have installed the GLPI agent in this server for monitoring purpose . So you mean to say we should uninstall the GLPI agent and reinstall in a different path.

/usr/bin/perl: symbol lookup error: /usr/local/lib64/perl5/auto/Storable/Storable.so: undefined symbol: Perl_Istack_sp_ptr

--> Not sure what the error says about Storable.so

Appreciate your quick help on this but how can we resolve this error.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: perl issue in CentOS Linux release 7.8.2003 (Core)

Post by TrevorH » 2020/09/18 16:40:38

I'm suspecting you didn't install this from a package. Checking with yum provides '*/Storable.so' shows me that the file you have under /usr/local is already supplied by a CentOS package:

Code: Select all

perl-Storable-2.45-3.el7.x86_64 : Persistence for Perl data structures
Repo        : base
Matched from:
Filename    : /usr/lib64/perl5/vendor_perl/auto/Storable/Storable.so
Also, there is a package in EPEL that seems to be what you tried to install from source:

glpi.noarch 0.90.5-2.el7 epel
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

wariyalvikas54
Posts: 3
Joined: 2020/09/16 09:49:28

Re: perl issue in CentOS Linux release 7.8.2003 (Core)

Post by wariyalvikas54 » 2020/09/21 12:13:24

Thanks for your suggestions.

We were able to fix the issue by renaming the perl mentioned in the /usr/local/lib64 directory.

[root@ser~]# fusioninventory-agent
/usr/bin/perl: symbol lookup error: /usr/local/lib64/perl5/auto/Storable/Storable.so: undefined symbol: Perl_Istack_sp_ptr

[root@ser~]# ll /usr/local/lib64/
total 4
drwxr-xr-x 4 root root 4096 Oct 9 2015 perl5_bkp

The agent ran fine then.

Thanks a lot for your inputs.

Post Reply