LIGO O1 Open Data v1.01 - beta, Linux: no go
17 Jun 2019 21:17:08 UTC
Topic 219053
(moderation:
This morning, for the first time, GW Open Data injection runs popped up on my Linux host ... and immediately stopped with computation errors. So far I've had 42 of those tasks download and error out, and now the client has backed off downloading any new tasks for a few hours. Is there some way to gracefully get back to running Gamma-ray pulsar binary searches or should I just wait it out and see what new OD injection runs will bring?
Here is the application and error info:
Application: Gravitational Wave Injection run on LIGO O1 Open Data v1.01 (GW-opencl-ati)
x86_64-pc-linux-gnu
task ID: h1_0250.85_O1C02Cl3In1__O1OD1I1_251.00Hz_420_0
Standard Output:
<core_client_version>7.9.3</core_client_version> <![CDATA[ <message> process exited with code 127 (0x7f, -129)</message> <stderr_txt> ../../projects/einstein.phys.uwm.edu/einstein_O1OD1I_1.01_x86_64-pc-linux-gnu__GW-opencl-ati: relocation error: ../../projects/einstein.phys.uwm.edu/einstein_O1OD1I_1.01_x86_64-pc-linux-gnu__GW-opencl-ati: symbol __get_cpu_features version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference </stderr_txt> ]]>
Ideas are not fixed, nor should they be; we live in model-dependent reality.
cecht wrote:Is there some way
)
Deselecting it in the project preferences and abort - report any that's been downloaded?
It doesn't work for me either
)
It doesn't work for me either in Win7.
https://einsteinathome.org/content/next-gravitational-wave-search-gpus-very-soon#comment-171622
The only option to deselect it is from Test Apps as this app isn't listed yet.
mmonnin wrote:The only option
)
The Linux app is now listed (June 17) and both it and the MacOS app are showing as beta test.
The Windows app is also listed but without a 'beta test' label. The status page shows lots of tasks ready to send and lots of validations so are you sure there's still a problem for Windows?
Craig's experience is a bit of a worry though. I decided to google the key bit of his particular error message - ie. "__get_cpu_features version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference" and found this particular hit where the comments seem to paint the picture of why the problem is occurring - a private symbol having "moved from libc6 to ld-linux-x86-64.so.2 where it belongs" (whatever the full implications of that are) :-).
My very simplistic understanding of this is that the app was built against a version of libc6 that contained the "private symbol" (whatever that really is) and now Craig is trying to run it on his system where it's no longer in libc6.
My guess is that Bernd will need to sort this out.
Cheers,
Gary.
You could try to enable "Run
)
You could try to enable
"Run Linux app versions built with LIBC 2.15"
in the preferences.
Gary, These are the actual
)
Gary, These are the actual options in preferences. The injection app is not an option. The last 2 are different apps that are no longer listed on the apps page. The question was how to not receive the tasks.
Binary Radio Pulsar Search (Arecibo) Binary Radio Pulsar Search (Arecibo, GPU) Gamma-ray pulsar binary search #1 Gamma-ray pulsar search #5 Gamma-ray pulsar binary search #1 (GPU) Continuous Gravitational Wave search O2 All-Sky Gravitational Wave All-sky search on LIGO O1 Open Data Gravitational Wave Engineering run on LIGO O1 Open Data
Yep, that was already
)
Yep, that was already enabled. What I did was disable "Run test applications" under the Beta Settings for Project Preferences. That worked to stop those tasks from downloading.
Ideas are not fixed, nor should they be; we live in model-dependent reality.
mmonnin wrote:Gary, These are
)
Yes, my apologies.
I was talking about the applications page, not the preferences pages, and I should have made that clear.
It seems these days that before a new app gets listed in the preferences, they make it available through the applications page list so that anyone helpful enough to have the test applications preference selected will get them automatically. I'll have to make sure to remember to check the preferences list of searches before saying that something is 'listed'. My bad.
The main reason for posting was to provide some information about the error message that cecht saw. I'm glad he took your advice to turn off test apps to stop the carnage :-).
Cheers,
Gary.