A new Linux App is available from our Beta Test page.
This App should fix the bug that caused a SEGV (signal 11) when the BOINC Core Client became unresponsive (e.g. due to network access / problems).
This "standard" (non-SSE) App has the "linear SIN/COS" code working (many thanks to Akos and Bikeman) and should thus be somewhat faster than the 4.20.
We (Einstein@home and BOINC) are migrating to a new way of doing the graphics (actually BOINC has, I'm still working on Apps for Einstein@home). In the present state I couldn't get the "old-style" graphics to work, but I guess not many Linux users will look at it anyway. The next App release should have "APIv6 graphics".
Please test and report!
BM
BM

GNU/Linux S5R3 App 4.24 available for Beta test
)
Sorry, my fault (typical OOC error). The app_info.xml listed a einstein_S5R3_4.24_i686-pc-linux-gnu.so file. I updated the app_info.xml, the archive, the md5sum and the instructions on the webpage.
Thanks for reporting this.
BM
BM
RE: Hi Bernd, not a problem
)
I'm not sure I understand you correctly. It sounds like the App exits and is restarted rather often. Do you get a lot messages like "... exited with zero status but no 'finished' file" of the BOINC Client or see "no heartbeat from core client" in stderr.txt in the slot directory?
BM
BM
BTW: The version of the BOINC
)
BTW: The version of the BOINC library in this App uses the 'old' method for determining the CPU time. This means that even on older kernels the CPU time should be updated correctly.
BM
BM
RE: In fact, the message
)
For whatever reason the Core Client doesn't respomd to the App. Prior this lead to a signal 11, now with the fixed App it's just a restart.
However with the App not being able to run more than 30 seconds you will hardly get any 'work' done at all. By default it checkpoints every minute; and depending on your machine the time for recovering from a checkpoint might well be more than that.
In any case I'd remove the debugger file (the sig11 has been fixed anyway) and try to find out why the Core Client is gets somewhat stuck on your machine. The task you mentioned apparently ran fine for the first 18 minutes - anything changed then you are aware of (started a particular program, updated the system, whatever)?
BM
BM
It looks like newer Core
)
It looks like newer Core Clients become unresponsive when they loose network connection (probably for DNS timeouts), causing a missing 'hearbeat' on the App side. It's good to know that this is not limited to Linux. For the moment I'd suggest to use an older Core Client.
BM
BM
RE: RE: A new Linux App
)
You're absolutely right. I updated the app_info.xml, the package and the md5sum again.
Thanks,
BM
BM
RE: md5sum does not match
)
No clue. The one on the webpage is correct on the server side and when downloading it to my local machine.
Surprises me a bit, but good to know. Just for the records: which Client version are you using? It's just a warning anyway.
Thanks for the report.
BM
BM
RE: The problem is that
)
The logs are plain text files in the BOINC directory (stdoutdae.txt and stderrdae.txt); you don't need to use the manager.
BM
BM
RE: This is the first time
)
That's entirely true.
If everything is running fine now I wouldn't worry. It might be though that the slots/0 directory has a permission problem that could come up again in one of the next tasks.
BM
PS: as for the app_init.xml file - you're right, I should better strip it of all the references to 4.02. Feel free to do so manually until I found the time. I hope to be able to publish a new App soon anyway, as this one didn't show the speedup I expected, but I want to get the "signal 11" issue fixed.
BM
RE: I'm not sure what
)
It does.
BM
BM