..and up.

Still no work being distributed though. Running on reducing cache.

---

Go away, I was asleep

I keep getting one machine running dry, and not being fed. The other is ok albeit gets short at times. Its my dual 5970 machine that is not getting fed quick enough, keeps getting "zero sent" whilst there are WUs available. At literally the same instance in time, my other machine with a 5850 gets WUs.....

I have switched the dual 5970 to Collatz for now until supply is sorted out, as I am having to baby sit it, and its running at half capacity at MW at present

Regards
Zy

I keep getting one machine running dry, and not being fed. The other is ok albeit gets short at times. Its my dual 5970 machine that is not getting fed quick enough, keeps getting "zero sent" whilst there are WUs available. At literally the same instance in time, my other machine with a 5850 gets WUs.....

I have switched the dual 5970 to Collatz for now until supply is sorted out, as I am having to baby sit it, and its running at half capacity at MW at present

Regards
Zy

B A C K U P P R O J E C T !

We are in "code red" at the moment.

---

Greetings from,
TJ

We're working on it.

-Matthew

B A C K U P P R O J E C T !

this has probably been hammered to pulp, but I am not interested in scouring this whopper thread.

I have a feeling backupproject is, in the current ati environement, not as envisioned when collatz thrives on memory clock and mw does not. changes have to be made if interested in keeping the gpus setup optimally for each project and that requires intervention.

I agree, I run three ATI GPU projects, Dnetc and Collatz run at least moderately well together. When I add MW into the mix, the only way MW will process work is when I temporarily suspend the other two projects.

Since MW is, frankly, the LEAST reliable of the three projects at this point, what I do is suspend the other two projects only when I can check back often enough to make sure that MW hasn't gone walkabout (like it has this afternoon), so I can pull either or both Collatz and Dnetc off of suspend mode, at which point they take over GPU processing (even if there is MW work).

B A C K U P P R O J E C T !

this has probably been hammered to pulp, but I am not interested in scouring this whopper thread.

I have a feeling backupproject is, in the current ati environement, not as envisioned when collatz thrives on memory clock and mw does not. changes have to be made if interested in keeping the gpus setup optimally for each project and that requires intervention.

---

We're working on it.

-Matthew

Thanks for info!

---

Though a bit more info might be a good thing (ie outage for hours, days)...

We're working on it.

-Matthew

Thanks for info!

---

I always get the message won´t finnish in time.
Thats just a joke.

My monster does all the units i have in my cache in less a day.
Sadly i have to crunch einstein and collatz.

Boinc 6.10.58

---

Mike

Many of the BM Messages tab messages are there to be ignored if you know your monster is meeting it's project targets.

---

Go away, I was asleep

Mike

Many of the BM Messages tab messages are there to be ignored if you know your monster is meeting it's project targets.

At least i dont get work.

I´m running 6 cores @ 3.8 GHZ atm but nothing to crunch.

---

Validator up to 50K ATM, so trouble is here.

My MW tasks report but are now not getting new work.

I will leave the good cache and revert to Collatz.

---

Go away, I was asleep

Validator choking on returned work.

Is this another Aaaarrrrgggghhhh moment soon?

---

Go away, I was asleep

11/14/2010 6:14:52 AM Milkyway@home Sending scheduler request: To fetch work.
11/14/2010 6:14:52 AM Milkyway@home Requesting new tasks for GPU
11/14/2010 6:14:55 AM Milkyway@home Scheduler request completed: got 0 new tasks
11/14/2010 6:14:55 AM Milkyway@home Message from server: No work sent
11/14/2010 6:14:55 AM Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.
11/14/2010 6:17:02 AM Milkyway@home Sending scheduler request: To fetch work.
11/14/2010 6:17:02 AM Milkyway@home Requesting new tasks for GPU
11/14/2010 6:17:05 AM Milkyway@home Scheduler request completed: got 0 new tasks
11/14/2010 6:17:05 AM Milkyway@home Message from server: No work sent
11/14/2010 6:17:05 AM Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.
11/14/2010 6:19:35 AM Milkyway@home update requested by user
11/14/2010 6:19:37 AM Milkyway@home Sending scheduler request: Requested by user.
11/14/2010 6:19:37 AM Milkyway@home Requesting new tasks for GPU
11/14/2010 6:19:40 AM Milkyway@home Scheduler request completed: got 0 new tasks
11/14/2010 6:19:40 AM Milkyway@home Message from server: No work sent
11/14/2010 6:19:40 AM Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.


server status indicates WUs available, running. I run gpus, not cpu. not getting WUs. I post this because the messages kind of suggest no WUs because I am not running n-body simulation. that has not been a problem until about an hour ago. something change, lately?

The validator is choking again. An hour ago is was about par, 6,500 waiting for validation. Over the last hour its steadily risen, and its now well over 50,000 and still rising. When it gets like that it trys to balance off WU production V Supply V Validation and you end up with bursts of available WUs etc, but its an inexorable move to falling over. See what happens, lately its survived on over 200,000 waiting validation, but at present the runes are not good, and back up projects need checking and winding up. Would be no surprise if it fell over totally within an hour from now.

EDIT:
Hope springs eternal - the GPU WU assimilator just went offline, could be someone is beavering away up there , lets hope so (and plaudits as its Sunday and a day off as such for them)

Regards
Zy

And still rising - now to 72,490

Some admin needs to sort out the servers, they deserve a good kicking.

---

Go away, I was asleep

Not gotten squat the past few days. GPU's sitting there doing nothing.

Supply was fine up to earlier this morning. There must be another reason connected with your setup - what is your cache level, held WUs for different Projects, and BOINC stated run time for each of your GPU Project WUs?

EDIT:
Just had a look at your machines, your 3300 has been performing fine, the others are empty, so there is a difference somewhere in the setups between the main machine and the others which were not getting work. None will right now due to the validator

Regards
Zy