LHC@home

I've two machines, cruching SETI (100), Einstein (100) & LHC (100). Both have huge negative long term debt, but won't download any units, after crunching merrily since Saturday. Is there a download limit on units or is something else going on?

---

There is a download limit but that is to prevent that corrupted hosts download one workunit after the other without producing any relevant results. That limit is also pretty high so that can't be the cause of your problem.

Is there still a lot of work left on those hosts? Because that could be the reason for not downloading work: it might be in EDF-mode to meet the deadlines.

---

BOINC.BE: The team for Belgians and their friends who love the smell of glowing red cpu's in the morning

There is a download limit but that is to prevent that corrupted hosts download one workunit after the other without producing any relevant results. That limit is also pretty high so that can't be the cause of your problem.

Is there still a lot of work left on those hosts? Because that could be the reason for not downloading work: it might be in EDF-mode to meet the deadlines.

This happens to me once in awhile. I am running a 2.26 Pentium 4 with XP. I would turn on my computer more, but the electricity bill would not get paid. LoL


1/17/2006 8:34:09 PM|LHC@home|Message from server: No work sent
1/17/2006 8:34:09 PM|LHC@home|Message from server: (won't finish in time) Computer on 17.8% of time, BOINC on 99.5% of that, this project gets 99.3% of that
1/17/2006 8:34:14 PM|LHC@home|Message from server: Not sending work - last RPC too recent: 5 sec
1/17/2006 8:34:14 PM|LHC@home|No work from project
1/17/2006 8:34:15 PM|LHC@home|Deferring communication with project for 58 seconds

---

Probably the work that you have for SETI and Einstein is more than what BOINC thinks it can do in the time limits. If you have it set to report every 3 days and you have what it thinks is 5 days work it will not fetch work.

You can get around this by suspending SETI and Einstein, than updateing LHC but watch for it going onto EDF.

Did you check and make sure that work fetch was not turned off by mistake in BOINC? That had happened to others on other projects.
Ray

---

Pizza@Home - Rays Place - Rays place Forums

You say you have negative LTD. That could be the issue right there. Negative LTD means that project already got more than it's share of time, and it needs to work some debt off of the other projects first.

Or did you mean LHC has positive LTD, and the other projects are negative?

---

This happens to me once in awhile. I am running a 2.26 Pentium 4 with XP. I would turn on my computer more, but the electricity bill would not get paid. LoL

1/17/2006 8:34:09 PM|LHC@home|Message from server: No work sent
1/17/2006 8:34:09 PM|LHC@home|Message from server: (won't finish in time) Computer on 17.8% of time, BOINC on 99.5% of that, this project gets 99.3% of that
1/17/2006 8:34:14 PM|LHC@home|Message from server: Not sending work - last RPC too recent: 5 sec
1/17/2006 8:34:14 PM|LHC@home|No work from project
1/17/2006 8:34:15 PM|LHC@home|Deferring communication with project for 58 seconds

the recent BOINC Clients (beginning with V4.45 I think) take into account the time your computer is turned on!
In the quote above the computer is turned on 'only' 17% of the time. BOINC client calculates the estimated duration multiplied with 'turn on time'. If this time is beyond the report deadline the computer will not get any more work (-> computer is overcommitted)!

---

Udo

This happens to me once in awhile. I am running a 2.26 Pentium 4 with XP. I would turn on my computer more, but the electricity bill would not get paid. LoL

1/17/2006 8:34:09 PM|LHC@home|Message from server: No work sent
1/17/2006 8:34:09 PM|LHC@home|Message from server: (won't finish in time) Computer on 17.8% of time, BOINC on 99.5% of that, this project gets 99.3% of that
1/17/2006 8:34:14 PM|LHC@home|Message from server: Not sending work - last RPC too recent: 5 sec
1/17/2006 8:34:14 PM|LHC@home|No work from project
1/17/2006 8:34:15 PM|LHC@home|Deferring communication with project for 58 seconds

the recent BOINC Clients (beginning with V4.45 I think) take into account the time your computer is turned on!
In the quote above the computer is turned on 'only' 17% of the time. BOINC client calculates the estimated duration multiplied with 'turn on time'. If this time is beyond the report deadline the computer will not get any more work (-> computer is overcommitted)!

---------------------------------------------------------------------

Interesting. I have never corrupted or failed at a workunit. If you look at my work unit history, you will see that my Requested credit is always less than my granted credit. It is kind of upsetting that BOINC does this.

---

---------------------------------------------------------------------

Interesting. I have never corrupted or failed at a workunit. If you look at my work unit history, you will see that my Requested credit is always less than my granted credit. It is kind of upsetting that BOINC does this.

I think it is a problem with the server today. I am getting that on one system also today, usually get plunty of work. Other system got work earlier, more than it needed, 12 units when it only has a 27% resource share.

They all probably will get it later I guess.
Ray

---

Pizza@Home - Rays Place - Rays place Forums