I'm hoping that someone will do the Tuesday maintenance and it will help. I hope the Tuesday maintenance is mainly automated. It started really early the past couple of weeks.

I fear that Jeff has just proved that maintenance isn't completely automated. This just appeared on the front page:

Jeff Cobb wrote:

Because of the Christmas and New Years Day holidays, our weekly outage will be on Wednesday rather than the normal Tuesday both this week and next.

. . Cool! Knowing is enough :)

. . Thanks for the repost ...

Stephen

:)

The validators are validating, the assimilators are assimilating, so the system is looking good until the Wednesday outage. I'm glad they let us know. I hope everyone has a good holiday!!!

. . And a peaceful

M E R R Y
. . . . . . . . . . . C H R I S T M A S

to everyone ...

Stephen

:)

I'm hoping that someone will do the Tuesday maintenance and it will help. I hope the Tuesday maintenance is mainly automated. It started really early the past couple of weeks.

I fear that Jeff has just proved that maintenance isn't completely automated. This just appeared on the front page:

Jeff Cobb wrote:

Because of the Christmas and New Years Day holidays, our weekly outage will be on Wednesday rather than the normal Tuesday both this week and next.

The outage may not be automated, but it would appear the notice is.

---

Grant
Darwin NT

Have not been able to connect with the servers for the last 20 minutes or so.
Anybody else?
Or a problem for the kitties to solve?

Meow?

---

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

. . Did someone let the servers know it is Christmas? They seem to be having a break by themselves.

. . Server with message forums, super slow. Upload/download servers very slow to respond (getting servers may be offline message) and then when a work request does get through ... "No tasks available" ...

. . I am beginning to think these servers have developed their own intelligence and are playing games with us. ...

. . Forgive the whimsy but hey ... what the heck?

Stephen

<shrug>

I'm just acknowledging that there is an issue with the seti machines. It might be a temporary thing as we have noticed this happening for a couple of days now. It might fix itself, or it might not. I do not wish for anyone to be disturbed. Just wanted to mention it.

Merry Christmas!!!

Web site is very slow right now. I'm not getting through now either
Serenity

103509 SETI@home 12/25/2018 1:17:21 PM Scheduler request failed: Timeout was reached
103510 SETI@home 12/25/2018 1:17:21 PM [sched_op] Deferring communication for 00:03:27
103511 SETI@home 12/25/2018 1:17:21 PM [sched_op] Reason: Scheduler request failed

---

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

A proud member of the OFA (Old Farts Association)

. . Did someone let the servers know it is Christmas? They seem to be having a break by themselves.

. . Server with message forums, super slow. Upload/download servers very slow to respond (getting servers may be offline message) and then when a work request does get through ... "No tasks available" ...

. . I am beginning to think these servers have developed their own intelligence and are playing games with us. ...

. . Forgive the whimsy but hey ... what the heck?

Stephen

<shrug>

Thanks for the confirmation.
Hopefully just a chron job that will clear in a bit.

Meow.

---

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

Yep the servers are having indigestion.

---

Tue 25 Dec 2018 04:38:09 PM EST |  | Project communication failed: attempting access to reference site
Tue 25 Dec 2018 04:38:09 PM EST | SETI@home | Scheduler request failed: Timeout was reached
Tue 25 Dec 2018 04:38:12 PM EST |  | Internet access OK - project servers may be temporarily down.

Servers Christmas hangover?

---

Well, the kitties will send the word out.
If Eric or Jeff are about and wish to attend to it, fine.
If it doesn't get fixed before tomorrow's outage, that is just fine too.

Meow.

---

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

Hosts are out of gpu work and not getting any. Time for backup projects.

---

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

A proud member of the OFA (Old Farts Association)

I see the Scheduler is having issues again, either "Couldn't connect to server" or when it does the often seen "Project has no tasks available".
Received-last-hour numbers have fallen off a cliff, and the Database Master-queries-per-second hit zero. They've recovered slightly, but are still well down on their usual 1.5k or so. And quite a few of the Server Status values haven't update for over an hour.

I think the staff should get at least 1 day a year off. We'll just have to wait till after tomorrows official outage, to recover from todays un-official one.

---

Grant
Darwin NT

Seems to me the flow has restarted.

Seems to me the flow has restarted.

+1, slowly but surely recovering. Caches refilled here.
Merry Christmas, all.

---

Seems to me the flow has restarted.

Yep.
The servers live again.

---

Grant
Darwin NT

RTS over 800K. We have seen this before where the splitter cutoff mechanism doesn't trip correctly and the splitters continue to split but the scheduler doesn't recognize requests for work and sends out no tasks available messages. Looks like the scheduler picked up the pieces again and tasks are going out to refill caches.

---

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

A proud member of the OFA (Old Farts Association)

RTS over 800K. We have seen this before where the splitter cutoff mechanism doesn't trip correctly and the splitters continue to split but the scheduler doesn't recognize requests for work and sends out no tasks available messages. Looks like the scheduler picked up the pieces again and tasks are going out to refill caches.

That's the resends sending the RTS up Keith, not the splitters. ;-)

Cheers.

RTS over 800K. We have seen this before where the splitter cutoff mechanism doesn't trip correctly and the splitters continue to split but the scheduler doesn't recognize requests for work and sends out no tasks available messages. Looks like the scheduler picked up the pieces again and tasks are going out to refill caches.

That's the resends sending the RTS up Keith, not the splitters. ;-)

Cheers.

Really? We get 300K resends for every hour??

---

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

A proud member of the OFA (Old Farts Association)

Thanks for the confirmation.
Hopefully just a chron job that will clear in a bit.

Meow.

. . I don't think I have asked this before, but what is a Chron job?

Stephen

? ?