CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Running, Solving & CFD (https://www.cfd-online.com/Forums/openfoam-solving/)
-   -   libz.so.1: no version information available (https://www.cfd-online.com/Forums/openfoam-solving/146689-libz-so-1-no-version-information-available.html)

dmaz January 4, 2015 09:14

libz.so.1: no version information available
 
Dear Foamers,
I'm trying to run a Steady-state simulation using the rhoSimpleFoam solver and the k-omegaSST RASmodel.
In order to do this I have copied a tutorial folder of rhoSimpleFoam adding the new mesh.
However, I get the following errors, after 2 or 3 timesteps:

Code:

#0  Foam::error::printStack(Foam::Ostream&)addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?
#1  Foam::sigFpe::sigHandler(int)addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?
#2
addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at sigaction.c:?
#3  Foam::hePsiThermo<Foam::psiThermo, Foam::pureMixture<Foam::sutherlandTransport<Foam::species::thermo<Foam::hConstThermo<Foam::perfectGas<Foam::specie> >, Foam::sensibleInternalEnergy> > > >::calculate()addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?
#4  Foam::hePsiThermo<Foam::psiThermo, Foam::pureMixture<Foam::sutherlandTransport<Foam::species::thermo<Foam::hConstThermo<Foam::perfectGas<Foam::specie> >, Foam::sensibleInternalEnergy> > > >::correct()addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?
#5
addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?
#6  __libc_start_mainaddr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?
#7
addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
 at ??:?

Which can be the cause of these errors? It seems an installation problem right?
I'm using OpenFoam 2.3.0 on Centos 6.6 and this errors occurs also using other solvers and models.
Thanks in advance,
Dmaz

wyldckat January 4, 2015 12:53

Greetings Dmaz,

A few questions:
  1. Which installation instructions did you follow?
  2. Did you do anything differently from the instructions you followed?
Best regards,
Bruno

dmaz January 4, 2015 16:22

Hi wyldckat,
thanks you for replying.

I followed the instructions of this link:
https://openfoamwiki.net/index.php/I...HEL#CentOS_6.5

I have checked, the version of Centos: is 6.2. I havent found the instructions for that version. OF seems to work correctly but when a simulation crash it shows that error.
I'm verifing the tutorials with OF installed in two system, Ubuntu 14.04 and Centos 6.2.
The simulations crash about at the same iteration, but in Centos the errors refer also to libz.so.
Is it possible that this error doesn't affect the simulation?

Dmaz

wyldckat January 4, 2015 16:54

Hi Dmaz,

The problem shouldn't affect OpenFOAM's binaries. The message indicates that the problem is related to a binary that OpenFOAM is using to assist in handling the print stack operation, namely addr2line:
Code:

addr2line: /lib64/libz.so.1: no version information available (required by addr2line)
Although this is a bit strange, since it should not happen. You can try and diagnose this further by running:
Code:

which addr2line
ldd $(which addr2line)

To me it gave me this:
Code:

$ which addr2line
~/OpenFOAM/ThirdParty-2.3.1/platforms/linux64/gcc-4.8.4/bin/addr2line

$ ldd $(which addr2line)
    linux-vdso.so.1 =>  (0x00007fff111ff000)
    libz.so.1 => /lib64/libz.so.1 (0x0000003d5e000000)
    libc.so.6 => /lib64/libc.so.6 (0x0000003d5d000000)
    /lib64/ld-linux-x86-64.so.2 (0x0000003d5c800000)

This was because I'm using OpenFOAM 2.3.1 on CentOS 6.6. But still, the differences shouldn't be big enough.

Beyond this, it seems as the "libz.so.1" version your addr2line is getting isn't the same version of "libz.so" that was used to build addr2line. If this is the case, then you should try to remember if you had any other shell environment paths loaded up that could have interfered with the build process.

Best regards,
Bruno


All times are GMT -4. The time now is 13:28.