nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Template issues in TS 7.2.1

Light_House

Hello everyone,

We have just installed TS 7.2.1 on Linux server. Now, when we try to open some of our portal templates, we get the following errors.

Root cause:
Can't load '/usr1/iw-home/TeamSite/iw-perl/site/lib/auto/DBI/DBI.so' for module DBI: /usr1/iw-home/TeamSite/iw-perl/site/lib/auto/DBI/DBI.so: ELF file data encoding not little-endian at /usr1/iw-home/TeamSite/iw-perl/lib/DynaLoader.pm line 229. at /usr1/iw-home/TeamSite/iw-perl/site/lib/DBI.pm line 256 BEGIN failed--compilation aborted at /usr1/iw-home/TeamSite/iw-perl/site/lib/DBI.pm line 256. Compilation failed in require at /usr1/iw-home/TeamSite/local/bin/BCBSMA/type_speciality_inline.ipl line 12. BEGIN failed--compilation aborted at /usr1/iw-home/TeamSite/local/bin/BCBSMA/type_speciality_inline.ipl line 12.

Has anyone seen this error message in the past? Please share some ideas where we should look to get rid of this error message.

Many many thanks in advance.

TS 7.2.1
Linux OS

Find more posts tagged with

Comments

nipper

You need to debug your perl DBI install.

From the error I assume this never worked on this server

Where did the DCTs come from ? Who loaded (or not) DBI ?

ISCBorisB

Hello everyone,

We have just installed TS 7.2.1 on Linux server. Now, when we try to open some of our portal templates, we get the following errors.

Root cause:
Can't load '/usr1/iw-home/TeamSite/iw-perl/site/lib/auto/DBI/DBI.so' for module DBI: /usr1/iw-home/TeamSite/iw-perl/site/lib/auto/DBI/DBI.so: ELF file data encoding not little-endian at /usr1/iw-home/TeamSite/iw-perl/lib/DynaLoader.pm line 229. at /usr1/iw-home/TeamSite/iw-perl/site/lib/DBI.pm line 256 BEGIN failed--compilation aborted at /usr1/iw-home/TeamSite/iw-perl/site/lib/DBI.pm line 256. Compilation failed in require at /usr1/iw-home/TeamSite/local/bin/BCBSMA/type_speciality_inline.ipl line 12. BEGIN failed--compilation aborted at /usr1/iw-home/TeamSite/local/bin/BCBSMA/type_speciality_inline.ipl line 12.

Has anyone seen this error message in the past? Please share some ideas where we should look to get rid of this error message.

Many many thanks in advance.

TS 7.2.1
Linux OS

This is one of the typical manifestations of "Perl Contamination", like TS Perl V5.8 trying to load Weblogic
Perl V5.6 Libraries.

So... Do you have "other" Perls installed in the same Environment (Tomcat, Weblogic, Oracle, you name it...)?

What is your Platform? Formally, the error means that you are either trying to use big endian loader in little
endian context or conversely, have big endian DBI.so and trying to load it a little endian context.
(Little endian platforms are usually x86-32, x86-64 Intel/Pentium, etc...).

Light_House

Many thanks to Nipper and Boris for the prompt response. This is a freshly TS 7.2 installation on this server. And we are trying to use this template on this server for the first time.

Yes we have other Perls installed in the same environment such as Oracle, WebLogic. Our platform is x86_64 x86_64 x86_64 GNU/Linux.

Thanks in advance.

Adam Stoller

From the error message it appears to be using the correct perl (i.e. iwperl) as it's complaining about libraries within IWHOME (the other Perl programs installed on that server wouldn't probably know about that path - unless you're running one of them on a script that explicitly includes the IWHOME/iw-perl libraries)

iwperl is a 32-bit program. You are on a 64-bit server. Is it possible that some of the libraries on the server are not 32-bit-backward-compatible?

ISCBorisB

Many thanks to Nipper and Boris for the prompt response. This is a freshly TS 7.2 installation on this server. And we are trying to use this template on this server for the first time.

Yes we have other Perls installed in the same environment such as Oracle, WebLogic. Our platform is x86_64 x86_64 x86_64 GNU/Linux.

Thanks in advance.

Do you have DBI.pm Module in the ...iw-perl/vendor/lib directory?

In other words, are you sure that DBI has been installed with TS? I *seem* to recall that
you had to compile it in Linux installations (not for Windows though). If it has not been
installed automatically, how did you get "DBI.so" Module?

Light_House

Thanks Ghoti, Its a valid point that you mentioned, but our other Solaris server also a 64-bit server with TS 6.5 installed. That is working perfectly fine with the same perl module.

@Boris, yes, we have DBI.pm module in the ...iw-perl/vendor/lib directory. I got the information from the Admin that it was installed automatically.

Many Thanks.

nipper

Thanks Ghoti, Its a valid point that you mentioned, but our other Solaris server also a 64-bit server with TS 6.5 installed. That is working perfectly fine with the same perl module.

@Boris, yes, we have DBI.pm module in the ...iw-perl/vendor/lib directory. I got the information from the Admin that it was installed automatically.

Many Thanks.

If it is installed correctly then have the Admin write a simple perl script to use it.

screenshot.png

Adam Stoller

Thanks Ghoti, Its a valid point that you mentioned, but our other Solaris server also a 64-bit server with TS 6.5 installed. That is working perfectly fine with the same perl module.

@Boris, yes, we have DBI.pm module in the ...iw-perl/vendor/lib directory. I got the information from the Admin that it was installed automatically.

Many Thanks.

The error message seems reasonably clear:

Can't load '/usr1/iw-home/TeamSite/iw-perl/site/lib/auto/DBI/DBI.so' for module DBI: /usr1/iw-home/TeamSite/iw-perl/site/lib/auto/DBI/DBI.so: ELF file data encoding not little-endian at /usr1/iw-home/TeamSite/iw-perl/lib/DynaLoader.pm

- I suggest you run file on all the libraries in /usr1/iw-home/TeamSite/iw-perl/site/lib/auto on both of those servers -- and also verify that they didn't copy files from Solaris to Linux (you did say the new server is Linux, and you're saying that the old server is Solaris - so you're kind of comparing apples and oranges there when you say it works on one but not the other)