I think it may also have something to do with how much work each machine has to download. My one rig has to download well over 2000 wu's to sustain it for 3 days. I often have to battle maxed out bandwidth, and continously babysit my rig to get enough work, which really doesn't happen until the limits are taken off. If I needed much fewer wu's, then it would fill up much faster, hence less chance of ghosts. Just my thoughts, and I could be completely wrong. :)

Steve

I don't think so Steve. My little box doesn't take much to fill it. About 120 or so lasts me through the outages usually but I've had to clear 100s of ghosts since we've started these long outages.

---

PROUD MEMBER OF Team Starfire World BOINC

A hint for the developers:
I have 7 Linux boxes running Seti.
Until now I had not one ghost attached to them.
For me it looks like a "Windows only" problem.

LOL, I think it is a server-side issue almost exclusively, which would make it "Linux only". In reality, it is of course just a weakness of the BOINC system and some programming effort is needed to make it more robust.

                                                                 Joe

It was not meant as a statement pro/contra Windows. Sorry if you misunderstood
that. But there must be a reason that only the Windows clients have
that problem.

19 minutes until about 10 tasks are past the deadline... come up uploads!!

Seems uploads were going by this time last week....

Also normally they have built up the cache for results ready to send, now there's now none, wonder if there's some problem going on.

At least someone is there...All on except upload/download...

---

Official Abuser of Boinc Buttons...
And no good credit hound!

The Gates are open. :-)

Uploading starts here.

Helli

---

A loooong time ago: First Credits after SETI@home Restart

The Gates are open. :-)

Uploading starts here.

Helli

Ok, I'm all uploaded, they can start the reporting and downloading now! :-)

---

PROUD MEMBER OF Team Starfire World BOINC

mostly uploaded.. still can not report.

8/6/2010 8:53:17 AM SETI@home Reporting 67 completed tasks, requesting new tasks for CPU
8/6/2010 8:53:19 AM Project communication failed: attempting access to reference site
8/6/2010 8:53:19 AM SETI@home Scheduler request failed: Couldn't connect to server
8/6/2010 8:53:20 AM Internet access OK - project servers may be temporarily down.

---

Janice

A hint for the developers:
I have 7 Linux boxes running Seti.
Until now I had not one ghost attached to them.
For me it looks like a "Windows only" problem.

I think it may also have something to do with how much work each machine has to download. My one rig has to download well over 2000 wu's to sustain it for 3 days. I often have to battle maxed out bandwidth, and continously babysit my rig to get enough work, which really doesn't happen until the limits are taken off. If I needed much fewer wu's, then it would fill up much faster, hence less chance of ghosts. Just my thoughts, and I could be completely wrong. :)

Steve

I have enough for maybe another 4.5 days and that's just for the fab four gpus. :D

---

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

Uploaded, and ready to report...LOL

8/6/2010 9:28:37 AM | SETI@home | Reporting 1514 completed tasks, requesting new tasks for CPU

---

Official Abuser of Boinc Buttons...
And no good credit hound!

My BOINC ULed 633 results.
Can't report.
Today my BOINC got a -12 error of the CUDA app. Damaged WU quota if my BOINC can/will report.

---

1189 to upload still, But I'm not downloading for a few days.

---

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

Looks like we are up and running....

8/6/2010 9:48:51 AM | SETI@home | Reporting 1519 completed tasks, requesting new tasks for CPU

8/6/2010 9:51:09 AM | SETI@home | Scheduler request completed: got 0 new tasks

8/6/2010 9:51:09 AM | SETI@home | Message from project server: Project has no tasks available

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I am getting this message again on my P4 which is not running Seti;
06/08/2010 19:12:42 SETI@home update requested by user
06/08/2010 19:12:47 SETI@home Sending scheduler request: Requested by user.
06/08/2010 19:12:47 SETI@home Not reporting or requesting tasks
06/08/2010 19:13:09 Project communication failed: attempting access to reference site
06/08/2010 19:13:09 SETI@home Scheduler request failed: Couldn't connect to server
06/08/2010 19:13:11 Internet access OK - project servers may be temporarily down.
IS it because of the numbers or is there still a problem with the scheduler?

---

19 minutes until about 10 tasks are past the deadline... come up uploads!!

Seems uploads were going by this time last week....

SS, different week.......different s.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I am getting this message again on my P4 which is not running Seti;
(...)
IS it because of the numbers or is there still a problem with the scheduler?

My BOINC get also this messages.
But also messages with well contact.

I guess it's the normal up/down after an outage.
Cricket graph is also maxed out.

---

From Jeff, this weeks limits.

We're on line with the same starting limits as last week:

40/CPU
320/GPU

and with the planned Monday limits also the same as last week:

320/CPU
2560/GPU

Astropulse is back on line and that should ease the raw data consumption rate. Without AP running SAH tears through the data such that keeping the splitters fed over the weekend becomes a challenge.

Will be interesting to see how it goes with those Monday limits, i almost ran out of work over this outage, and several others mentioned they did. That may have been due to the server crash just before the outage, only time will tell. I'm thinking another 40 per CPU (and equivalent number per GPU) would be better, but we'll just have to wait & see.

---

Grant
Darwin NT

got troubles with the cpu, not getting much of those, some pc's only have some gpu but no cpu


6-8-2010 23:33:05 SETI@home update requested by user
6-8-2010 23:33:06 SETI@home Sending scheduler request: Requested by user.
6-8-2010 23:33:06 SETI@home Not reporting or requesting tasks

---

Joined Seti@home on 20 June 1999 (id:797875)
Made This1 to Join the Eve Team

http://www.eveonline.com/seti/

6-8-2010 23:33:05 SETI@home update requested by user
6-8-2010 23:33:06 SETI@home Sending scheduler request: Requested by user.
6-8-2010 23:33:06 SETI@home Not reporting or requesting tasks

It's not a server issue- for whatever reason, your system isn't requesting any work.

---

Grant
Darwin NT

6-8-2010 23:33:05 SETI@home update requested by user
6-8-2010 23:33:06 SETI@home Sending scheduler request: Requested by user.
6-8-2010 23:33:06 SETI@home Not reporting or requesting tasks

It's not a server issue- for whatever reason, your system isn't requesting any work.

There is one way it might possibly be a server problem. The preference setting to not use the CPU is sent to the core client and it stops asking for CPU work. Because there have been rare past incidents where preferences changed spontaneously it is at least worth checking.

                                                               Joe

Might be the right place to just mention that it appears the server-side DCF for AP and anonymous platform may finally be in place. Last week when I had WUs, they were estimated at ~26 hours (almost accurate). Starting to get some now and they are estimating 3 hours.

I know it'll work itself out eventually, but those like me who are AP-only, keep an eye on work-fetch successes..don't want to get too many and start having deadline concerns.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)