Hello everyone.
Been running Einstein on a variety of hosts and platforms for several years now, however, since the beginning of November 2011, I've run into a puzzling issue on my 64-bit Linux hosts. The best I could find on the forums is this thread: I have the same error as the first work-unit the original poster quoted, relating to sched_setscheduler.
What puzzles me is that I've run Einstein work-units on these machines just fine in the past. I checked the compatibility packages list in the BOINC Wiki (I'm using Kubuntu) and made sure that I already have ia32-libs and libstdc++6 installed. libstdc++5 is not available for my current release and I'm pretty sure I haven't needed to use it for some time now. And I don't have GPU processing available on the affected hosts, so presumably freeglut3 is irrelevant.
So... has anyone had similar issues and/or have ideas on how I can go about diagnosing/resolving this, please?
Soli Deo Gloria
Copyright © 2024 Einstein@Home. All rights reserved.
Suspected 32-bit vs 64-bit Issues (Linux)
)
I would start by running ldd on each of the application files that BOINC is attempting to launch. This will tell you if any libraries are missing.
For example:
ldd $BOINCDIR/projects/einstein.phys.uwm.edu/einstein_S6Bucket_1.01_i686-pc-linux-gnu__SSE2
Ah! I forgot about that
)
Ah! I forgot about that trick. Although, in this case, they all seem to be static executables - I keep getting the message 'not a dynamic executable'.
...is that right? I would have thought that they would at least use some generic external libraries.
Oh well, thanks for the tip.
Soli Deo Gloria