Hey Everyone,

The MilkyWay server will be going down from 4PM today until midnight. After this outage, we should have the server up and running as normal, and the workunit generation issue will hopefully be solved.

Best,
Tom

Thanks for the heads up and your work. Much appreciated.

Greetings,

Thanks for the notification on maintenance, Tom. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

The server is back up after some tweaking of the server's database. Hopefully that fixes the problems that we were having. We are currently monitoring the system, and I will have more info for you all tomorrow.

- Tom

Greetings,

Thank you for informing us :]

---

There are still no workunits for Milkyway@Home in BOINC, even the waiting ones disappeared! Quitting, restarting and updating Milkyway@Home are without effect.

Same, still nothing, and server status lists none available. But it doesn't even seem to connect properly, because I changed the project resource share and it doesn't update.

I checked my tasks list and I have a lot of "cancelled by server" notations. Is this part of the usual restart procedure?

---

Plus SETI Classic = 21,082 WUs

Still seeing no new tasks as of this writing.

We fixed the problem with the work generators, but our fix seems to have caused a problem with the transitioner, which means that no new workunits are going out at the moment. We will have to do some server maintenance again in the near future to fix this, and I'll update you all with details when I know more.

This is a problem caused by running out of valid workunit IDs (since you all have crunched over 2 billion workunits!) so we had to reset the entire database ID count and delete old workunits. As a result, there are some residual ID mismatches that we are trying to find and sort out. The transitioner was working as of midnight last night, but it seems to have switched off sometime in the early morning.

Thanks for your patience,
Tom

Let me guess, we crunched 2,147,483,647 work units lol. Might I suggest you plan for this eventuality, as it will happen again and more quickly as GPUs will continue to get faster and faster. Without knowing how your DB is set up, or even what DB you are using I could not begin to offer a solution but would be happy to have a look if y'all have room for another volunteer :)

Yup, you got it. I don't think the Boinc framework really planned on encountering this problem. This happened to a different table in the past, so we are aware of the issue, but as far as I can tell other projects haven't hit this limitation yet.

We are discussing ways to prevent this problem in the future. The simplest "fix" would be to change the Primary Key of each affected table to a BIGINT instead of an INT, which we may end up doing at some point in the future once things are working again.

I believe that was SETI@HOME's solution (64 bit INT).. (The joys of success!!)

Ed F

All looks good on this user's end. Crunching again.

Yep, seems all right for me too. Crunching WUs nicely.
Thanks for sorting this out!

Well, it's working in the idea that I'm getting work, but only a couple WU's at a time.

Plenty of work and verifying just fine so far.

---

Plus SETI Classic = 21,082 WUs