I have been having a problem with my dedicated crunchers, and I think I have traced the problem back to BAM.

I have two venues set "home" which is the default and set to connect .5 days, and "work" which is set to connect 10 days.

I set my dedicated crunchers (macs running 5.8.0 and 5.8.2) to "work" on BAM. Have the hosts connect to BAM, and connect to SETI. I get the message "new location: work" in the client. Everything looks good. But they never download any more than .5 days.

Quit and restart BOINC, and I get:

General prefs from BAM
Host location: none
General prefs: using your defaults

I double checked location settings on both BAM and SETI. They both say work. Yet when BAM communicates to BOINC, the message is not getting through that the location is really work, so the client reverts to my default location.

To test this, I set up host-specific general preferences on BAM, with a setting of 10 days. Bingo! Success! A butt load of WUs downloaded.

I have the same experience. Only host-specific settings seem to work OK.

This is still not working. And now even setting host-specific settings will not work.

This is part a failure in the BOINC client, and a small bug in a BAM! webpage.

The settings are send correctly to the projects, I confirmed this by changing venues in BAM!, then checking the host on the project website. The venue is set correctly.

After setting the venue in BAM!, after the page reloads, it showed the old venue. This is fixed. It didn't affect the functionality though.

BOINC 5.8.x supports setting the venue directly on the host by using an AMS. I added this to BAM!.

Host Specific Settings are send to the host (you can confirm this by checking file acct_mgr_reply.xml in the BOINC directory).
If they don't work I suspect this is a client bug.

Okay, I will ask over on the mail list. What is an AMS? I looked through the menus on 5.8.8, but couldn't find anything to set the venue. Thanks.

From F.A.Q.:


In your case - BAM!