Given that the majority of this issue seems to effect only Anonymous platforms, I have to wonder who besides SETI actually supports the Anonymous platform in production? Not trying to excuse the clearly malfunctioning or non-existent change control system, since there really is no excuse. Just curious.

---

BOINC as a whole "supports" it, and has done since the very beginning. But SETI probably "exploits" it more than any other public project that we know about. We - and BOINC - have no idea how many private projects exploit it, because we don't even know how many private projects exist.

BOINC seems to be very allowing when you want to do your own thing. I mean someone had the foresight to create the <dont_check_file_sizes> flag seemingly just to allow people to do what they want. And I'm glad they did for instances like this. It basically lets you run anonymous platform when not under anonymous platform lol.

---

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

Both my hosts have stalled downloads now...

If I had the knowledge I would have done it already and made a new windows app, then gone back to watching the clouds again.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

I'm shooting down my host until the issue where corrected. Hope soon.

For those who celebrate i wish a Merry Christmas.

---

. . On the one machine I changed to stock (renamed app_info.xml) I received a good number of tasks over several hours, but since implementing the AnonPlat workaround, while crunching is AOK, I have not received a single new task.

. . I think that roll back is essential ........

Stephen

:(

There have been so many posts on this SETI problem that I may have missed an answer to the following question.
Does the staff at Berkeley think a resolution might come soon, or might it take more than a week?
From reading the posts, I believe that is the question for which everyone really needs an answer.

There have been so many posts on this SETI problem that I may have missed an answer to the following question.
Does the staff at Berkeley think a resolution might come soon, or might it take more than a week?
From reading the posts, I believe that is the question for which everyone really needs an answer.

I believe this is the best answer available for your question: https://setiathome.berkeley.edu/forum_thread.php?id=84983&postid=2024655

---

Muchas gracias Juan.
That is exactly what I was looking for.
To save time for everyone who hasn't seen it, I will reprint Richard Hasselgrove's earlier post:

____________________________________________________________________________________
Posted: 23 Dec 2019, 16:55:49 UTC

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.
ID: 2024655 · Report as offensive \
Posted: 23 Dec 2019, 16:55:49 UTC

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.
____________________________________________________________________________________


p.s. Thank you, Richard!

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.

This sounds great. I wish them all the best with reverting to an earlier version of the server code.

---

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.

This sounds great. I wish them all the best with reverting to an earlier version of the server code. Hope what Eric said below isn't true
Message 2024312 - Posted: 22 Dec 2019, 8:10:05 UTC (Old 117 thread)

Unfortunately there a database change that renders the 7.09 server inoperable. :(

Hence the statement "revert the database"...

---

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.

This sounds great. I wish them all the best with reverting to an earlier version of the server code. Hope what Eric said below isn't true
Message 2024312 - Posted: 22 Dec 2019, 8:10:05 UTC (Old 117 thread)

Unfortunately there a database change that renders the 7.09 server inoperable. :(

Hence the statement "revert the database"...

Thanks for that I change to my original post

---

Hence the statement "revert the database"...

Or more aptly:

Reverse the polarity of the neutron flow?

;-)

Keep searchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Another problem shared from BETA, some of these Host detail numbers have been frozen all day. Namely the APR numbers.
SETI@home v8 8.11 x86_64-apple-darwin (cuda42_mac)
Number of tasks completed 135
Max tasks per day 156
Number of tasks today 2873
Consecutive valid tasks 54
Average processing rate 1,740.18 GFLOPS

SETI@home v8 8.19 x86_64-apple-darwin (opencl_nvidia_mac_old)
Number of tasks completed 139
Max tasks per day 52
Number of tasks today 2000
Consecutive valid tasks 2
Average processing rate 1,768.32 GFLOPS

By this time, the cuda42 numbers should be quite a bit higher, but, they haven't changed.
https://setiathome.berkeley.edu/host_app_versions.php?hostid=6796479

Muchas gracias Juan.
That is exactly what I was looking for.
To save time for everyone who hasn't seen it, I will reprint Richard Hasselgrove's earlier post:

____________________________________________________________________________________
Posted: 23 Dec 2019, 16:55:49 UTC

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.
ID: 2024655 · Report as offensive \
Posted: 23 Dec 2019, 16:55:49 UTC

For general information

I've had a provisional whisper back from the project. As of about an hour ago, the provisional plan is to go through normal maintenance and backup tomorrow (Tuesday), and then revert the database changes so we can go back to running the old server code.

My gloss on that is that it probably means a longer outage, and an even worse than usual recovery, but everyone should be able to enjoy the rest of the holiday in peace. Most especially, the staff can relax. Sounds like a good idea to me.
____________________________________________________________________________________


p.s. Thank you, Richard!

My wishes with you!

p.s.
After another call to Santa I can verify with the the following:
I'm going to replace some GPUs and it seems so I can have time to tune them up too.

Nightey Nightey! [nati nati]

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

My wishes with you!
p.s.
After another call to Santa I can verify with the the following:
I'm going to replace some GPUs and it seems so I can have time to tune them up too.
Nightey Nightey! [nati nati]

. . Can I have the discards ? ? :) . {joke}

. . Merry Christmas Petri!

Stephen

:)

Hi All

I haven't been very active the last couple of years or so, I thought I might fire up a box or two now that SAH has had the time to fix the software/server/WU availability issues that had been plaguing them...

---

Member of the 20 Year Club

After some interruptions and getting a couple of jobs done outside before that so called rain gets here (if it even bothers to turn up at all) I've just finished cleaning out all the dust, ash and soot from the last 3 months out of my 2500K rig as well as updating it so it's ready for when things come back up properly.

I'll do the other in the morning as it's getting far too warm here now and my back needs a rest while I need to enjoy a few beers. ;-)

Cheers.

Uhh, don't know where you read that the project was back to normal. It is not. Won't be until after tomorrow's outage/backup/recovery. (Fingers crossed.)

---

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

A proud member of the OFA (Old Farts Association)