Hello!

I haven't got any work for nearly 2 weeks now. It ran perfectly before...

I've had a look at the board but I couldn't really find someone in the same situation...

For info, I run on GNU/Linux AMD64.

In the milkyway folder of BOINC there is the astronomy 1.24 app. I guess I should update or something?... I tought boinc was supposed to do it automatically, and I can't find a download to do it myself...

Any idea about how I could solve this?

++ - Bornerdogge

Yes you need to update, read some of the other posts for more details. I believe it is the app file that needs deleted.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Hello!

I haven't got any work for nearly 2 weeks now. It ran perfectly before...

I've had a look at the board but I couldn't really find someone in the same situation...

For info, I run on GNU/Linux AMD64.

In the milkyway folder of BOINC there is the astronomy 1.24 app. I guess I should update or something?... I tought boinc was supposed to do it automatically, and I can't find a download to do it myself...

Any idea about how I could solve this?

++ - Bornerdogge

1. Delete the app_info.xml and astronomy_1.2.....exe files in your projects/milkyway.cs.rpi.edu_milkyway directory

2. Detach from milkyway

3. Attach to milkyway (2 & 3 ensure you download the latest milkway apps)

4. solved

---

I you run other applications / projects on the machine one of the other things that *CAN* possibly cause this (in my experience) is that the long term debts get out of whack. BOINC is supposed to maintain the debts correctly but I have seen situations where they don't seem to correct.

Of course when we asked for a tool to fix this ... well, the developers knew that we did not need it. A participant wrote a tool for windows that resets the debts ... but OS-X and Linux ... well ...

There is supposed to be a command line switch you can run with the command line BOINC CMD to reset the debts, but I never got that to work.

The EASIEST way I know to see if THIS is the problem is to edit the client state file. Which of course is risky... screw up this file and the world goes away.

But, if you are up for it, stop BOINC, backup the client state file, open the Client state file in a pure text editor and look for the tag long_term_debt ... change all of the numbers to 0.0 for all the lines (one per project), save the changed file, restart BOINC.

with the debts reset BOINC should D/L at least one task per project that you are attached to (assuming they have work). BTW, I also did not have MW work and I just did this and Bobs your uncle ...

Your mileage may vary, no returns, all sales final ... proceed at your own risk ... :)

---

{Duplicate post oops}

---

He did say he was still on v. 1.24, so that should have nothing to do with ltd's for getting work. Once the new app is downloaded, it will prob run MW for awhile to catch up on MW's debt.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Actually, BOINC shouldn't have accumulated much more LTD for MW than it had when it first ran out of work.

The reason is that it has probably spent most of the time in a deferred state (No Work from Project) for MW and the CC doesn't add debt to a project when it's out of work and comm deferred.

Alinator

I have seti suspended for a couple years now and it will slowly add to its debt over time, it's minute since its share is only 1%.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Agreed, strictly speaking there is a short opportunity for a project which isn't available or sending work to accumulate a small amount of LTD during the interval between when the comm deferral period expires and the next scheduler request goes through or dies.

However, most changes in the LTD for 'inactive' projects come from making manual (or anomalous) adjustments to other projects debt.

IE, manually editing another projects debt (active or inactive), resetting/detaching a project, CC goes insane for some reason (rare, but happens), etc.

No debt is added or subtracted by the CC for projects which are NNT or Comm Deferred when out of work, or when suspended (even if there is work onboard).

I have seven hosts which have suspended projects. When I started my latest long term experiment back on July 1st, I reset the debts for all projects to zero.

As mentioned previously, the only exception is the host which only has ReiselSieve as the suspended project. It was reset to zero on July 1st as well, but was left active as a 'canary' for when they came back. Finally after three months, I suspended it too (to kill the excessive clutter in the logs). It had accumulated 404 seconds (.02%) of new LTD out of a possible 1,987,200 seconds (1/4 share of 92 days) of debt if there were no 'inactive' project gate.

All of the other suspended projects are still showing 0.000000 seconds of LTD in client_state, almost six months later.

Alinator

I've deleted the files, dettached and re-attached, so it downloaded the new optimized app and now it's working: got 2 WUs this afternoon... :)

thanks to you all! ;)