Problem running vendor daemon "INTEL" on Linux 64-bit

Problem running vendor daemon "INTEL" on Linux 64-bit

edwin.l.blosch@lmco.com's picture

We successfully installed Composer XE 2013 and then the license manager software.  We then started the lmgrd process and it gave an error trying to start up the process named "INTEL".  It tried several times at different ports, then gave up.  Does anyone know what the issue could be?

I tried to invoke "./INTEL" from the command line, just to see if I could glean anything, and it immediately returns with "Floating point exception". 

Thanks,

Ed

12 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.
hubert-haberstock (Intel)'s picture

Which OS are you running on the license server (lsb_release -a)?
Regards, Hubert.

edwin.l.blosch@lmco.com's picture

I believe it's SuSE 11.  The machine is physically off the network so I would have to walk over there to try the lsb_release command. Let me know if you specifically need the output of that command.  Otherwise, I hope the info below can suffice.

#platform: linux-suse11-x86_64
#gcc version: ['4', '3', '4']
#gcc lib: /usr/lib64/gcc/x86_64-suse-linux/4.3/libgcc.a
#gfortran version:  None
#Details:
#   platform.platform = Linux-2.6.32.59-0.3-default-x86_64-with-glibc2.2.5
#   platform.architecture = ('64bit', 'ELF')
#   platform.machine = x86_64
#   platform.uname = ('Linux', 'fwhpctest', '2.6.32.59-0.3-default', '#1 SMP 2012-04-27 11:14:44 +0200', 'x86_64', 'x86_64')
#   platform.libc_ver = ('glibc', '2.2.5')
#   platform.dist = ('SuSE', '11', 'x86_64')
#   sys.version = 2.6.8 (unknown, May 29 2012, 22:30:44)
#[GCC 4.3.4 [gcc-4_3-branch revision 152973]]
#Filtered /proc/meminfo output:
#MemTotal:       529419776 kB
#Filtered /proc/cpuinfo output:
#model name     : Intel(R) Xeon(R) CPU E7- 8870  @ 2.40GHz
#cpu MHz                : 1064.000
#cache size     : 30720 KB

edwin.l.blosch@lmco.com's picture

I believe it's SuSE 11.  The machine is physically off the network so I would have to walk over there to try the lsb_release command. Let me know if you specifically need the output of that command.  Otherwise, I hope the info below can suffice.

#platform: linux-suse11-x86_64
#gcc version: ['4', '3', '4']
#gcc lib: /usr/lib64/gcc/x86_64-suse-linux/4.3/libgcc.a
#gfortran version:  None
#Details:
#   platform.platform = Linux-2.6.32.59-0.3-default-x86_64-with-glibc2.2.5
#   platform.architecture = ('64bit', 'ELF')
#   platform.machine = x86_64
#   platform.uname = ('Linux', 'fwhpctest', '2.6.32.59-0.3-default', '#1 SMP 2012-04-27 11:14:44 +0200', 'x86_64', 'x86_64')
#   platform.libc_ver = ('glibc', '2.2.5')
#   platform.dist = ('SuSE', '11', 'x86_64')
#   sys.version = 2.6.8 (unknown, May 29 2012, 22:30:44)
#[GCC 4.3.4 [gcc-4_3-branch revision 152973]]
#Filtered /proc/meminfo output:
#MemTotal:       529419776 kB
#Filtered /proc/cpuinfo output:
#model name     : Intel(R) Xeon(R) CPU E7- 8870  @ 2.40GHz
#cpu MHz                : 1064.000
#cache size     : 30720 KB

hubert-haberstock (Intel)'s picture

We support SuSE 10 SP4 onwards, but glibc 2.2.5 looks too old. Let me check.

hubert-haberstock (Intel)'s picture

glibc should be 2.5 or higher. I'm wondering why you have such old glibc on your system. The 'Floating Point Exception' error definitely is a sign of an unsupported system lib. You may consider to update your glibc or run another license server.

Pls. verify which the default glibc is:
/lib64/libc.so.6
or
ldd --version

No chance to run the Intel® Software License Manager if it's (far) below 2.5.

Hubert.

edwin.l.blosch@lmco.com's picture

GNU C Library stable release version 2.11.3 (20110527), by Roland McGrath et al.

I had reported the output of the platform.platform() function from a Python script.  I don't know why it says 2.2.5, but it also does the same on another computer which I know just got a clean RedHat EL 6 install.  My guess is that the platform module reports the libc version against which the Python interpreter was built.

At any rate, the host inquestion is well beyond glibc 2.5. 

 

hubert-haberstock (Intel)'s picture

Edwin,

Which libc is behind the symlink libc.so.6?

E.g.:
ldd INTEL | grep libc
        libc.so.6 => /lib64/libc.so.6 (0x0000003de5400000)
 ls -al /lib64/libc.so.6
lrwxrwxrwx. 1 root root 12 Jan  3  2011 /lib64/libc.so.6 -> libc-2.12.so

If libc is not actual enough you may consider creating a symlinc to a higher version of libc, if possible. If not possible, I don't see a way to run INTEL on that system.

Hubert.

hubert-haberstock (Intel)'s picture

Edwin,

Do you need more help?

Regards, Hubert.

 

edwin.l.blosch@lmco.com's picture

I will check the libc symlink today and let you know what I find.

Yes, still need the problem resolved. We decided to renew maintenance on the license so that we are justified in asking for premier support help, so the issue is still there and we still need to ultimately find a solution.

edwin.l.blosch@lmco.com's picture

Hubert,

libc.so.6 is a link to libc-2-4.so on this system.

Is that too old?

Thanks

hubert-haberstock (Intel)'s picture

Yes, libc 2.4 seems to be too old.

Login to leave a comment.