Ok you 'orrible lot, there I was going to run out of tasks during the maintenance, so I switched off and went to beddie-byes to get some much needed beauty sleep, and when I wake up and boot up the old computer I find some miserable fiend(s) have stolen all de tasks, including all those AP ones.

So own up who dun it.

Ok you 'orrible lot, there I was going to run out of tasks during the maintenance, so I switched off and went to beddie-byes to get some much needed beauty sleep, and when I wake up and boot up the old computer I find some miserable fiend(s) have stolen all de tasks, including all those AP ones.

So own up who dun it.

don't feel so bad...i was awake and querying the server every 6 minutes for the past several hours and i didn't get any either lol...

---

Where do you put the <flops> entry in the App_info?

See Geek@Play's How to add flops value thread.

                                                                Joe

Maintenance is sometimes a cause and not a solution so it seems....

Something seems borked in Setiland. The database queries are way up there, the assimilators are badly constipated, and the result creation rate is way down. I've tried to hold back, but I'm going to have to do some rescheduling before my CPU freezes. ;-)

---

Aaaaaaand the servers bit the dust again... :(

---

Aaaaaaand the servers bit the dust again... :(

I was just gonna say that!

Well....
The whole thing's crashed now.
Can't connect to the server for either uploads or reporting/work requests.
Cricket is bottomed out.

Hopefully somebody's up late resetting things, otherwise we are dead in the water until tomorrow morning.

---

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

Status page is still updating, but doesn't show anything wrong. Hopefully it is just some backend work from an insomniac ;)

---

Servers look okay, cricket showing 600 bits/sec (note.. not kilo or mega as a prefix) indicates a failed link. Either a network cable got unplugged, or a router bit the dust. Or some device/interface forgot what its IP settings were.

---

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

Servers look okay, cricket showing 600 bits/sec (note.. not kilo or mega as a prefix) indicates a failed link. Either a network cable got unplugged, or a router bit the dust. Or some device/interface forgot what its IP settings were.

Those pesky cleaning folks must've plugged their vac into the wrong socket again.......

---

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

Interesting - I looked an hour ago and there were virtually no WU available to download and the crickets were going wild, but there are a few thousand WU available and the crickets are "flat lining". As others have said - something is eating the dust on the floor. Whatever it is it may self recover in a short time, but my guess is we'll have to wait for the tyre kicker in chief to get into the lab in about 12 hours time.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Looks like someones playing, it started working for a while and now its stopped again.

---

Kevin

Aaaaaaand, we're back! Well, at least uploads and reporting are working. However I got a "limit on tasks in process" when requesting GPU work. I have none on board...

---

It's better than before. I can now upload. The couple of downloads i had waiting have finally donwloaded. And i can now contact the Scheduler. Now all i need to do is time it right so i can get some work allocated.
And hit retry a few thousand times to get them to download.

---

Grant
Darwin NT

Well, I managed to get a couple of WUs last time round - both newly split work, so the splitters are working, but both shorties. We could really do with those mid-AR WUs that Joe was forecasting from the September observations to give everyone, and everything, a chance to catch their breath.

Aaaaaaand, we're back! Well, at least uploads and reporting are working. However I got a "limit on tasks in process" when requesting GPU work. I have none on board...

I'm so happy I could just...

Like you (out of GPU WUs); I've got two GTX 460s and a GTX 560Ti that are at room temperature, leaving some old and/or less capable CPUs crunching along slowly.

The good news? The P4 with the GT 240 still has some GPU work left.

The bad news? The only one of my computers with some CUDA work left is the slowest one.

Speaking of how SLOWLY we are alien-hunting, and the large amount of time between the "find" and the "confirmation," I suppose the odds are that by the time we find-out that someone's computer found an alien, the computer that found it will be in a scrap heap somewhere and there will be nothing to send to the Smithsonian.

I guess the owner of that computer will have to agree to be taxidermied (or disinterred) and sent to the Smithsonian.

The plaque will have to read something like:

"The bones of the person who owned the computer we can't find that found an alien signal in 2001 which was confirmed in 2037."

Isn't that a strange thought... you could have found "the signal" and been buried and forgotten by the time anyone discovers that you helped find it. If that happens to me I hope someone has the good taste to change my epitaph from "Dead" to "Dead. Helped discover the first E.T. signal from outer space and never even knew it."

Even stranger - we could be extinct and the nitpicker could discover a signal and post it online all by itself.

Not sure how long things will keep going for- the MB assimilator backlog just continues to grow.

---

Grant
Darwin NT

Aaaaaaand, we're back! Well, at least uploads and reporting are working. However I got a "limit on tasks in process" when requesting GPU work. I have none on board...

Hmm.. maybe there is something wrong with the S@h server settings?

I get always this message, BOINC have ~ 1,600 GPU WUs, but nearly all shorties, BoincTasks say this could be enough for the next ~ 3 days (yes, with <flops> ;-) ..

A pity, that we don't get an update in the TechNews area about the set limits.

-----------------------------------------------

Just noticed..
At some threads the first message isn't displayed.
For example at this thread, also the sticky HE connection problem thread.

Mistake during update of the forum software?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

Just noticed..
At some threads the first message isn't displayed.
For example at this thread, also the sticky HE connection problem thread.

Mistake during update of the forum software?

No. That's what happens when users post in the wrong message boards - like posting general questions in News message boards, or technical queries in the Cafe.

Our long-suffering Mods try to find a suitable home for these lost posts. If they move a post into a thread which was created after the mis-placed post, then it becomes the new 'first post'. But in both the threads you mention, the original first post is still visible - no forum glitch at all.

Update on the Limit message I received earlier. I have not since seen the message, and have downloaded a handful of WU's. All crunched and returned by now though :(

---