Seti is coming alive again. One of my machines was able to get 113 tasks. Another machine wasn't able to get any. Hopefully the defrag of the dbase will help in the days to come.

. . I have a feeling of deja vu ...

:)

I have a feeling of Deja vu all over again ;/

Tom

---

A proud member of the OFA (Old Farts Association).

We are back! After 13 hours this is going to be a bumpy recovery.

Beyond bumpy.
Ready -to-send buffer emptied before the splitters got going. And that was with all the "Project has no tasks available" messages.

Splitters have finally come to life, but they need to sustain their present output & not give up entirely, or go back to just trickling work out either.
I'm still out of CPU work on 1 system, and things aren't looking too promising for any work in the near future.


Edit- i'm sure there is a script running that scans through the forums for posts on issues, and as soon as you post about the issue it's addressed.
Just like that, within 5 min of posting about it, i managed to get some CPU work.

---

Grant
Darwin NT

I'm not having any luck getting work on my big iron. The little iron got work early in the recovery before the RTS went to zero.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Same. Luckily I still have about 500 WUs but that’s fading quickly from the main machine.

Slow machines that came back early got some tasks but none since. Some others are dry and waiting.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

The good news is that the RTS has managed to build up a small amount (80K- less than an hours worth). Bad news we are splitting the end bits of all the blcs for a while. Results returned in the last hour is 140K, so I'm assuming some noisy WUs but not too bad. Not sure if they will give us more files to split tonight, or wait until tomorrow. I'm curious if we will get data from a new day or more from this same day.

Happy crunching, may your caches stay full :-)

There are a lot of BLC34 tapes mounted ready to split.

---

haha I didn't have to be curious for long. post about something and it will be fixed. :-)

There are a lot of BLC34 tapes mounted ready to split.

. . I expect these to be slower than those we have done so far. Are they from the same day? I'll look ...

. . I just saw that I already have them in my cache. Some are from the same night as those we have been doing and have jumped the queue, others are MUCH older and will be the ones we see most of I expect. At least it seems the blc16 series ran through to completion.

. . Yep checked the status page and there is a full series of blc34 tapes from 58405/58406 matching those we have been crunching. These are the first blc3x series that I can recall, and there may be 4x and above as well. But there are also a dozen orphan tapes from several different days much earlier than the main series.

Stephen

. .

haha I didn't have to be curious for long. post about something and it will be fixed. :-)

. . The SETI ghost strikes again ...

Stephen

:)

01dc06aa

Coming now to your local cruncher.
Interesting ...

---

01dc06aa

Coming now to your local cruncher.
Interesting ...

very interesting...very curious why we are given this now.

I wonder if they are running out of work for us to process . . . . . . so we get retreads.

I think they really need to get humping on the Parkes data acquisition splitting.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

01dc06aa

Coming now to your local cruncher.
Interesting ...

. . and 01dc06ab as well ...

. . like the words of the song ... "let's go back, way back!"

Stephen

? ?

I wonder if they are running out of work for us to process . . . . . . so we get retreads.

I think they really need to get humping on the Parkes data acquisition splitting.

. . Maybe someone at Arecibo just opened a drawer that had not been opened for a long time :)

Stephen

:)

I wonder if they are running out of work for us to process . . . . . . so we get retreads.

I think they really need to get humping on the Parkes data acquisition splitting.

I follow the Greenbank twitter thread. They are recording some data right now. One day of data collection at Greenbank takes us weeks to get through, so while I really really want to see the Parkes data, I don't think we are in danger of running out of data anytime soon. The blc 34 files should keep us busy until next friday (Jan 18) and that is assuming (incorrectly) that they don't have more Aricebo data coming in daily.

I wonder if they are running out of work for us to process . . . . . . so we get retreads.

I think they really need to get humping on the Parkes data acquisition splitting.

I follow the Greenbank twitter thread. They are recording some data right now. One day of data collection at Greenbank takes us weeks to get through, so while I really really want to see the Parkes data, I don't think we are in danger of running out of data anytime soon. The blc 34 files should keep us busy until next friday (Jan 18) and that is assuming (incorrectly) that they don't have more Aricebo data coming in daily.

. . Probably longer as they take 30% to 50 % longer to process on my rigs than the blc16 tasks. They should keep us busy for a while. I am still keen to start crunching Parkes data as well though.

Stephen

:)

Didn't know it could be done:

BOINC is temporarily shut down for maintenance. Please try again later.

Okay, fess up, who dunnit?

---

I'm still wondering who worded it?

Maintenance is a Temporary state, Shutdown can be Permanent.
Which is it?

---

just might have been a momentary glitch. the project is working here for me

---

The BOINC front page is.
The Seti project is.
But the BOINC forums are not: https://boinc.berkeley.edu/forum_index.php

Anyway, sent off an email to David, let's see what he says.
I'm getting withdrawal symptoms.

Wikis are also affected, here's what I get when I search in the User Manual:

This is a cached copy of the requested page, and may not be up to date.
Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Cannot access the database)

Perhaps that database being defragged?

---