I have one AP wu on mu old PC, but still nothing on the new one.

I'm stuck between knowing if it's the general problems or the new machine.

Keeps doing the whole;

12/08/2008 05:18:46|SETI@home|Sending scheduler request: To fetch work. Requesting 77474 seconds of work, reporting 0 completed tasks
12/08/2008 05:18:51|SETI@home|Scheduler request succeeded: got 0 new tasks

thing over and over. Rosetta and Spinhenge are ok though.

hey, its 4:30am Wednesday, and im still having trouble getting work down the pipe. Tried KNSW's suggestion, but no luck. howd you other guys get work to come through, or is it mostly just luck of the draw getting to the servers first?

I have one AP wu on mu old PC, but still nothing on the new one.

I'm stuck between knowing if it's the general problems or the new machine.

Keeps doing the whole;

12/08/2008 05:18:46|SETI@home|Sending scheduler request: To fetch work. Requesting 77474 seconds of work, reporting 0 completed tasks
12/08/2008 05:18:51|SETI@home|Scheduler request succeeded: got 0 new tasks

thing over and over. Rosetta and Spinhenge are ok though.

That's what my six machines have been doing since they fixed the upload server. That just means the scheduler did respond, but since the scheduler doesn't have any tasks to give out to anyone, it tells the client there's no new work available. Looking at the server status page, the results waiting to send is a very small number (should be at least 4 figures, at a very minimum).

Keep in mind that WUs only need to be run on 2 or 3 machines to get enough computation to decide what results are good and bad. 30 WUs ready to send are only going to spread out to the first 60-90 clients to connect. Luck of the draw.

AP WUs are nice in a situation like this though. 60-72 hours instead of 1-4 hours for MB. I'm on two dual-core Opterons right now and I've got two AP WUs running at the moment. I'm covered for 3 more days.

---

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

That's what my six machines have been doing since they fixed the upload server. That just means the scheduler did respond, but since the scheduler doesn't have any tasks to give out to anyone, it tells the client there's no new work available. Looking at the server status page, the results waiting to send is a very small number (should be at least 4 figures, at a very minimum).

Keep in mind that WUs only need to be run on 2 or 3 machines to get enough computation to decide what results are good and bad. 30 WUs ready to send are only going to spread out to the first 60-90 clients to connect. Luck of the draw.

AP WUs are nice in a situation like this though. 60-72 hours instead of 1-4 hours for MB. I'm on two dual-core Opterons right now and I've got two AP WUs running at the moment. I'm covered for 3 more days.

I've added Einstein to my machines to keep active through this outage.

Since the server status page has been frozen for over 5 hours, I don't think you can draw an conclusions on what is going on. It's not luck of the draw at present. Looking at the cricket graph, the system has likely not sent out any work to anyone in the last 5 hours.

---

SETI Astropulse WUs are credited very low. In example - I have a few machines with 4-cores CPU each with total average credit 2100 per day, this is 525 credits/day/core. Now I have computed a few AP units, one AP unit takes avg. 45 hours and granted credit is 720. This is only 384 credits/day/core, it means 1536 credits per day/CPU. I loss more than 550 credits per day at each computer. Why? Where is the problem?

---

who is maul (splitter2) and why is always disabvled. i am new to this and having trouble getting work t fulfil processor, woring curently on ein stien,
love cute cat

SETI does not always run the maximum number of splitters because generally they can keep up without running all of them.

... and I don't know, but I suspect at the moment that the splitters are "throttled" by disk space -- that they run fast when there is room, and run a lot slower as the drives get full.

As people report finished work and the work transitions, space will free up.

Not looking that way. Scarecrow's graphs show a dead response for several hours. My machines are getting a few sporatic MB wu's but can't fill the two day cache yet. (So E@H is getting the benefit of my clients.) Things were looking up when SetiCentralCommand had only 1 AP splitter working for a while, but then they turned on 2 (leaving Maul turned off) and the system has choked again.

I don't want any AP wu's for now but have had several assigned but never downloaded to me. I'm sure I'm not the only one. These are the ghost wu's discussed elsewhere, which will sit on the server's disks until hell freezes over, or September, which ever comes first. Since they are AP wu's they are 40x larger than MB wu's, and if a lot of us have them, these ghost help explain the choking of disk space. I fear that unless they are cleaned up, the entire system will constipate and the Seti project stops.

My vote is to PLEASE stop producing AP wu's for a while until the servers can recover or stabilize. That is, turn off the AP_splitters so we can get some work done! Meanwhile, in the background sort out AP's distribution and storage problems now that you have some experience with it. Then only turn on 1 AP splitter.

The following WU's are ghost, they do not show up anywhere in the client:

949023054 313897646 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023053 313897640 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023051 313897634 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023049 313897628 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023046 313897622 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023044 313897616 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023042 313897610 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023040 313897604 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023038 313897598 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023036 313897592 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023034 313897586 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023032 313897580 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949023030 313897574 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949022964 313897510 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949022961 313897498 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949022958 313897492 13 Aug 2008 0:27:24 UTC 20 Aug 2008 0:27:24 UTC In progress --- New --- --- ---
949022957 313897486 13 Aug 2008 0:27:24 UTC 30 Aug 2008 7:45:42 UTC In progress --- New --- --- ---

There was a timeout on a work fetch scheduler request within a few seconds of the time that they were supposed to be sent.

It seems that things got better for a while last night...and both my machines finally got several WU's. I checked again this morning and it's back to not getting new WU's from the SETI servers, so they are waiting idle.

It seems that things got better for a while last night...and both my machines finally got several WU's. I checked again this morning and it's back to not getting new WU's from the SETI servers, so they are waiting idle.

Same here, i only just re-joined the project a few days ago, at first i thought it was my computer that was to blame for not getting any WU`s, having left my computer on over night i discovered that 6 WU`s were downloaded and completed over night, but since then i have received no more WU`s. I was totally unaware of any problems until i checked the message boards.

Tom.

The present outage, is different from the weekend one. During the w/end the test site remained in operation, but today the test site is also down.

Is it possible we have some sort of Einstein@Home 5th columnist lurking behind the servers at Berkeley, screwing seti up, so that we all run more wu's for our fall-over project: E@H?

I know my queues are full with E@H work and the occasional seti. I also noticed a number of seti wu's stuck during download. Probably 5th column guy again!

Yep. Gone dead.
We'll have to wait until the guys get in to give the system a good kicking - some time around now, I guess.

---

Is it possible we have some sort of Einstein@Home 5th columnist lurking behind the servers at Berkeley, screwing seti up, so that we all run more wu's for our fall-over project: E@H?

I know my queues are full with E@H work and the occasional seti. I also noticed a number of seti wu's stuck during download. Probably 5th column guy again!

No, my guess it's those biology types, they think those of us interested in space sciences are all aliens, and they don't want us calling home.

Is it possible we have some sort of Einstein@Home 5th columnist lurking behind the servers at Berkeley, screwing seti up, so that we all run more wu's for our fall-over project: E@H?

I know my queues are full with E@H work and the occasional seti. I also noticed a number of seti wu's stuck during download. Probably 5th column guy again!

No, my guess it's those biology types, they think those of us interested in space sciences are all aliens, and they don't want us calling home.

Or, maybe we should be looking futher outward, perhaps our alien counterparts have seen the mess we made of our world and dont want any contact, i`m sure they could screw up the servers if they so wished,lol.

Tom.

Someone on staff should check the stats .xml export - I think it may be down...
Hard to tell with all the ups/downs, but I haven't had a SETI credit since Sunday. (and I've uploaded about 80 Wu's in that period!)

---

.

Hello, from Albany, CA!...

For those of us HAVING issues CONNECTING , I fail to see HOW this can be done since I am CURRENTLY waiting to connect to report 15 and to upload 33 results. I even tried to join a couple of other PROJECTS to get data to crunch and couldn't even do that...MAYBE it isn't SETI@HOME after all but something else on BERKELEY's END causing the WHOLE ISSUE.

RG---FYI I'm running 2 other projects on my systems and am experiencing no difficulties on either project.

I'm sorry friend, but Berkeley is not the source of any connection difficulties you are experiencing with other projects.

---

I havn't been able to get new workunits for at least 4 days now , Anyone know when sti@home might get fixed ?

I havn't been able to get new workunits for at least 4 days now , Anyone know when sti@home might get fixed ?

I just rec. 20 - 25 WU and I have been empty for 4 days also.

I havn't been able to get new workunits for at least 4 days now , Anyone know when sti@home might get fixed ?

i had 7 WU`s start to download about 2 hrs ago, 4 of which downloaded ok, however the final 3 are still pending, i get a report keep telling me the servers are down again, oh hum!

Tom.

SETI Astropulse WUs are credited very low. In example - I have a few machines with 4-cores CPU each with total average credit 2100 per day, this is 525 credits/day/core. Now I have computed a few AP units, one AP unit takes avg. 45 hours and granted credit is 720. This is only 384 credits/day/core, it means 1536 credits per day/CPU. I loss more than 550 credits per day at each computer. Why? Where is the problem?

I'm sure you crunched many more SETI workunits per day, so it follows that your daily RAC would be higher, whereas AP workunits are hard to complete in a single day so the daily RAC will decline.