Reason: project is down Mo 12 Feb 01:10:43 2007|Einstein@Home download Masterfile then Mo 12 Feb 01:06:50 2007|Einstein@Home|Scheduler request failed: HTTP internal server error Mo 12 Feb 00:53:01 2007||Fetching configuration file from http://einst
Language
Copyright © 2024 Einstein@Home. All rights reserved.
I join the unwashed masses. I
)
I join the unwashed masses. I too haven't gotten any work units from Einstein@home in, I'd guess, 10 days or so. When you try to "report problems" via BOINC, you just get message boards where we talk to each other. Evidently, some people are having the usual success in dealing with E@home, but many are not. What adds insult to injury is the lack of any real place to say: "Hello. We have a problem." Someone is really asleep at the switch and/or the Einstein "system" is not designed well enough to recognize and handle problems. "The server status page has temporarily been taken offline due to database problems." That's a feeble way to respond when you finally wake up to a problem. The Einstein folks will need to do some serious redesign work, and some serious PR, if they hope to keep people interested in doing their work.
RE: "The server status page
)
The admins have known for well over a month now that they have database and server problems and have relayed this information to us here at Einstein. That you may have missed this information is not their problem.
Bruce is at this moment rebuilding the back end components, to see if that can speed up the database without too many problems. Or at least try to get it down from 900 queries a second to something a little more normal.
Anyway, try reading an old thread like this one to see why it may be that there's so little admin acknowledgment around here. Or read Gary's post here on what may be happening.
Want to help Einstein? Attach to other projects as well. BOINC is made with that in mind.
The people who wrote BOINC
)
The people who wrote BOINC (which is also the name of the software on the web/database side of things) had this to say, yesterday:
Anyway.. some good news. Bob may have gotten to the core of our database query problems, which is just in time as it seems other BOINC projects may be experiencing similar behavior as their databases swell. Basically it may just be as simple as adjusting database variables so specific queries won't keep whole tables in memory just in case updates are made during potentially long lookups. These queries don't require super-accurate information (like the result/workunit counts on the server status page), so if they are off by one or two out of a half million, so be it.
So it sounds like some issues were found, and they will be relaying it to the projects, and hopefully we will see some if these issues resolved, soon.
I've started to receive
)
I've started to receive credit for some of the WUs I reported last week... I would imagine the validators are a bit busy at the moment. ;) Progress is good, though, we like that!