I select a host.

I have a machine attached to a project A (doesn't matter which one). I check the NNW box and the DD box and click Set. The NNW box is still checked, but grayed out. The other two boxes are checked and not grayed out. Perfect.

Now, I go to make any other change to any other other project for that host and click Set.

The settings for project A have changed. NNW is no longer checked. Attach and DD are still checked.

So now my machine is getting new work again, and will never detach, because it never runs out of work.

I can reproduce this at will, 100% of the time.

Fixed this. Seems that when a checkbox is grayed out it's value isn't submitted with the form.

This however only affected older clients where I added the automatic check of NNW because the client didn't do this itself. Newer clients do NNW whenever DD is set.

Thanks!

HM, could it be that something went wrong with the fix ?

I have a couple of projects on one of my boxes; only 1 (SIMAP) has work.

When I attached the box to BAM, all projects had the setting NNW, except of SIMAP (having work)

Later on, I set all projects from this client in BAM to NNW. But SIMAP won't switch.

I have tried a lot of switching, but SIMAP is still refusing to follow a command from BAM. I don't have an idea wheather this is because of BAM or the client. Local on the client I can set NNW and reverse to SIMAP.

I have tried the same with CPDN, this switches as BAM coordinates it.

So, my question(s):

- I'm running client 5.10.20. Is this okay ?

- Is it not possible to set NNW as long as a project has work on the machine ?

- Is it a problem that the project had already been attached on the client when I attached it to BAM ?

Thanks for help, Yeti

[edit]Forgot to say: After changing settings in BAM I forced the client to communicate with BAM[/edit]

Meanwhile I have detached all projects from the client and reattached through BAM.

But still NNW doesn't work on all projects; some projects don't switch, other do.

This is the host: http://boincstats.com/bam/account_host.php?host_id=68423

Projects that don't follow the NNW-switch are: SIMAP, QMC, APS

Yeti

It's not BAM! nor the projects that have to honor the NNW switch, it's the BOINC client. The client controls whether a project will fetch new work or not.

But if I set NNW local on the client it works

and if I do it with BOINCView it works

What can I do to help find the problem ?

Yeti

Post the contents of the file acct_mgr_reply.xml here. Change the NNW settings, then sync the client, then copy the contents.

Changed the project-settings from NNW to opposite, synced:

<?xml version="1.0" encoding="ISO-8859-1" ?>
<acct_mgr_reply>
<name>BOINCstats BAM!</name>
<signing_key>
(REMOVED)
</signing_key>
<repeat_sec>3600</repeat_sec>
<message>BAM Host-ID: 68679</message>
<account>
<url>http://lhcathome.cern.ch/lhcathome/</url>
<url_signature>
(REMOVED)
</url_signature>
<resource_share>1000</resource_share>
</account>
<account>
<url>http://boinc.bio.wzw.tum.de/boincsimap/</url>
<url_signature>
(REMOVED)
</url_signature>
<resource_share>1000</resource_share>
</account>
<account>
<url>http://qah.uni-muenster.de/</url>
<url_signature>
(REMOVED)
</url_signature>
<resource_share>1000</resource_share>
</account>
<account>
<url>http://www.apsathome.org/</url>
<url_signature>
(REMOVED)
</url_signature>
<resource_share>250</resource_share>
</account>
<account>
<url>http://www.cosmologyathome.org/</url>
<url_signature>
(REMOVED)
</url_signature>
<resource_share>1000</resource_share>
</account>
<opaque>
<host_authenticator>(REMOVED)</host_authenticator>
</opaque>
</acct_mgr_reply>

So, for which projects had you set NNW? Because none of the projects have this set in the xml file.

Willy,

I checked a little bit more and found:

1) Immediatly after Updating the NNW-setting at BAM, in the next client connect the <dont_request_more_work>1</dont_request_more_work> switch is send.

2) In the following client-connects this switch is not contained

3) I changed the settings for all projects of the client and the switch was there for all projects in the acc_mgr_reply.

So, it is really the client that is ignoring configurations :-( I will give Rom a hint

Is it by design as you wanted, that this switch is only contained in the first client-connect after any change ? I would expect the switch to be contained in all replies

Yeti

It is by design to send it only once. The client should keep the setting until it is changed again.