Welcome to MilkyWay@home

Posts by Darrell Tangman

1) Message boards : Number crunching : Waiting for shared memory (Message 67239)
Posted 10 Mar 2018 by ProfileDarrell Tangman
Post:
In chasing down a problem with running boinc on an Ubuntu Mate 17.10 system I killed and restarted boinc several times. Now BOINC Manager tells me I have eight Milkyway@Home tasks with status "Waiting for shared memory". I am currently splitting my resources between SETI@home and Milkyway@Home. Each time I restarted boinc I got two more partially completed Milkyway@Home tasks waiting for shared memory and two new Milkyway@Home tasks began execution. At the same time SETI@home tasks simply resumed execution when boinc was restarted. (Running boinc 7.8.3 x86_64-pc-linux-gnu, MilkyWay@Home 1.46, and SETI@home v8 8.00.)

Anyone have any thoughts on what might be going on?
2) Questions and Answers : Unix/Linux : Consistent "Validate error" status (Message 66176)
Posted 10 Feb 2017 by ProfileDarrell Tangman
Post:
The update to BOINC client version 7.6.31 successfully corrected my problem; Milkyway@Home work units are now completing correctly and validating.
3) Questions and Answers : Unix/Linux : Consistent "Validate error" status (Message 66157)
Posted 4 Feb 2017 by ProfileDarrell Tangman
Post:
Since updating to BOINC client version 7.6.31 this computer has completed one work unit, which shows a status of "Completed, validation inconclusive", definitely an improvement on "Validate error". Now I have to wait for someone else to complete that work unit, but the "q is 0.0" message has disappeared, which is certainly a hopeful sign.

It took a little hacking to get this done, because I've been running BOINC for quite a while. When I installed Ubuntu 16.04 I just linked to the old BOINC directory, which had been initialized from the BOINC download page, which is still handing out 7.2.42. I start the client manually using scripts written some time in the distant past; this PC is rebooted infrequently enough that it's never been worthwhile to switch over to letting init manage BOINC. The scripts don't work if there's a boinc running as user "boinc", and the obvious way to prevent init from starting boinc (setting ENABLED="0" in /etc/default/boinc-client) didn't prevent init from starting boinc. It remains to be seen if I've fixed that, the next time this PC gets a reboot.

Thank you for your assistance!
4) Questions and Answers : Unix/Linux : Consistent "Validate error" status (Message 66149)
Posted 30 Jan 2017 by ProfileDarrell Tangman
Post:
Since at least January 1, 2017, and for an unknown time prior to that date, all work units from MilkyWay@Home have resulted in a "Validate error" status. Time on this system is split 50:50 between MilkyWay@Home and SETI@home; during the same period SETI@home has yielded no invalid results. Any thoughts on what might be going wrong?

AMD FX-6300 / Linux 4.4.0-59
BOINC 7.2.42
MilkyWay@Home v1.40
5) Questions and Answers : Unix/Linux : Milkyway@Home says it's running a task on 4 CPUs, but it isn't. (Message 63505)
Posted 3 May 2015 by ProfileDarrell Tangman
Post:
Second the previous message; I just aborted an N-Body task that had accumulated 52 hours of CPU time and was still tying up four CPUs to run a single thread.




©2019 Astroinformatics Group