https://setiathome.berkeley.edu/workunit.php?wuid=3044805892]blc16_2bit_blc16_guppi_58165_82671_DIAG_PSR_J0613 has been stuck in the my inconclusive list for over a month. The 3rd result was returned on 11 July and is still waiting validation. Just curious as anybody else had the same scenario?

---

Yes, servers occasionally hiccup and don't send out another task for validation. Or I've seen them regularly miss awarding credit and purging the result after two results are returned and validated. Give them another chance when the original deadline date passes and they usually pick up the recalcitrant task.

---

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

A proud member of the OFA (Old Farts Association)

https://setiathome.berkeley.edu/workunit.php?wuid=3044805892 blc16_2bit_blc16_guppi_58165_82671_DIAG_PSR_J0613 has been stuck in the my inconclusive list for over a month. The 3rd result was returned on 11 July and is still waiting validation. Just curious as anybody else had the same scenario?

Report deadline 31 Aug 2018, 23:20:00 UTC, this is when that task should get kicked. This happens more often than most think and usually happens just after an outage. ;-)

Cheers.

I totally agree, Zalster. My 2nd degree humor (and fake jealousy) can't hide the fact that we can only rejoice that so many knowledgeable people and ressources can be mobilized to find that elusive technosignature...

Citizen science, baby ! =:)

And thanks to you guys, I now know (amongst other things) I can set the BIOS to ignore my laptops' batteries the day before they totally go down the drain =:/ =:)

What's wrong with some cosmetic justice giving us slugs the glint of a transient and vain hope to eventually catch up a bit with you power burners ? Huh ?

Smoke if you got them.......

---

Apr 3, 1999 - May 3, 2020

https://setiathome.berkeley.edu/workunit.php?wuid=3044805892]blc16_2bit_blc16_guppi_58165_82671_DIAG_PSR_J0613 has been stuck in the my inconclusive list for over a month. The 3rd result was returned on 11 July and is still waiting validation. Just curious as anybody else had the same scenario?

. . Sadly yes ...

. . Sometimes it is a dud WU, sometimes one or a series of dud wing men. I have had some in that status for nearly 6 months. That is why I wish people leaving the program would flush their caches first, it only takes a few seconds to mark and abort all uncompleted WUs.

Stephen

:(

https://setiathome.berkeley.edu/workunit.php?wuid=3044805892 blc16_2bit_blc16_guppi_58165_82671_DIAG_PSR_J0613 has been stuck in the my inconclusive list for over a month. The 3rd result was returned on 11 July and is still waiting validation. Just curious as anybody else had the same scenario?

Report deadline 31 Aug 2018, 23:20:00 UTC, this is when that task should get kicked. This happens more often than most think and usually happens just after an outage. ;-)

Cheers.

Thanks for all the responses. Normally I would agree with what you are saying but all the results are returned, guess I will just have to wait until 1 October as I am in New Zealand

---

Even less need to panic.. They gave us more gbt files
blc06_2bit_guppi_58329_... - for the curious this is July 30, 2018 .

Even less need to panic.. They gave us more gbt files
blc06_2bit_guppi_58329_... - for the curious this is July 30, 2018 .

. . But not a complete set this time ...

Stephen

. .

I had 100 tasks arrive from 17au18aa all vlar. I had a look on the SSP page and it must be a ghost tape because there is nothing listed there. On my 970 it looks like they are going to take 12 minutes/712 seconds each.

---

I had 100 tasks arrive from 17au18aa all vlar. I had a look on the SSP page and it must be a ghost tape because there is nothing listed there. On my 970 it looks like they are going to take 12 minutes/712 seconds each.

It's split and gone a long time ago. It takes 5 hours or so, before it works itself through the "Results ready to send" queue.
If as of now, there is 605,939 "Results ready to send", and there is 114,982 "Results received in last hour", you can calculate for yourself how many hours it can take
before the WU's from a split file starts getting sent out.

You're absolutely correct. I never thought of it like that. I must say and make the change from working on BLC tasks

---

Oh dear. All the old symptoms are back: stuttering message boards, stats delayed on the server status page, and no new work being issued.

There. Is that enough of a prod to cure them all?

Oh dear. All the old symptoms are back: stuttering message boards, stats delayed on the server status page, and no new work being issued.

There. Is that enough of a prod to cure them all?

And my account page only partially loads......

:D

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

Oh dear. All the old symptoms are back: stuttering message boards, stats delayed on the server status page, and no new work being issued.

There. Is that enough of a prod to cure them all?

And my account page only partially loads......

:D

Steve

And the last couple of tries, this rig was unable to connect to report work.
Meowsigh.

---

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

Uh-oh. All hosts down on work. No tasks are available. Wonder it the load on the servers that was up at 131K/hour finally caused them to buckle. Time for the elves in the lab to kick the servers.

---

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

A proud member of the OFA (Old Farts Association)

And my hourly WOW! report is barely a third of what it should be...

I just got a blast of work.

Yes. my hourly output is half what it should be.

---

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

A proud member of the OFA (Old Farts Association)

Well, it was worth posting about it - everything back to normal here (subject to checking WOW in 10 minutes' time).

Yes, always good to make the servers feel like their ears are burning. All hosts back up to full caches.

---

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

A proud member of the OFA (Old Farts Association)

not at panic stage... but interesting stage...
The RTS queue is slowly falling. it is still healthy at 515K . This could be due to the aforementioned problem and this is just the refilling of everyone's personal caches. Hard to say.

nevermind - already going up again. all is well. at this pace though the RTS is only good for 4.5 hours though.