There is a scheduled outage for Tuesdays. The start time is variable and the end time is variable. When the outage is done the seti servers get clogged with us all trying to return finished WUs and get new WUs at once. There is never enough WUs in the RTS queue when it does start handing out WUs again, so there are a variety of errors of communication that are "normal" for Tuesdays.

I'm familiar with that, but the second block of messages is from yesterday (Monday) on the other machine that gets work when it needs it. That's why I'm suggesting that is "normal" now for some reason.

edit: I'm concerned by the line mentioning you don't have a usable version of V8

On my main machine, I am set for AP-only, and my app_info only has AP in it. I made a work request, and the scheduler said that no AP was available, but it wanted to send me MBs, but my app_info doesn't have entries for MB, so it can't send me that work.

It does that even though the venue settings are set to NOT send work for other applications. It has done that for something like 3 years now.

---

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

Looks like the MB Validators are falling behind, again.

---

Grant
Darwin NT

And the splitters are still rather lethargic.

---

Grant
Darwin NT

As Grant said, the splitters are not keeping up. RTS is falling at the moment.

edit: to keep up with 140k per hour being returned and needing to be replaced we need to have around 39/sec creation rate. Faster would build the RTS queue back up.

. . Where can I get some hair to tear out when I need it ..........

Stephen

:(

A wig?

---

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

Did anybody notice that the replica database has reappeared after half a year? Wonder what was wrong with it and what was needed to fix it?

---

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

A proud member of the OFA (Old Farts Association)

Did anybody notice that the replica database has reappeared after half a year? Wonder what was wrong with it and what was needed to fix it?

But it's currently 76,944 seconds (over 21 hours) behind the master.

Was it up-to-date last night, and not updated since - or was it even further behind, but catching up? I was in a train during the outage, and didn't notice the exact figures when I got home.

Did anybody notice that the replica database has reappeared after half a year? Wonder what was wrong with it and what was needed to fix it?

But it's currently 76,944 seconds (over 21 hours) behind the master.

Was it up-to-date last night, and not updated since - or was it even further behind, but catching up? I was in a train during the outage, and didn't notice the exact figures when I got home.

Haveland graphs only have it restarting at 1800 UTC Wednesday. So it didn't reappear after yesterday's outage but in fact just today.

---

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

A proud member of the OFA (Old Farts Association)

Did anybody notice that the replica database has reappeared after half a year? Wonder what was wrong with it and what was needed to fix it?

. . The main thing would be that it is actually fixed ...

. . Fingers crossed.

. . I am still on the lookout for 'amigos' to appear :)

Stephen

:)

Splitters and MB Validators are both still rather lethargic; although the Splitters are doing better than the Assimilators. The Assimilator backlog isn't clearing, but at least it isn't growing either.

---

Grant
Darwin NT

Uh oh

---

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

Da, contemplating an email to Eric or not ...
EDIT: SSP Update doesn't show much improvement.
Mail Sent to the Master.

---

Da, contemplating an email to Eric or not ...

. . NO splitters are running. The only new work are resends. I would guess someone is doing something, or they need to know there is a problem. Since it isn't quite 2pm in Berkeley on a Friday, now might be a good time to find out which ...

Stephen

? ?

It's not only resends, I'm also getting new work, just not so often...

It's not only resends, I'm also getting new work, just not so often...

. . According to the stats, the hopper (RTS) was pretty full about 10 to 15 mins ago so some of those tasks must be filtering out to the field.

Stephen

. .

Ever since the last weekly outage the splitters & MB Validators have been rather marginal in their performance. And looking at the Haveland Graphs you can see there have been 2 other instances where the In Progress level has dropped- an indication of work not being sent out. More Scheduler shenanigans.

And the reason the splitters aren't running at the moment is the Ready-to-send buffer is full, and it's not going to get any lower if the Schedulers aren't going to dish out any work- "Project has no tasks available" has ben the response for over an hour now.

---

Grant
Darwin NT

Yes, have run out of gpu work already. Nothing but Project has no tasks available messages.

---

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

A proud member of the OFA (Old Farts Association)

That is not surprising at all. With the replica database being brought back online, it is trying to catch up and creating a lot of extra load.

Things are working as expected in my opinion. It took about 3 attempts I have a full load of work on board 100 tasks. One _2 task which I have pushed to the front of the queue

---

07/12/2018 23:05:39 | SETI@home | Scheduler request completed: got 0 new tasks
07/12/2018 23:15:06 | SETI@home | Scheduler request completed: got 24 new tasks

Don't pay too much attention to transient, ephemeral, artefacts. Give the servers a second chance.