Hi,
Einstein@home binaries would fail to run on my new 48cores nodes running Linux 64 bit OS. The same happens with Spinhenge@home. Other projects binaries are fine, except Rosetta@home which would crash and corrupt all running Rosetta if more than about 1/3 of teh cpu's are trying to run at the same time rosetta...
Coming back to Einstein@home binaries (and Spinhenge@home) they run for even less than a second before failing.
Any ideea what I must do?
Thank you.
Ionel
Copyright © 2024 Einstein@Home. All rights reserved.
48 cores linux64
)
Post some links to failed tasks so that the error messages can be inspected?
Failing that, my guess is that you still have to install the 32-bit compatibility libraries - Einstein Linux apps are all 32-bit, and that's a mistake which many users before you have made.
Well, in stderr of this tasks
)
Well, in stderr of this tasks I read:
error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
From the "Application version" I also see that you are running the "SSE2" version of the App, which is 32Bit, though I'm not sure why. Could be that you're running a 32 Bit BOINC Core Client or the Client falsely assumes that you have installed the 32 Bit compatibility libraries. I'd try that first, i.e. install the compatibility libraries for running 32 Bit Applications. My guess is that the libdl.so.2 on your system is 64 Bit only and can't be linked to the 32 Bit App.
BM
BM
I can only find stuff like
)
I can only find stuff like this in the log file:
I run this boinc version:
boinc_6.10.58_x86_64-pc-linux-gnu
.ldd says:
Going into projects/einstein.phys.uwm.edu and running this:
ldd *linux-gnu* | grep not | sort -u
gives me:I can't figure out which packages I must install for those libraries... I will try few.
In the mean time, why ldd on the boinc executable says
libdl.so.2 => /lib/libdl.so.2 (0x00007f024a895000)
while ldd on one einstein executable sayslibdl.so.2 => not found
?I guess that is not my fault.
Ionel
See section "64 Bit
)
See section "64 Bit Considerations" here.
The loader of your 64 bit system can link the 64 bit version of libm.so.6 and libdl.so.2 to the 64 Bit BOINC Client, but not to the 32 Bit Applications.
The trouble is that the BOINC Client reports that your system is capable of running 32 Bit Apps, which it actually isn't.
Possibly there is some way you could tell the Client to omit that (i.e. disable the i686-pc-linux-gnu platform), but I don't know.
There is code in BOINC to actually check for the 32 Bit libraries being present before reporting the 32 Bit platform, but this is pretty new. I don't think it's in the 6.10.58 Client, I guess it's only in some recent versions of 6.12.
Einstein@home has a Linux 64 Bit application that should work on your system, but being slightly slower than the 32 Bit SSE2 App you'll get the latter if your client reports it can run 32 Bit Apps.
BM
BM
Hi, I solved the problem
)
Hi,
I solved the problem using brute-force! :-)
I simply copied
and the two they actually link to:
from a computer which has the same architecture and were it works (e.g. the master node of those nodes).
All is in order now. Some nodes must wait a while now because they reach a limit of 16 tasks per day.
I need now to solve the same problem for Spinhenge@home. The above trick did not work. More libraries are missing...
Thank you for explaining.
Ionel
P.S. Totally unrelated, Bernd, I am considering for a while now to compile Einstein@home for IRIX. Is there a place I can get some help installing the missing libraries on my IRIX so I can complete the compilation? I will share the executable with other IRIX users when/if I succeed.
RE: Totally unrelated,
)
I'd try:
SGI freeware
* Download and unpack this archive. Run the file compile.sh from this package. It should download and compile additional source tarballs and install this software in /usr/local. This includes a recent version of gcc, newer autotools and git.
* See the license page for the actual source code of the GW application, including a build script.
Feel free to PM me if you have further questions or ask these in the forums. But please understand that support for self built applications is not our highest priority.
BM
BM