. . Now all we need is someone to give the pfb splitter a kick and mount some more tapes in the next 24 hours before the current units are exhausted.

Stephen

:)

They loaded more tapes and the splitters are working hard, but it is hard to come back from the earlier outage.

. . Now all we need is someone to give the pfb splitter a kick and mount some more tapes in the next 24 hours before the current units are exhausted.

Stephen

:)

They loaded more tapes and the splitters are working hard, but it is hard to come back from the earlier outage.

. . Yes, it will take a while for the RTS buffer to recover, things will be hit and miss until then. But I was concerned that with the high rate of noise bombs we saw in the last 24 hours the remaining Blc22 tapes might disappear all too quickly.

. . More tapes mounted is a good thing. But at 41/sec I wouldn't say the splitters were working hard, but they are working. If they were stepped up to max (70 to 90/sec) then the RTS buffer might be showing more recovery ...

Stephen

:)

The assimilators are NOT running. At what point will this be a problem??

Unknown.

It has happened in the past that the assimilators weren't running for a while & everything came to a grinding halt when they ran out of disk space.
But what the current storage levels are, and at what point space becomes an issue & everything grinds to a halt I haven't clue.

I notice too that the Arecibo file27se18ab is still sitting there with 2 channels in progress. I think that's been the case for several days now.
And the purge numbers (both results and WUs) appear to have flat lined.

---

Grant
Darwin NT

I have a feeling that it is also the job of the assimilator to tell the scheduler when a task is old enough to be deleted.

It is understandable that the purge number wouldn't climb without the assimilator running, since it isn't finished with it yet.

EDIT: Duhh, the db_purge script isn't running ...

it looks like the stats are down again. havent seen FreeDC and BoincStats stats for several days. but the numbers listed here on the website seem to be updating.

---

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

Yes. the servers have lots of things messed up now. Expect a long outage tomorrow to hopefully straighten things out properly. We shall see I guess.

---

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

A proud member of the OFA (Old Farts Association)

Yes. the servers have lots of things messed up now. Expect a long outage tomorrow to hopefully straighten things out properly. We shall see I guess.

I certainly agree!! Hopefully they can fix some of the problems that have been happening for a couple of weeks now during Tuesday's outage (outrage?? - probably)

Uploads are getting a bit flaky. Getting a few that are taking a couple of attempts to finally upload.

---

Grant
Darwin NT

Grant was right. I was wrong. I didn't know that over time that the times would change. Thanks for all those who continue to respond to my silly posts and teach me how seti works.

I didn't see a "silly" post. I don't think anyone else did either.

Tom

---

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

It's been over 30m since I have received any tasks.
SSP is frozen in time ...

It's been over 30m since I have received any tasks.
SSP is frozen in time ...

No new WU here too.

---

And we are back...

That was a long outage...

---

nice to be back on our message boards, but I'm guessing it will be a while until things are back to normal.

Any idea what caused this outage? Was it the same issues that were discussed on Sunday?

I have 14 completed tasks that say "uploading" and haven't got anything new all day.

And we are back...

That was a long outage...

My queue of 3600 tasks only lasted 12.5hrs. I was idle for about an hour. Lol. Long indeed.

Still idle since I’ve only recieved 1 new task since coming back up.

---

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

Any idea what caused this outage? Was it the same issues that were discussed on Sunday?

There is planned maintenance every Tuesday. Sometimes it just takes longer than others.

---

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

Reporting doesn't work ATM, my guess the servers are getting hammered.

---

My queue of 3600 tasks only lasted 12.5hrs. I was idle for about an hour. Lol. Long indeed.

That must be American math. How did you do 12.5h of work during 11h of maintenance? :D

My queue of 3600 tasks only lasted 12.5hrs. I was idle for about an hour. Lol. Long indeed.

That must be American math. How did you do 12.5h of work during 11h of maintenance? :D

that was starting from about 9:30am or so, then i left for work. i wasnt able to babysit it to keep the queue filled until the moment the outage started. i had about 2900 CPU tasks stacked up for the outage, and the 700 GPU tasks kept full up. right before i left for work i swapped all the 2900 CPU tasks back to GPU.

---

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