i've been having problems all day today downloading new work units for my crunchers.

the message i'm seeing is:

Not sending work - last RPC too recent xxx sec

(xxx can range from 90 to 900)

i just did a rosetta install onto a new machine and i'm getting this same message. right now it's crunching on the single WU it downloaded as part of the initial install, but i'm not able to download anything more.

what in blazes is going on?! please tell me this is a server problem and that it's not a client issue.

i've already checked my preferences,etc and everything is OK. i did not have any problems d/l'ing WU's or doing new installs yesterday.

I set the min_sendwork_interval to 10 minutes. See this page for more information about this config setting.

PJ; seems to have resolved itself now, my new install has added the correct number of WUs. (After a 20 min pause).

---

David,

can i override this setting by creating my own config.xml file? there is a myriad of settings like db_name, db_host, etc...do i need to define these?

a sample file would really help...

also, was min_sendwork_interval changed in the last 24 hrs on the back-end (server-side)?

ps. [Tank] 2 thumbs up on your animated sig. cute. :-)


ackkk....it's late. need to catch some shut-eye!

---

- team XPC - 'Where merry times and good crunching meet head-on!'

No, it is our boinc server configuration file, and yes, I changed the value yesterday to reduce the amount of work units sent to a host that may be getting too many. Are you not getting enough work units to keep crunching?

PJ; seems to have resolved itself now, my new install has added the correct number of WUs. (After a 20 min pause).

I just wanted to say, your sig is brilliant.

---

Team CFVault.com
http://www.cfvault.com

No, it is our boinc server configuration file, and yes, I changed the value yesterday to reduce the amount of work units sent to a host that may be getting too many. Are you not getting enough work units to keep crunching?

actually on that new install, when i checked it this morning it was out of work (completed 6 WU's). some of my crunchers do not have 24 hr internet connectivity. (this is because of self-imposed security concerns with the nature of the work that these machines perform)

just my opinion but unless you have a very real issue with downloading abuse (or are bound by server/connectivity issues), i question why min_sendwork_interval has to be increased at all, particularly now when a host of potential members may be evaluating this project for the first time. i can see where a new user might find it disconcerting to see numerous "Not sending work" entries in their message log; it's not an ideal way to put your best foot forward for this project, imo.

if you allow your particpants to define their own preferences for connect frequency, then at some point you need to trust in their being responsible enough to manage this for themselves. of course, a newbie cruncher might innocently set this value out of ignorance to an excessive value. in which case, user education (through the form of public reminders on the home page) is probably a good start.

in short, empower your users rather than arbitrarily defining limits. it sounds radical but it actually works, sometimes. :)

---

- team XPC - 'Where merry times and good crunching meet head-on!'

I changed it down to 2 minutes instead of 10.

I changed it down to 2 minutes instead of 10.

many thanks, David! much appreciated. :)

---

- team XPC - 'Where merry times and good crunching meet head-on!'