A new Linux App is available from our Beta Test page.
This App was built with newer version of the BOINC library that I hope to fix some of the segfault client errors (exit status 11).
In addition it will stop trying to immediately sync the checkpoint file after five successive failures (which should help e.g. on XFS). And in contrast to the 4.14 will still keep the checkpoint if syncing failed.
I intend to make this one the "official" Linux App soon, we should at least get some more information about the computing errors we still get of the 4.02 App.
BM
BM
Copyright © 2024 Einstein@Home. All rights reserved.
GNU/Linux S5R3 App 4.16 available for Beta test
)
All WUs errored out with "process got signal 11", also the new ones downloaded. This time made sure i wasnt trying to use the Windows beta app =) So what am i doing wrong this time... I did stop the client before copying the 4.16 files to the E@H directory, and i did overwrite app_info with the new one.
The host: http://einsteinathome.org/host/1033251/tasks
Boinc client version 5.10.8 on Kubuntu 7.10
Team Philippines
Thank you for the
)
Thank you for the report!
I can see that this is bad for you, but maybe it will help us anyway.
Do you have ddd debugger installed on the machine? If so, you could create a file "EAH_DEBUG_DDD" in the BOINC directory, and the next time a tash is started should fire up ddd attached to it. Hitting the "Cont" button will let the App run under the debugger. It should catch the signal and list where it occurred.
Thanks a lot!
I'll try to reproduce this on the same system.
BM
BM
RE: I'll try to reproduce
)
Yep, seen it:
update_app_progress (cpu_t=1.008062, cp_cpu_t=0) at boinc_api.C:265
Apparently this BOINC library version makes things rather worse than better.
Thanks a lot again for the report!
All others: be careful when using this Beta App. Would be nice to get some reports of systems where it works. I hope to issue a new, fixed version soon.
BM
BM
Ah well, no risk no fun. I'll
)
Ah well, no risk no fun. I'll try this app out on my laptop and see what happens. Don't worry about those computation errors, btw, I completely forgot I still had some WUs in the queue when I did the app change.
Debian 4.0, Boinc client
)
Debian 4.0, Boinc client 5.4.11, same.
http://einsteinathome.org/host/1041649/tasks
Edit: I can try to upgrade this one to boinc 5.10.27 from the Debian unstable release later.
Team Philippines
Upgraded the host to sid
)
Upgraded the host to sid (Debians unstable release), with all the new libraries and boinc 5.10.27-1, no go. Can do more experimenting on this one (its just a VMWare WS guest install) if anyone got ideas.
The 5.10.27 results:
http://einsteinathome.org/task/88426898
http://einsteinathome.org/task/88426895
Team Philippines
Interesting. I'm pretty sure
)
Interesting. I'm pretty sure it hasn't anything to do with the BOINC Core client version. Is this App actually running on any system at all?
BM
BM
Apparently not. I temporarily
)
Apparently not. I temporarily suspended my other two projects to force the laptop to run Einstein and got two (dual core) signal 11 errors almost within the same second. Downloaded another WU, crashed that, too. I don't think this is going to work out. Running Kubuntu 7.10 on a Core Duo laptop, core client 5.10.8. The computation errors are followed by an odd "output file absent" error, which doesn't tell me anything, but I hope it's helpful for you and the other project devs.
EDIT: I removed app_info.xml now, didn't want to waste any more WUs. I think there should be quite a bit of output now, hope it helps.
We got a fix for BOINC from
)
We got a fix for BOINC from David Anderson. I'm currently rebuilding and updting the App. The 4.16 Beta Test package has been removed until it got updated.
BM
BM
Ok, I updated the 4.16 App
)
Ok, I updated the 4.16 App with new BOINC library (as of today).
Please download the new package with the old name and replace the files
(new md5 is 4a13337ab423e80cabacc1e14fdf1866, old was dc0867738e712a71ca1ec458c0eec185).
BM
BM