|
|
 |
 |
Joined: 7/4/2006
Posts: 1079
|
|
|
In case you were unaware:
News
March 18, 2008 Project Temporarily Suspended We are suspending WU generation until the "Rombint" errors are solved and a new generator is up and running.
In the mean time, they're not addressing the issue of what's to happen with wus currently out in the wild. Watch your caches, and make sure you have a backup project ready in case this lasts a while.
Happy crunching!
Gary
You can't fix dead.
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/7/2006
Posts: 2508
|
|
|
I detached a week ago. Working on my SETI rac.
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/9/2006
Posts: 1183
|
|
|
March 19, 2008 Project daemons back up and running
The
project is now back up and running. The generator will be down for a
bit until we run down the available WUs, but then the new generator
will kick in.
Also, if you haven't attached to Cosmology since Jan 25, 2008, detach and reattach with the following url- http://cosmologyathome.org
As of today (Jan 24), the old URL (http://cosmos.astro.uiuc.edu/cosmohome) will
no longer function for making scheduler requests. In fact, the only
thing it *will* do is allow web browsers to navigate to the new URL.
Therefore, if you don't re-attach to the project, you will find it
difficult to keep crunching.
I've said it before, but I'll say it again: I sincerely
apologize for the inconvenience I've caused you. I didn't foresee a
"simple" task like changing the project URL to be so difficult, but it
ended up that way. If you have any concerns or questions, feel free to
make a post on the forum or send me a PM.
____________
Scott Kruger
Project Administrator, Cosmology@Home
|
|
|
|
 |  |
|
|
 |
 |
Joined: 2/24/2007
Posts: 485
|
|
|
NOTE from Cosmology:
March 19, 2008 Project daemons back up and running The project is now back up and running. The generator will be down for a bit until we run down the available WUs, but then the new generator will kick in.
 
Truth is after all a moving target
Hairs to split, and pieces that don't fit
How can anybody be enlightened?
Truth is after all so poorly lit - Getty Lee
|
|
|
|
 |  |
|
|
 |
 |
Joined: 10/1/2006
Posts: 627
|
|
|
I have some problems with this project in general.
The Wu's takes to much RAM, they make my computer stall which is not cool in anyway... This is so sad really, I like the projects goals in general !
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/9/2006
Posts: 1183
|
|
|
Past few days have seen a multitude of problems, I'm guessing there are many RAC happy people climbing on board the project, even with it's difficulties. End result seems to be they are overloaded, with erroring units looping and doubling or tripling the problem. The site is being hammered, forums are agonizingly slow. BOINC reports Project comunication failed and Scheduler request failed errors with me.
|
|
|
|
 |  |
|
|
 |
 |
Joined: 2/24/2007
Posts: 485
|
|
|
I have my computers not receiving work from cosmo or milkway currently. Seem both projects ignore work percentages and just whore off a pc. I have 400+ WU's for seti that wouldnm't have gotten done if I hadn't stopped the WU's from coming in. 1 PC was getting 1 milkway after another and didn't allow any other work to get done. including cosmo or rosetta. I'm getting a bit annoyed at a project that I set to 1% and it take up 20+% of all my work
 
Truth is after all a moving target
Hairs to split, and pieces that don't fit
How can anybody be enlightened?
Truth is after all so poorly lit - Getty Lee
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/4/2006
Posts: 1079
|
|
|
Getting work is spotty, and reporting results is also spotty. Seems that the project team is MIA for the weekend. I have one box that's super low, and is down to sharing with Einstein, but the others have more than enough work to last out the weekend.
We'll see how the project team handles things on Monday. It may be time to move on to another project if the problems with this project continue. I know they're beta, but usually teams pay more attention to beta projects...
Gary
You can't fix dead.
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/4/2006
Posts: 1079
|
|
|
Problems continued unchecked over the weekend, and the project team is MIA. As my boxes run out of work I'll be moving them permanently over to Einstein.
Gary
You can't fix dead.
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/7/2006
Posts: 2508
|
|
|
I like the idea of giving Einstein a good pounding. Think I'll do the same on a 50/50 split with SETI for a little while.
|
|
|
|
 |  |
|
|
 |
 |
Joined: 2/24/2007
Posts: 485
|
|
|
Xaak wrote Problems continued unchecked over the weekend, and the project team is MIA. As my boxes run out of work I'll be moving them permanently over to Einstein. looks like somebody wants to be a 6X millionaire
 
Truth is after all a moving target
Hairs to split, and pieces that don't fit
How can anybody be enlightened?
Truth is after all so poorly lit - Getty Lee
|
|
|
|
 |  |
|
|
 |
 |
Joined: 7/7/2006
Posts: 2508
|
|
|
Problem is fixed according to
Scott Kruger, Project Administrator, Cosmology@Home Here's the scoop on the weekend shenanigans:
I left on Thursday to visit the UWM physics department (home of
Einstein@Home). I made sure not to make any changes so things would at
least stay at the status quo while I was gone. However, it just so
happened that the mysql server decided to blow up (figuratively) while
I was gone.
After a number of hours working on the machine today, I finally figured
out what the problem was. Debian plays around with the mysql startup
script a bit, adding a check of the database integrity. However, the
integrity check faltered at some point and stalled. Because it was just
sitting there with a hold on the results table, queries kept piling up
and at some point, the number of pending queries exceeded the maximum
number of connections and everything went to hell.
I removed Debian's unnecessary check, increased the max_connections
parameter, and increased the share of the server's memory alloted to
mysql. Hopefully this will prevent more issues in the future.
The server is pretty overworked now as you can imagine, so I think it
would be best to wait until tomorrow to look into the validation issue.
|
|
|
|