The XML exports are not updating. Can someone give them a kick ?

Last update user XML 2020-04-21 03:20:03 UTC (6 days 10:48:03 old)
Last update host XML 2020-04-21 03:20:03 UTC (6 days 10:48:03 old)
Last update team XML 2020-04-21 03:20:03 UTC (6 days 10:48:03 old)

From Boinstats

Thanks
Bill F

---

They know about it. Doubt that they intend to fix it. Any credits granted past 4/21 will only be visible at the website. The 3rd party stats websites will be frozen at that date. In the case of BoincStats, your Seti credit will disappear anyway after 60 days of no host contacting the project and reporting work that would be exported. So get used to it, it will be the normal condition going forward.

---

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

A proud member of the OFA (Old Farts Association)

It would be very nice if they fixed this problem. A lot of us are helping to finish up the remaining work units to tidy things up. I and others would sure appreciate an update to bonicstats. Thanks Angie.

---

Not believe anyone will hear you unless you post your claim in the Seti FB. Unfortunately :(

---

Not believe anyone will hear you unless you post your claim in the Seti FB. Unfortunately :(

Had we known the project was just going to shut down, perhaps we wouldn't have donated to BOINCstats to help keep them alive, or pitched in to buy storage for SETI@Home as well. Guess you live and learn.

I think this project shutting down is going to impact a lot more than just S@H.

Not believe anyone will hear you unless you post your claim in the Seti FB. Unfortunately :(

Had we known the project was just going to shut down, perhaps we wouldn't have donated to BOINCstats to help keep them alive, or pitched in to buy storage for SETI@Home as well. Guess you live and learn.

Your donation to BOINCstats supports them not Seti and stat's are good to promote competition regardless of if it is Rosetta@home for Medical Science or the World Community Grid for Cancer research. You were correct to donate,

Bill F

As for Seti@home not caring enough to finish up professionally well some people may have gotten too big for their britches. My Last WU went in this morning my first was May of 1999.

---

External Stats are powered by the BOINC replica database, which has been Offline for about a week.

https://setiathome.berkeley.edu/show_server_status.php

I would be very appreciative if it could be brought back online, especially if it is not damaged. Angie

---

I would be very appreciative if it could be brought back online, especially if it is not damaged. Angie

I think it's probably on the project staff's to-do list, but they are concentrating their limited resources on completing the final data set for the Science Database.
The project will continue running after their primary objective has been completed
Getting the stats out to external sites is probably a nice thing to have, but not the highest priority while they are working from home.

If they brought it back online, it might cause operational issues with it being so far out of date at this point and needing to be synced up with the master again. They might be just waiting for all the outstanding WUs to be validated before bringing it back, if they even plan to bring it back at all.

---

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

Not believe anyone will hear you unless you post your claim in the Seti FB. Unfortunately :(

Had we known the project was just going to shut down, perhaps we wouldn't have donated to BOINCstats to help keep them alive, or pitched in to buy storage for SETI@Home as well. Guess you live and learn.

Your donation to BOINCstats supports them not Seti and stat's are good to promote competition regardless of if it is Rosetta@home for Medical Science or the World Community Grid for Cancer research. You were correct to donate,

Bill F

As for Seti@home not caring enough to finish up professionally well some people may have gotten too big for their britches. My Last WU went in this morning my first was May of 1999.

You misunderstand. I donate to both.

If they brought it back online, it might cause operational issues with it being so far out of date at this point and needing to be synced up with the master again. They might be just waiting for all the outstanding WUs to be validated before bringing it back, if they even plan to bring it back at all.

And this goes back to my original post on the matter. It really has to do with prioritization right now, and the biggest priority is completing the project. It isn't the way any of us would have liked it to happen, but we are nearing the end. I do believe that they'll get to it, I hope they do, even if it is just for that final snapshot. In that same scope, it would be nice if BOINCstats kept that final image as a static page, but I can't make any demands of them. They'll approach this as they will, but it will look shabby to others if they decide to just arbitrarily delete entire historical records from their archives.

The only other possibility here is if they recreated the backup database. It would be much faster than having to wait for it to catch up to the prior database, even still, that would require another down day to do a database backup on the primary database, while they're doing the actual creation of the new database, and begin synchronization at the current snapshot of the database.

God! Nightmares of making new replica databases and exchange databases just came back to me. STOP IT! :). Make the voices stop mommy.

The only other possibility here is if they recreated the backup database. It would be much faster than having to wait for it to catch up to the prior database, even still, that would require another down day to do a database backup on the primary database, while they're doing the actual creation of the new database, and begin synchronization at the current snapshot of the database.

They probably burned through so many hard drives on the replica database of late because of disk thrashing that they've ran out of drives for it.

Cheers.

The only other possibility here is if they recreated the backup database. It would be much faster than having to wait for it to catch up to the prior database, even still, that would require another down day to do a database backup on the primary database, while they're doing the actual creation of the new database, and begin synchronization at the current snapshot of the database.

They probably burned through so many hard drives on the replica database of late because of disk thrashing that they've ran out of drives for it.

Cheers.

That, I would absolutely believe my friend. Sight unseen, proof not needed.

Edit: I had just started working at an online backup site, and they had an issue with thrashing. Due to an executive decision, lower grade drives were purchased which were not enterprise grade to cut costs. It was only then they realized their mistake. The thrashing was so intense, grooves the size of the RW head were literally carved into the platters. That is the problem with spindle drives, and executives who don't understand technology.

I contacted Eric and he responded.................
"Carolyn has been down. I've started stats dump on oscar."


Meow, Eric!

---

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

I contacted Eric and he responded.................
"Carolyn has been down. I've started stats dump on oscar."


Meow, Eric!

---

I contacted Eric and he responded.................
"Carolyn has been down. I've started stats dump on oscar."


Meow, Eric!

Thank you Eric, and Mr KatMan.