Drat, all I'm getting across all 3 machines are "no tasks are available" The toggle in Preferences didn't do anything.

---

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

A proud member of the OFA (Old Farts Association)

OK, it took a few cycles of requests to start work flowing again after my Preferences toggle. I'm getting about 80/20 BLC to Arecibo work on the last successful request. I've put tasks per GPU back to 2 also.

---

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

A proud member of the OFA (Old Farts Association)

No panic here...

I welcome BLC work units.....

. . There's one in every crowd! :)

Stephen

:)

Shedloads of Guppis and no AP's :-(

There are a couple of new Arecibo files loaded, and they're splitting some AP from them.
And with plenty of Guppies, the system will be busy for longer during the weekly outage. Might even make it all the way through... (nah, but it's a nice thought).

---

Grant
Darwin NT

Servers are back online but can't be reached with comms error.

---

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

A proud member of the OFA (Old Farts Association)

Servers are back online but can't be reached with comms error.

. . Yep, back online, have reported all completed tasks but while not getting any comms error I am getting "Project has no tasks available".

. . I guess Einstein will get a little more work out of me today ....

Stephen

:(

Yeah, the servers can't be reached because of HTTP errors only lasted about 5 minutes. Now is just no work is available.

---

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

A proud member of the OFA (Old Farts Association)

The task creation rate spiked to 50+ per second right after coming back online. But it has now crashed and burned down to 2/sec.

---

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

A proud member of the OFA (Old Farts Association)

Looks like all 7 GBT splitters are running on the same file now. That is a recipe for disaster. Or at least curtailed WU output as mentioned just above.

---

Greetings All

Found a strange one, and there might be a topic for it, but it could be 5 pages or more away.

So the following task, has been marked - Completed, validation inconclusive, on both the 1st and 2nd recipient and now waiting for the 3rd recipient.

https://setiathome.berkeley.edu/workunit.php?wuid=2463641979

Trouble is the 3rd received it on the 11th March and it is now nearly May, he/she hasn't returned any tasks at all (52), thinks it may be a ghost/dead machine.

Or maybe on a positive note, has crunched them, but is not in a position to upload them.

Oh well, at least on a positive note, the supply of workunits is good lol.

Happy Crunching
Mark

Greetings All

Found a strange one, and there might be a topic for it, but it could be 5 pages or more away.

So the following task, has been marked - Completed, validation inconclusive, on both the 1st and 2nd recipient and now waiting for the 3rd recipient.

https://setiathome.berkeley.edu/workunit.php?wuid=2463641979

Trouble is the 3rd received it on the 11th March and it is now nearly May, he/she hasn't returned any tasks at all (52), thinks it may be a ghost/dead machine.

Or maybe on a positive note, has crunched them, but is not in a position to upload them.

Oh well, at least on a positive note, the supply of workunits is good lol.

Happy Crunching
Mark

. . Hi there Mark,

. . The sad reality of crunching for Seti is that there many derelict machines out there. Some are newbies who tried it and were unimpressed, leaving again with a cache full on uncompleted tasks to sit in limbo for a couple of months. Others are older contributors who probably should know better but for whatever reason have left the project doing the same thing. There's no excuse for them, it takes only a couple of minutes to set "No new work", mark all uncompleted tasks as aborted and upload that to the servers before shutting down. I wish more people would pick up on that.

. . The good news is that all his "ghosted" tasks will expire before the end of the week and hopefully bounce to another host that is NOT a derelict machine.

Stephen

:(

...and one class of computer you miss - those that have suffered a major hardware failure which prevents the computer from being used - "failure" might include the data disk failing, a house fire, the computer being stolen, all of which have happened and will happen again. Thankfully these are relatively rare events, but hey do contribute to the list of computers "missing in action" :-(

(Said with some feeling as I sit here looking at a pair of 2Gb disks that failed when a PSU decided to send 230v up the 12V line to them...)

---

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

...and one class of computer you miss - those that have suffered a major hardware failure which prevents the computer from being used - "failure" might include the data disk failing, a house fire, the computer being stolen, all of which have happened and will happen again. Thankfully these are relatively rare events, but hey do contribute to the list of computers "missing in action" :-(

(Said with some feeling as I sit here looking at a pair of 2Gb disks that failed when a PSU decided to send 230v up the 12V line to them...)

. . Yes I did overlook that group, my apologies to those thus afflicted and as for your HDDs, ... OUCH!

. . I should have thought to include them as Wiggo had a power outage take his machine down only to find no working HDD when it fired back up. Thankfully he had a spare unit and reconfigured it and is back crunching ... but there are now x number of ghosties on his rig too. I have offered him a copy of my tried and proven Ghost Recovery process but so far no answer :)

. . I will qualify that by adding the process was provided by someone else but I have added my own refinements to make it pretty much bullet proof. The only drawback is that it is a little fiddly and can only recover 20 ghosts at a time (that is all the system will send you) so if you have a lot of ghosts it can take a while, but better than leaving them, and your wingmen, in limbo for two months :)

Stephen

:)

...and one class of computer you miss - those that have suffered a major hardware failure which prevents the computer from being used - "failure" might include the data disk failing, a house fire, the computer being stolen, all of which have happened and will happen again. Thankfully these are relatively rare events, but hey do contribute to the list of computers "missing in action" :-(

(Said with some feeling as I sit here looking at a pair of 2Gb disks that failed when a PSU decided to send 230v up the 12V line to them...)

. . Yes I did overlook that group, my apologies to those thus afflicted and as for your HDDs, ... OUCH!

. . I should have thought to include them as Wiggo had a power outage take his machine down only to find no working HDD when it fired back up. Thankfully he had a spare unit and reconfigured it and is back crunching ... but there are now x number of ghosties on his rig too. I have offered him a copy of my tried and proven Ghost Recovery process but so far no answer :)

. . I will qualify that by adding the process was provided by someone else but I have added my own refinements to make it pretty much bullet proof. The only drawback is that it is a little fiddly and can only recover 20 ghosts at a time (that is all the system will send you) so if you have a lot of ghosts it can take a while, but better than leaving them, and your wingmen, in limbo for two months :)

Stephen

:)

Yeah, going through that right now with one. 8 month old 250g SSD died, no backup, of course.

---

Yeah, going through that right now with one. 8 month old 250g SSD died, no backup, of course.

On the bright side it should still be under warranty. Best of luck with your data recovery

---

This WU certainly was around the block to validate.
http://setiathome.berkeley.edu/workunit.php?wuid=2518067783
I kept it in case someone wants to look at it.

This WU certainly was around the block to validate.
http://setiathome.berkeley.edu/workunit.php?wuid=2518067783
I kept it in case someone wants to look at it.

One of the systems is pumping out heaps of Invalids & Errors.
EDIT-
Another is pumping out almost nothing but Invalids & Inconclusives.
Another has 2 Valids, and everything else is an Error.
I'm guessing the 2nd computer that scored the Valid result was initially inconclusive against the first computer to return Valid work, looks like yours confirmed the result.

---

Grant
Darwin NT

...and one class of computer you miss - those that have suffered a major hardware failure which prevents the computer from being used - "failure" might include the data disk failing, a house fire, the computer being stolen, all of which have happened and will happen again. Thankfully these are relatively rare events, but hey do contribute to the list of computers "missing in action" :-(

(Said with some feeling as I sit here looking at a pair of 2Gb disks that failed when a PSU decided to send 230v up the 12V line to them...)

. . Yes I did overlook that group, my apologies to those thus afflicted and as for your HDDs, ... OUCH!

Yeah, going through that right now with one. 8 month old 250g SSD died, no backup, of course.

. . You have reminded me of something I should probably take care of right away :)

. . Time to make a backup of all seti drives ....

Stephen

:)

. . @ Keith

. . I was reminded today of our conversation about running Arecibo VLAR tasks on GPUs using SoG.

. . On my new rig, Bertie, I made a goof with the scheduling and ran out of GPU tasks. So to keep the GPUs working while I sorted it out (uploaded a swathe of result files and downloaded some fresh stuff), I moved some of the Arecibo VLAR tasks queued behind the CPU into the GPU Q. As I am doing four at a time (2 per GPU) I moved 4 across and they were all done in 24.5 mins on my GTX 970s (SoG r3557). Normal Arecibo tasks under the same conditions take 13 to 14 mins. Not quite twice as long but at least they were being productive. So anytime you feel the need to do the same I am pretty sure you will be fine.

. . Of course I have not tried that with r3584.

Stephen

.

Hi Stephen, I should try and find the answer myself with a forum search, but since I have your attention, what is the method you use to move a Arecibo VLAR onto a Nvidia GPU? The scheduler won't do it because of the way the move rules are written. I too have been in troubles especially on outage days where I run out quickly on GPU tasks and it would be nice to move some CPU tasks to GPU. At least for the slow FX systems. I've learned that is counter productive on the Ryzen system since it would run out just as fast for both task types on that system. Best to let it run un-optimized without rescheduling on outage days.

---

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

A proud member of the OFA (Old Farts Association)