|P is for Practical|
Vendor program can't load *.so file after OS patchingby c01362 (Initiate)
|on Dec 20, 2019 at 18:45 UTC||Need Help??|
c01362 has asked for the wisdom of the Perl Monks concerning the following question:
We have a lab application running on RHEL 6 with poor vendor support that started having issues after applying the latest OS patches.
Here's the error encountered when we try to start the app:
Can't load '/home/test/lib/aarch4p.so' for module aarch4p: /home/test/lib/aarch4p.so: wrong ELF class: ELFCLASS64 at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/DynaLoader.pm line 230. at /home/test/bin/startup line 54
Line 54 of the startup script is simply "use aarch4p;"
And line 230 (and 231) of the DynaLoader.pm file is:
my $libref = dl_load_file($file, $module->dl_load_flags) or
croak("Can't load '$file' for module $module: ".dl_error());
I'm certain some shared object/library/file updated as part of the OS patching is the source of the problem but I'm not sure where to begin looking.
I'm not a Perl expert by any stretch of the imagination so if you are gracious enough to reply, please be as explicit as possible.
I realize I haven't provided much information here but any suggestions on where to look for the source of the issue would really be appreciated.