We thought we had the hardware problem with the workunit download server diagnosed, but looks like we were wrong. False positive. The good news is that the kind folks who donated the thing have another ready to ship. But until we get it, that probably means potential random resets all weekend. Jeff just put an /etc/rc script in place so that upon reset/reboot there's a chance it'll be operational, meaning short glitches instead of multi-hour outages. That's the hope anyway. We might actually test that later today (if it doesn't reset itself on its own). There was discussion about how to implement a second workunit storage server so we don't have this single point of failure anymore. Not as easy as it sounds.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Thanks for the update.

Back tracking is a pain, and implementing a solution is never easy when the reason appeared to have been identified.

Keep your chin up, as it will sort out eventually

---

It's good to be back amongst friends and colleagues

Ah, "Thinking Thursday" - whoever would have thought it? :D LOL.
Thanks for the update AND the hard work :)

---

Matt, When you get a chance could you kick BETA? Thanks again for the hard work!

Matt, When you get a chance could you kick BETA? Thanks again for the hard work!

And the download server, if the current slowdown isn't a deliberate test/repair.

Don't expect much joy for the next 10 hours in beta or the public project - the latest reset triggered a full RAID resync, which will take at least that long. In theory we could run the project while the devices sync up, but due to the extra I/O that will take about two weeks to complete. Sigh.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

. . . Thanks for Posting Matt - Nice goin' @ Berkeley > things are workin' better here w/ my boxes @ least ;O

< thought You might like a 'slight' distraction;

. . . Thinking Thursday: Magic and Ethics

. . . an ethical dilemma that’s obscure and on the surface, meaningless. However, to a certain subset of a subset of people,

it’s a huge problem that we wrestle with constantly, almost every single time we interact with the public

edit: nice edit Matt ;)

---

BOINC Wiki . . .

Science Status Page . . .

Don't expect much joy for the next 10 hours in beta or the public project - the latest reset triggered a full RAID resync, which will take at least that long. In theory we could run the project while the devices sync up, but due to the extra I/O that will take about two weeks to complete. Sigh.

- Matt

C'est la vie . . .

You do your best and we'll do ours (or is that hours?
I do mine with recycled electrons to keep the cost down.
Stan Fockner

Don't expect much joy for the next 10 hours in beta or the public project - the latest reset triggered a full RAID resync, which will take at least that long. In theory we could run the project while the devices sync up, but due to the extra I/O that will take about two weeks to complete. Sigh.

- Matt

Well 10 hours is better than 336 hours(2 weeks). :D

---

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

It's at times like these I wonder if it would be better to scale back the project, fix/perfect the issues, and then restart the growth cycle. Not doing so seems like a huge psycho-strain by everyone and a source of volunteer-distress.

Another solution would be to rally the user base so that at a given UTC time we all chug 20oz of our individually favorite local brew together, as a team. That may lead to the only real manifestation of global warming, and concurrently may be the only true relief of our user/volunteer angst. I sugeest 1400UTC on Friday, April 11, but am open to alternative times and dates. (Obviously, I'm willing to risk the short term global water shortage when 20m later we all process our beer down the toilet. Life is not worth living unless you risk a bit.)

It's at times like these I wonder if it would be better to scale back the project, fix/perfect the issues, and then restart the growth cycle. Not doing so seems like a huge psycho-strain by everyone and a source of volunteer-distress.

Another solution would be to rally the user base so that at a given UTC time we all chug 20oz of our individually favorite local brew together, as a team. That may lead to the only real manifestation of global warming, and concurrently may be the only true relief of our user/volunteer angst. I sugeest 1400UTC on Friday, April 11, but am open to alternative times and dates. (Obviously, I'm willing to risk the short term global water shortage when 20m later we all process our beer down the toilet. Life is not worth living unless you risk a bit.)

I won't argue against beer drinking, although 1400UTC is a little early here.

I may run out of work for the first time in years, which is saying something since I usually don't carry much of a cache. Then again, I might not run out of work.

So, just in case, I've reattached to LHC, since they seem to have work, and I'll still be here tomorrow when the download server will likely be back up.

---

In keeping with the current theme (beer drinking not excluded) I have the perfect title for tomorrow's thread.
(Trying Tuesday, Working Wednesday, Think again Thursday).....


ooops... never mind.... the censor won't let me post my thread title suggestion. ;)

In keeping with the current theme (beer drinking not excluded) I have the perfect title for tomorrow's thread.
(Trying Tuesday, Working Wednesday, Think again Thursday).....


ooops... never mind.... the censor won't let me post my thread title suggestion. ;)

Think Battlestar Galactica....

---

Could always do Fukitol Friday. For those that don't know what that is, I can provide a link to the infomercial if you PM me. ;-)

Could always do Fukitol Friday. For those that don't know what that is, I can provide a link to the infomercial if you PM me. ;-)

BINGO!

In keeping with the current theme (beer drinking not excluded) I have the perfect title for tomorrow's thread.
(Trying Tuesday, Working Wednesday, Think again Thursday).....


ooops... never mind.... the censor won't let me post my thread title suggestion. ;)

Your thought was easy to follow and appreciated by me and its great to start the day with a good giggle - although you guys may think differently! I suppose I'll just have to be patient; the odd thing is one of my PCs got more work, only a few minutes before the other tried to get more (and failed). Thats Life, I suppose.

---

Don't take life too seriously, as you'll never come out of it alive!

Don't expect much joy for the next 10 hours in beta or the public project - the latest reset triggered a full RAID resync, which will take at least that long. In theory we could run the project while the devices sync up, but due to the extra I/O that will take about two weeks to complete. Sigh.

- Matt

I think the next post should have the subject "running on empty" :-)

My machines will soon be out of work, even with 2 days extra cache on most of them. JD's Thurston won't know what to do with itself.

---

BOINC blog

You might be spared running on empty, someone got up early and opened the gates.
Cricket graph

---

You might be spared running on empty, someone got up early and opened the gates.
Cricket graph

No, that's the end of the "ten hours" that Matt mentioned ;),

[add] the d/l server is exhibiting its usual signs of laboring under stress - breaking d/l's in the middle, not starting them, refusing to even consider them, etc.[/add]

---

.

Hello, from Albany, CA!...