Just noticed that this host NET2-3200 is crunching wu's in chronological order, whereas the others are just crunching.

I don't think it could be EDF as it's wu's are deadlined 12/07 & 01/08

Using stock 5.10.28

Any ideas as to why?

---

On the 9th I had quite a few that had 8 day 16 hr deadlines, AR=1.488, but would have thought it was too early for EDF mode to kick in yet, if you got some of those.

On the 9th I had quite a few that had 8 day 16 hr deadlines, AR=1.488, but would have thought it was too early for EDF mode to kick in yet, if you got some of those.

Had 18 wu's - 16 with 12/07 & 2 01/08. it has been working down the list in date order. Only 11 left - 9 31/12/07 & 2 02/01/08.

At the same time, it is not d/l'ing any more wu's, whereas my other hosts are.

Have not changed any setting on host or added anyting to it. Weird!!!

---

On the 9th I had quite a few that had 8 day 16 hr deadlines, AR=1.488, but would have thought it was too early for EDF mode to kick in yet, if you got some of those.

Had 18 wu's - 16 with 12/07 & 2 01/08. it has been working down the list in date order. Only 11 left - 9 31/12/07 & 2 02/01/08.

At the same time, it is not d/ling any more wu's, whereas my other hosts are.

Have not changed any setting on host or added anything to it. Weird!!!

Different rates of crunching for different setups maybe?

Otherwise Yer runnin out of chronoton particles. :D ;)

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Different rates of crunching for different setups maybe?

Otherwise Yer runnin out of chronoton particles. :D ;)

Haven't changed the setup but they are running in high priority. Have 39 days before the deadlines, so can't understand why!

Re-checked system & there have been no changes, as I've said, weird!!!

10 left with one near completion & still no d/l's

Different rates of crunching for different setups maybe?

Otherwise Yer runnin out of chronoton particles. :D ;)

Haven't changed the setup but they are running in high priority. Have 39 days before the deadlines, so can't understand why!

Re-checked system & there have been no changes, as I've said, weird!!!

10 left with one near completion & still no d/l's

Check your RDCF?

Different rates of crunching for different setups maybe?

Otherwise Yer runnin out of chronoton particles. :D ;)

Haven't changed the setup but they are running in high priority. Have 39 days before the deadlines, so can't understand why!

Re-checked system & there have been no changes, as I've said, weird!!!

10 left with one near completion & still no d/l's

Check your RDCF?

Thanks Richard - What is RDCF & How do I check it?

---

Different rates of crunching for different setups maybe?

Otherwise Yer runnin out of chronoton particles. :D ;)

Haven't changed the setup but they are running in high priority. Have 39 days before the deadlines, so can't understand why!

Re-checked system & there have been no changes, as I've said, weird!!!

10 left with one near completion & still no d/l's

Check your RDCF?

Thanks Richard - What is RDCF & How do I check it?

"Result Duration Correction Factor".

What is it? Not all computers are created equal. (surprise, surprise). BOINC doesn't bother to calculate your computer's speed exactly - it takes a rough guess, and then refines it from experience as it goes along. Sometimes glitches like interrupted benchmark runs cause the estimates to get way out of line, with effects similar to what you're describing.

Where is it? In your 'client_state.xml' file. NOT a good idea to go fossicking about in there, especially at this time of a Sunday night. Instead, go to your computer details page on this website, and scroll right down to the very bottom - the line above 'Location'. I'ts one of the private figure only the owner of the computer can see.

What should it be? Nominally, 1.000000
In practice, somewhat lower for stock applications, much lower for optimised applications - one of mine I've checked is showing 0.166741
If it's more than one - especially if it's up in the tens or hundreds - you've found your problem.

What do I do about it? NOTHING. It'll correct itself in due course. Have a good night's sleep. Then, if you still want to fix it in the morning:
1) Shut down BOINC fully
2) Backup client_state.xml
3) Open client_state.xml in Notepad
4) Find the line, in the SETI@home project section, which reads

    <duration_correction_factor>X.xxxxxx</duration_correction_factor>

and reset the numbers to something reasonable - 1.000000 is reasonable.
5) Save your changes to the file - making sure that you've changed nothing else.
6) Restart BOINC

Oh, and before you start:

0) Search these message boards and the Wiki for RDCF, and check that I've got it right.

might also go to "your account", "view computers", then select the host and look at the following:

% of time BOINC client is running 99.9516 %
While BOINC running, % of time work is allowed 99.993 %
Average CPU efficiency 0.994539
Result duration correction factor 0.166006

'
These are mine for one host.

Different rates of crunching for different setups maybe?

Otherwise Yer runnin out of chronoton particles. :D ;)

Haven't changed the setup but they are running in high priority. Have 39 days before the deadlines, so can't understand why!

Re-checked system & there have been no changes, as I've said, weird!!!

10 left with one near completion & still no d/l's

Check your RDCF?

Thanks Richard - What is RDCF & How do I check it?

Result Duration Correction Factor - it's a 'fudge factor' used to adjust estimates of how long it will take your system to crunch a given WU. You can find it by clicking on the link you supplied in your first post and scrolling to the bottom. it appears just above the 'Location' entry.

(Note: the layout of what you see when clicking that link vs what I can see are quite different...as the owner of the system, you see much more than I do...e.g. I can't see your location value, RDCF, etc. but I can on mine because I own it).

Excellent - Thanks for the info guys.

It's running on the following: -

86.6573%
99.982%
0.319761

Checked my other hosts, & it looks like it's pretty normal to me.

As it's not d/l any wu's & rather than mess anything up,will set it on NNT & delete it when finished with wu's & then re-install to see if that clears the problem.

Regards

PJ

---

At the same time, it is not d/l'ing any more wu's, whereas my other hosts are.

Since upgrading to newer BOINC versions (5.10.28 currently, but saw this before that), I've been seeing incidences in which it stops requesting work on one project on one machine, working the queue down to very near zero before requesting work.

I've mentioned a couple of instances here, and John McLeod has responded with a list of reasons for stopping fetch. However in the cases in point, none of the reasons he supplied were at hand.

Whether this is some sort of bug dependence on some internal state not obviously dependent on actual circumstances, or is just yet another intentional circumstance which applies to me but not mentioned by John, I don't know.

One quite recent example:
Q6600 Windows XP boinc 5.10.28
4 % SETI share, 96 % Einstein share
Short term and long term debt between projects in balance to less than 10
Normal alternation between 4 Einstein instances and 3 Einstein plus one SETI continued unaltered (i.e. mine did not look like EDF)
"Computer is connected to the Internet about every " 0.002 days
"Maintain enough work for an additional" 7.26 days
SETI Result Duration Correction Factor in this period .14 to .17

While Einstein work request continued, typically getting one result at time at intervals of about one to three hours, SETI work request just stopped. The amount of SETI work in queue, as estimated by BOINCView, declined from its usual about 150 hours (as prorated for resource share and such) to about 10 hours (near zero, really, given the resource share pro-rating) before a work request was finally generated.

I did not observe an abnormality of work order choice in these instances, but I was not looking for it.

This is not a match to the situation Sirius_B reports here, but is one in the category of work fetch oddities.

On the topic of "why would anyone care?", in this particular case it defeated my attempt to maintain a diverse stock of unprocessed work units of varied angle ranges and observation dates in order to provide a quick assessment of the correctness and relative speed of a hoped-for new SETI science ap optimized code release. By the time fetch resumed, all of the stock I had husbanded for weeks was gone.

On the other hand, fetch did indeed resume, without any violent actions on my part, and absent some special interests such as the assessment I mentioned above, there was not much of a problem here. I'm just adding to the observation pool.

---

This one is really weird though. Resources are 100% Seti, no changes made & all wu's are running in high priority.

They are running in total chronological order - time & date.

Other hosts have between 20 & 40 wu's - this has 5 left with 1 half completed.

No wu's are being d'l'ed at all which is very unusual for this host (Wife's) nothing has been changed or added to system.

Prefs (Local or Web) have not been altered in any way. This was noticed shortly after last Friday's outage, whether that had anything to do with the problem, I don't know.

After all wu's have been completed & reported in, will a clean re-installation of Boinc work?

---

After all wu's have been completed & reported in, will a clean re-installation of Boinc work?

Agree yours is both weird and different than my three or four incidents.

My bet is that sometime between now and zero work, it will suddenly resume downloading and return to normal, with no message to hint at why it paused.

If not, you might try "reset project" before a full re-install. If the bad piece of state is associated with the project, which seems somewhat likely, that might delete it.

I am just guessing.

---

This one is really weird though. Resources are 100% Seti, no changes made & all wu's are running in high priority.

They are running in total chronological order - time & date.

Other hosts have between 20 & 40 wu's - this has 5 left with 1 half completed.

No wu's are being d'l'ed at all which is very unusual for this host (Wife's) nothing has been changed or added to system.

Prefs (Local or Web) have not been altered in any way. This was noticed shortly after last Friday's outage, whether that had anything to do with the problem, I don't know.

After all wu's have been completed & reported in, will a clean re-installation of Boinc work?

I've noticed that when I change the 'Computer is connected to the Internet about every xxx days' in the 'General Preferences' to a several days or more, it stops crunching in the order received to date/time order. Guessing that BOINC wants to be sure that the ones with the soonest expiration dates get crunched and reported on time since the computer only connects once every xxx days.

Whey I go back to zero days, it switches back to date received crunching order.

---

After all wu's have been completed & reported in, will a clean re-installation of Boinc work?

Agree yours is both weird and different than my three or four incidents.

My bet is that sometime between now and zero work, it will suddenly resume downloading and return to normal, with no message to hint at why it paused.

If not, you might try "reset project" before a full re-install. If the bad piece of state is associated with the project, which seems somewhat likely, that might delete it.

I am just guessing.

Thanks, didn't think of that.

WU's will be completed by 21:00 tomorrow approx. Will try reset after all reported in.

Excellent - Thanks for the info guys.

It's running on the following: -

86.6573%
99.982%
0.319761

Checked my other hosts, & it looks like it's pretty normal to me.

As it's not d/l any wu's & rather than mess anything up,will set it on NNT & delete it when finished with wu's & then re-install to see if that clears the problem.

Regards

PJ

there are 4 reading in the prefs, but you only showed 3(and no indication of what those are), Is the other one low?

Is the system clock correct?

What version of BOINC?

Are prefs override set in Advanced Settings?

% of time BOINC client is running?

While BOINC running, % of time work is allowed?

Average CPU efficiency?

Result duration correction factor?

Other projects?

Excellent - Thanks for the info guys.

It's running on the following: -

86.6573% 1
99.982% 2
0.319761 4

Checked my other hosts, & it looks like it's pretty normal to me.

As it's not d/l any wu's & rather than mess anything up,will set it on NNT & delete it when finished with wu's & then re-install to see if that clears the problem.

Regards

PJ

there are 4 reading in the prefs, but you only showed 3(and no indication of what those are), Is the other one low?

Sorry Astro, I left out no 3 average CPU Efficiency which is 0.987436

Is the system clock correct? Yes

What version of BOINC? 5.10.28

Are prefs override set in Advanced Settings? No

% of time BOINC client is running? 1

While BOINC running, % of time work is allowed? 2

Average CPU efficiency? 3

Result duration correction factor? 4

Other projects?

No