The servers are still in recover after the AP splitting, no doubt it'll be some time before everyone's ghosts are resent,

There is a scheduler Bug fix in the works, hopefully it'll be deployed at Seti Beta on Monday, not expecting it to be a total cure, just a step in the right direction,

Claggy

Yes, it will be some time. I am now under 3000 ghosts on one computer and with the cache limit it will be a long time before they are all sent to me. But at least downloads are working as they should.

Most of the CPU tasks are being set to run at High Priority once they are scheduled to run. It is interesting to note that only 5 of the 8 CPU tasks will be High Priority at a time, they start in normal running mode then become High Priority as a WU gets finished. Just interesting to note.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

There is a scheduler Bug fix in the works, hopefully it'll be deployed at Seti Beta on Monday, not expecting it to be a total cure, just a step in the right direction,

Will that fix the Scheduler timeout problems, or fix the increasing number of Ghosts that are created when the Scheduler keeps timing out?

---

Grant
Darwin NT

What get me here is after fixing the connection issue with a proxy server I am now having to check on this machine every four hours as I only am getting enough work to keep it going for four hours before the LIMITS kick in.

I have been running Ghostdet and two days ago I was getting 54% ghosts tasks
Yesterday was 15%
Today 0% with 200 tasks on board.

They are all mostly shorties though.

Seems to be working itself out.

Now everytime I get a work request in the servers will only do ONE TO ONE
Report one, get one.

I hope this gets solved really fast as my patience is wearing thin as most are

We have built the fastest computer system in the world, lets keep it busy

How does one go about finding a proxy that is safe to use?

Frank

There is a scheduler Bug fix in the works, hopefully it'll be deployed at Seti Beta on Monday, not expecting it to be a total cure, just a step in the right direction,

Will that fix the Scheduler timeout problems, or fix the increasing number of Ghosts that are created when the Scheduler keeps timing out?

It'll fix the Bug of resending work to the wrong device, ie Boinc asks for CPU work only, but gets resends to the GPU instead (which wasn't asking for work), and so timing out any VLARs it encounters.

Claggy

The same happened to me on one computer. After thousands of scheduler timeouts, one request apparently got mangled/misinterpreted enough, server thought I reset the project and decided to abandon all tasks. That's at least what I think what happened...
In any case, you should delete (abort) all those tasks with boinc manager, as they will not get automatically deleted and server will just ignore them (you won't get any credit; they were already marked abandoned for you and re-sent to other crunchers).

Thanks Khangollo, I shall do that.

While i was at work, for some reson my internet connection died.
When i was able to reconnect, and upload all the work that had piled up, naturally the Scheduler timed out on all request for work & reporting.
Even with No New Tasks set it took several attempts to get a response from the Scheduler.
And even now, with only one task to report on one system, and a cou7ple on the other, all that i'm getting are Scheduler timeout errors.

Few more hours & i'll be completely out of work, before the weekly outage where i was expecting to run out of GPU work at least.

---

Grant
Darwin NT

While i was at work, for some reson my internet connection died.
When i was able to reconnect, and upload all the work that had piled up, naturally the Scheduler timed out on all request for work & reporting.
Even with No New Tasks set it took several attempts to get a response from the Scheduler.
And even now, with only one task to report on one system, and a cou7ple on the other, all that i'm getting are Scheduler timeout errors.

Few more hours & i'll be completely out of work, before the weekly outage where i was expecting to run out of GPU work at least.

Also getting timeouts, even on NNT. Dropping my max reported setting. I'll also run out because I've got mostly shorties. Low limits and shorties = cruelty to crunchers!

I crunched 3 tasks this morning with 60 day deadlines - 10 Jan. I don't remember seeing that before.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

I haven't put my hands on my i7 for a few days, but I will have to when i get home from work today. What concerns me, though, is that my account page says it only has 83 in progress, well below its limit of 200. Before all the trouble started, it typically ran in the 1100-1600 range. I know it just downloaded some new units from Einstein, but I don't know what the cause/effect relationship is. Is it getting Einstein because it can't get Seti, or is it feeling debt to Einstein and favoring it for now? My other two machines each reported one unit back to Einstein over the weekend without asking for more, leaving one of them with only Seti work on board. And I just slid back a position in my joining date class. :-(

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Media alert......
The kitties have inbound WUs!!!!

---

"Time is simply the mechanism that keeps everything from happening all at once."

Media alert......
The kitties have inbound WUs!!!!

Purrrrr......

[edit]Purr also for the fact that, according to the weather thing in my signature at the time I posted this, we actually got up to 33F here. Woo hoo.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

You do seem to have a metric buttload of GPU tasks even though your CPU pile finally dropped bellow 100 on two kitties.

I think the all tasks web page still needs a filter for CPU vs GPU tasks, or at least a count.

---

"Life is just nature's way of keeping meat fresh." - The Doctor

You do seem to have a metric buttload of GPU tasks even though your CPU pile finally dropped bellow 100 on two kitties.

I think the all tasks web page still needs a filter for CPU vs GPU tasks, or at least a count.

Well, this does it for me, but for a particular machine with particular software. On a Windows machine you'd need either cygwin or some replacement for wc (word count); ISTR there's a DOS equivalent of grep -- find? Bug: the grep for 'fermi' returns a line not associated with jobs in progress, so the third line overcounts by one.

[eesridr:BOINC] > cat showjobs 
date
grep 'received_time' client_state.xml|wc
grep 'fermi' client_state.xml|wc

[eesridr:BOINC] > . showjobs 
Tue Nov 13 00:06:50 GMT 2012
    687     687   36411
    589     589   23560

---

You do seem to have a metric buttload of GPU tasks even though your CPU pile finally dropped bellow 100 on two kitties.

I think the all tasks web page still needs a filter for CPU vs GPU tasks, or at least a count.

Those were all part of my caches before the problems started.
I had about 75,000 WUs in play before the trashing began.
It's down to 32,000 now.
9 rigs, remember. 20 GPUs.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I was just talking about one of the rigs that recently got CPU units. You still had around 1500 GPU units for the 3 GPUs. @500 seconds per GPU unit that's nearly 3 days worth left. Even if you get down to 100 per GPU that's still a half a day's worth. What did you normally run your queue as? 10 days.

It doesn't make a difference in bandwidth usage in the long run once the whole seti@home ecosystem hits steady state, it'll just mean that when a super cruncher's nVidia card goes off the rails they can only shaft at most 100 wingman per GPU as oppose to thousands. (Please check your, not directed at you msattler just nVidia users in general, results daily to catch when you system starts to produce mostly inconclusive/error/invalid GPU results.)

---

"Life is just nature's way of keeping meat fresh." - The Doctor

I was just talking about one of the rigs that recently got CPU units. You still had around 1500 GPU units for the 3 GPUs. @500 seconds per GPU unit that's nearly 3 days worth left. Even if you get down to 100 per GPU that's still a half a day's worth. What did you normally run your queue as? 10 days.

It doesn't make a difference in bandwidth usage in the long run once the whole seti@home ecosystem hits steady state, it'll just mean that when a super cruncher's nVidia card goes off the rails they can only shaft at most 100 wingman per GPU as oppose to thousands. (Please check your, not directed at you msattler just nVidia users in general, results daily to catch when you system starts to produce mostly inconclusive/error/invalid GPU results.)

Each 690 crunch a WU in less than 7 min runing 3 WU at time on each GPU (it have 2) about 48 per hour or more, so in a big cruncher (3x690) a 100 WU cache is simpy ridiculous, not last for 1 hour. I have 2x690 sleeping on a bed waiting they rissing the limits, with the actual limits is a waste of time/resources put them to work, simply they will not receive the WU they need to work.

---

Yay! Back from normal Tuesday time-out. (btw, people in lab are really morning people...)

Let's see what comes next... Cricket on top now, AP splitting disabled... Let's see and hope for better...

---

"Please keep Your signature under four lines so Internet traffic doesn't go up too much"

- In 1992 when I had my first e-mail address -

UTC
Yay! Back from normal Tuesday time-out. (btw, people in lab are really morning people...)

Let's see what comes next... Cricket on top now, AP splitting disabled... Let's see and hope for better...

Yes, they took it down just before 6am California time. Doesn't look any better to me. Had timeouts on work requests, so I went NNT and some of those timed out, but I finally reported my completions. First work request generated some new ghosts and I haven't got them yet. Down to 1.5 hrs of gpu work.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Yes, they took it down just before 6am California time. Doesn't look any better to me. Had timeouts on work requests, so I went NNT and some of those timed out, but I finally reported my completions. First work request generated some new ghosts and I haven't got them yet. Down to 1.5 hrs of gpu work.

My computers logs says that they too it down before 5:25, at that time came first "project in maintenance" -message. I don't like to wake up that early...

Well, timeouts is normal after maintenance period, IMHO.

Let's wait about 12 hours and hope for better.

Disappointed that Scheduler assigned some more work before I got the ghosts, so I have more ghosts now. Not a lot and the limits will contain it. But that's what got us the limits - scheduler should handle ghosts first, but it just showed me that it is not fixed. I got the first 20 resends and they weren't all shorties, so that's a help.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.