Hi folks,

I just noticed I had an unusually high number of pending tasks.
Looks like something was broken during or immediately after the long outage on August 9.
I have a lot of tasks that still have not been validated even though they were reported by both wingmen around this time:

https://setiathome.berkeley.edu/workunit.php?wuid=2632244434
https://setiathome.berkeley.edu/workunit.php?wuid=2632235792
https://setiathome.berkeley.edu/workunit.php?wuid=2628882004
https://setiathome.berkeley.edu/workunit.php?wuid=2632191521

There are lots more, but I think you get the point ...
Maybe someone needs to run a script to fix this.

Tom

People "bunkering" for the start of the WOW event....

---

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

People "bunkering" for the start of the WOW event....

I think you mean the "end" of the WOW event.

---

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

A proud member of the OFA (Old Farts Association)

Yes, those appear to be WUs that slipped past the validator, even though both hosts have reported. I think that happens after every outage, but sometimes it's more obvious than others.

The validator will take a second pass at those and should validate them just fine, but not until the original report deadline for the tasks are reached. In the case of the first example you posted, which looks like it was a "shortie", that should be 28 Aug 2017, 4:21:33 UTC. However, your second example has an original report deadline of 29 Sep 2017, 22:01:24 UTC, so you'll have to wait quite a while for that one to validate. Nothing you can do about it, but you will eventually get the credit.

No - a lot of people bunkered at the start, just look at the throughput on day on. No doubt there are some that bunker at the end, but that's a much higher risk activity.

---

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

Are we crashing here????
Checked a couple of rigs, and getting 'no tasks available'.
And the stats pages are not responding well at all.
Hope not, being Friday afternoon.

Meow?

---

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

Yeah, it seems problematic at the moment.
Let's hope it recovers, and doesn't crash!!!

Edit: And just after posting that, the cache filled up again.
As usual, as soon as you post about a problem, it goes away :-)

Well, if that's the way to fix things.............LOL.
I also got a couple of batches after posting that.
Something was temporarily veeeeeeeeeeeeeeeery busy.

Meow.

---

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

Are we crashing here????
Checked a couple of rigs, and getting 'no tasks available'.

Usual Scheduler weirdness.
Tbar's Update, Update, Update method got my cache re-filled.

Although it looks like the Master database Queries per second have dropped right off, and the AP graphs appear to be flatlining (very early on so hard to say for sure at this stage) so there could be trouble brewing.


EDIT- passing glitch.
Master Queries per sec did die off for a while there, then it came back with a vengeance & has settled back down to more normal levels.

---

Grant
Darwin NT

No - a lot of people bunkered at the start, just look at the throughput on day on. No doubt there are some that bunker at the end, but that's a much higher risk activity.

. . I really don't understand why they bother in most cases. While it gives them a high spot on the result table at the beginning their lower daily numbers mean throughout the event others just keep passing them and that makes their bunkering look so desperate ...

. . It also distorts the final numbers since most of their "results" are from outside the event period. And it is such a tedious obsessive thing to do .... Hopefully one day the organisers will suggest it is not a good practice.

Stephen

<shrug>

Are we crashing here????
Checked a couple of rigs, and getting 'no tasks available'.
And the stats pages are not responding well at all.
Hope not, being Friday afternoon.

Meow?

. . AAhhh, so the bug has reached the Kittyman ... :(

Stephen

Yeah, it seems problematic at the moment.
Let's hope it recovers, and doesn't crash!!!

Edit: And just after posting that, the cache filled up again.
As usual, as soon as you post about a problem, it goes away :-)

. . Fequently, but sadly not always ....

Stephen

.

Are we crashing here????
Checked a couple of rigs, and getting 'no tasks available'.
And the stats pages are not responding well at all.
Hope not, being Friday afternoon.

Meow?

. . AAhhh, so the bug has reached the Kittyman ... :(

Stephen

Nah. Full up again with no intervention.
Something else was afoot. My pendings also shot up and then dropped back down when the downloads started coming again.

---

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

. . AAhhh, so the bug has reached the Kittyman ... :(
Stephen

Nah. Full up again with no intervention.
Something else was afoot. My pendings also shot up and then dropped back down when the downloads started coming again.

. . Sounds like a temporary traffic jam within SETI HQ.

Stephen

.

Are we crashing here????
Checked a couple of rigs, and getting 'no tasks available'.
And the stats pages are not responding well at all.
Hope not, being Friday afternoon.

Meow?

. . AAhhh, so the bug has reached the Kittyman ... :(

Stephen

Nah. Full up again with no intervention.
Something else was afoot. My pendings also shot up and then dropped back down when the downloads started coming again.

Not sure what happened, but it looks like I missed it somehow.

Project details for: SETI@home including all dates
Total number of work requests: 507
Number of requests gaining work: 159
Number of requests not gaining work: 348
Number of requests not gaining work: 336 (project task limit)
Number of requests not gaining work: 9 (project shut down for maintenance)
Number of requests not gaining work: 1 (request was too recent)
Number of requests not gaining work: 2 (Project has no tasks available)
Number of times no work was requested: 0
Number of tasks gained: 190

Project details for: SETI@home on 25-Aug-2017
Total number of work requests: 134
Number of requests gaining work: 43
Number of requests not gaining work: 91
Number of requests not gaining work: 91 (project task limit)
Number of tasks gained: 44

Project details for: SETI@home on 24-Aug-2017
Total number of work requests: 148
Number of requests gaining work: 46
Number of requests not gaining work: 102
Number of requests not gaining work: 101 (project task limit)
Number of requests not gaining work: 1 (request too recent)
Number of tasks gained: 51

Project details for: SETI@home on 23-Aug-2017
Total number of work requests: 135
Number of requests gaining work: 42
Number of requests not gaining work: 93
Number of requests not gaining work: 91 (project task limit)
Number of requests not gaining work: 2 (Project has no tasks available)
Number of tasks gained: 45

Project details for: SETI@home on 22-Aug-2017
Total number of work requests: 90
Number of requests gaining work: 28
Number of requests not gaining work: 62
Number of requests not gaining work: 53 (project task limit)
Number of requests not gaining work: 9 (project down for maintenance)
Number of tasks gained: 50

No Scheduler Requests found for SETI@home on 21-Aug-2017

No Scheduler Requests found for SETI@home on 20-Aug-2017

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The creation rate of the splitters is very low now.
"Results ready to send" is dropping like a stone.
If nothing changes for the better, we'll be out of work in approx. 5 hours, if "Results received in last hour" stays about the same.

I'll watch it for a bit before I send out a kitty distress call.............

EDIT.....
Creation rate just popped back up.
Think it might be one of those temporary overload thingys.

---

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

The creation rate of the splitters is very low now.
"Results ready to send" is dropping like a stone.
If nothing changes for the better, we'll be out of work in approx. 5 hours, if "Results received in last hour" stays about the same.

I'll watch it for a bit before I send out a kitty distress call.............

EDIT.....
Creation rate just popped back up.
Think it might be one of those temporary overload thingys.

OK, we'll see. I haven't been able to get any new tasks for my main computer for an hour now.

Well, I'm afraid that's the rogue scheduler bug.
I'm within a few tasks of a full tank.

---

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

The creation rate of the splitters is very low now.
"Results ready to send" is dropping like a stone.
If nothing changes for the better, we'll be out of work in approx. 5 hours, if "Results received in last hour" stays about the same.

I'll watch it for a bit before I send out a kitty distress call.............

EDIT.....
Creation rate just popped back up.
Think it might be one of those temporary overload thingys.

OK, we'll see. I haven't been able to get any new tasks for my main computer for an hour now.

Well, I'm afraid that's the rogue scheduler bug.
I'm within a few tasks of a full tank.

Nah, I think it is the "You need to post about it" bug.
My cache just filled up again, to the top :-)
Geeze.....

LOL....seems to be a common fix-it tool around here lately.
Nice when it works.

---

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

The creation rate of the splitters is very low now.
"Results ready to send" is dropping like a stone.
If nothing changes for the better, we'll be out of work in approx. 5 hours, if "Results received in last hour" stays about the same.

I'll watch it for a bit before I send out a kitty distress call.............

EDIT.....
Creation rate just popped back up.
Think it might be one of those temporary overload thingys.

OK, we'll see. I haven't been able to get any new tasks for my main computer for an hour now.

Well, I'm afraid that's the rogue scheduler bug.
I'm within a few tasks of a full tank.

Nah, I think it is the "You need to post about it" bug.
My cache just filled up again, to the top :-)
Geeze.....

LOL....seems to be a common fix-it tool around here lately.
Nice when it works.

Yeah, worked for the second time today.
I think the scheduler is connected to this thread, and reacts to certain words :-)

The scheduler is part of Skynet.....

---

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

Nah, I think it is the "You need to post about it" bug.
My cache just filled up again, to the top :-)
Geeze.....

LOL....seems to be a common fix-it tool around here lately.
Nice when it works.

Yeah, worked for the second time today.
I think the scheduler is connected to this thread, and reacts to certain words :-)

. . It seems to be, now all we have to do is work out what the key words are then the post could be short and effective ... :)

Stephen

:)

Guess it's time to complain of no work available for any machine and hope that the schedulers pick up on the keywords.

---

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

A proud member of the OFA (Old Farts Association)