Boinc Manager 7.6.7 on Mac OS X 10.9.5

After varying time of operation, the Boinc client stops calculation with error message
"...
<TIMESTAMP> [PROJECT] Can't create task for <TASKNAME>
<TIMESTAMP> [PROJECT] exceeded limit of 200 slot directories
..."
(See
<VOLUME>/Library/Application Support/BOINC Data/stdoutdae.txt)

Actually, the directory
<VOLUME>/Library/Application Support/BOINC Data/slots/
contains 200 directories, with almost all of them being empty; except for a number as configured in the Boinc Manager's Properties.
Before the above error is thrown, the number of slot directories is steadily incremented up to the limit; new WUs downloaded from project servers are placed into the new directories, but slot directories from completed WUs are emptied, but not reused, and thus are piling up until hitting the error threshold.

This behaviour was only observed with Boinc Manager 7.6.7, and not with the 7.4.42 version used previously.

My current workaround is to stop the client, and manually deleting superfluos empty slot directories. Afterwards the WU processing will continue until the next time the error threshold is hit.

Please don't hesitate to contact me should further information be required

Regards

cnamglaejoer

BOINC 7.6.10 is the new recommended version for the Mac, please test with that one if you can reproduce the problem.

---

Hi Jord,

preliminary status:
I've upgraded the box in question to Boinc Manager 7.6.10
I regret to say that the error still persits.
What makes things more complicated is that it appears to be not only a platform specific issue, but a platform/version specific one; on another box running Mac OS X 10.6.8 with Boinc 7.6.10 the slot directories are recycled as expected.

Do you have any idea which analytical data (log or config files) might be useful to isolate the culprit?

For the moment I will downgrade the erroneous box to Boinc 7.4.42; I'll report on the results accordingly.

Dazed and confused

cnamglaejoer

I have forwarded it to the developers. Let's see if they want to answer.

---

Hello Jord,

thanxallot for your quick help;
I've activated the slot_debug logging on both boxes, and switched the Boinc client on the troublesome box back again to v7.6.10.
I'll observe the boxes and will forward the respective stdoutdae logs when I have the impression that enough helpful analytical data are at hand.

Regards

cnamglaejoer

I've activated the slot_debug logging on both boxes

That's the right tag. Once you hit upon the problem again, check if there is extra information about it in stdoutdae.txt / Event Log. And post that here. :)

---

The developer has been busy testing things and found what caused this. He has since fixed the problem. It's in the new recommended 7.6.11 available from the normal download page.

---