• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Rosetta@Home stuck WUs

  • Thread starter Thread starter JC
  • Start date Start date
JC

JC

Diamond Member
Anyone else? This has happened at least 3 times in as many days now...currently it's a 'FA_RLXpt_hom006_1ptq_361_281_1'. Restarting BOINC seems to get it going again.
 
Haven't seen it here yet.... thanks for the heads-up though JC.

I'll watch times instead of % knowing this


-Sid
 
I havve a node not giving credit. It seems to run normaly, reports results with no CPU time. . I posted in the problem area at the rosetta site. Since then I discovered the graphics are broken on that rig. I would just reinstall every thing but I would like to keep the node number and ranking. Anyone know how to do that ?
 
I haven't found a way to do that Ken. I've just been merging the new installation with the old one. Keeps the points and RAC associated with the same PC, but the node number (computer ID) does change.

-Sid
 
in the your account section of the website, you can click on the view computers and see a list of all the installations BOINC thinks you have on that project. then you can select the link to see the details of any of those computers. at the bottom of the page, you should see a link to 'merge this computer'. when you click on that BOINC will give you a listing of all the computers 'matching' the one you started at. you can select merge there.

-Sid
 
March 22, 2006
Host Merging has been disabled for the time being... See Technical News for more details.
 
I havve a node not giving credit. It seems to run normaly, reports results with no CPU time. . I posted in the problem area at the rosetta site. Since then I discovered the graphics are broken on that rig. I would just reinstall every thing but I would like to keep the node number and ranking. Anyone know how to do that ?
Click to expand...

It can be done. Its not 100% foolproof, not endorsed but not completely frowned upon either.

As long as you keep the same OS(XP, W2K, etc) this should work*

Backup the entire bonic directory, move it to someplace safe.

If your going to start from scratch (ie wipe HD, new HD), reinstall OS, reinstall bonic, do not attach to any projects (will get new node if you do), copy your previously backeduped bonic directory(s) over the new installation, start bonic

If not starting from scratch, uninstall bonic, delete any remaining bonic directorys, clean out the registry of any bonic info, reboot, reinstall bonic (again don't attach to anything),
copy your previously backeduped bonic directory(s) over the new installation. start bonic.

Everything should then work fine with your old node number.

This worked for me on a couple of occasions. This host http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=325 started life as a Celey 900.

They are going to have to pry my low node id's from my cold dead hands.

*disclaimer...it worked for me, may not work for you. Worst case, you get a new node ID. YMMV. Not safe for children under 6, etc.
 
DAMN. I noticed some of my PCs were not reporting and they are stuck. I have a TOn of WUs called something like FA_RLXpt_hom006_1ptq__361_20_0. One has been going for 227 hours! *!@(&$

Is this a known issue at all? Do I just abort it? In my queue I have a ton of other WUs with the same name. I don't know if they will all kill it or what.
 
I'd just abort the stuck one. You can't tell from the names if it is going to stick or not.

The version 4.83 WUs are supposed to have a self-destruct built in at 24 hours, so the loss is a little more limited (I guess...)

-Sid

PS: it is a known issue
 
The 2.4c was stuck at 1% for 62 hours
The XP 1700+ 2 was stuck at 1% for 242 hours
The xp2400+ was stuck at 38% as well for over 200 hours

 
Originally posted by: Wolfsraider
The 2.4c was stuck at 1% for 62 hours
The XP 1700+ 2 was stuck at 1% for 242 hours
The xp2400+ was stuck at 38% as well for over 200 hours
Click to expand...

OUCH 🙁

One time I ignored the potted plants on the patio for 10 days...... half of them died 😛
 
Is there anything out of the ordinary about these systems that keep geting WUs stuck?

I've had none get stuck so far, which is either good or bad depending how you look at it with my participation in Ralph.
 
Originally posted by: Insidious
Originally posted by: Wolfsraider
The 2.4c was stuck at 1% for 62 hours
The XP 1700+ 2 was stuck at 1% for 242 hours
The xp2400+ was stuck at 38% as well for over 200 hours
Click to expand...

OUCH 🙁

One time I ignored the potted plants on the patio for 10 days...... half of them died 😛
Click to expand...

Yep half seems to be about right 😛
 
Originally posted by: RobertE
Is there anything out of the ordinary about these systems that keep geting WUs stuck?

I've had none get stuck so far, which is either good or bad depending how you look at it with my participation in Ralph.
Click to expand...

I am not sure, to be honest, mine were all in the garage...that had stuck wu's, but I am seeing it across the board at various times, could be certain batches. I don't think its computer related as:

I am running
2.8 xeon dual cpu
3.2 prescott
2.4 p4 o/c to 2700
2400+ amd
2 1700 amd's
1 opteron 165 o/c to 2340

and as stated its hit them all at one time or another.

I have seen that if I set the boinc manager to run always and always connected and use the latest truxsoft client it does seem that the wu's stuck at 1% are less than set anyother way.
 
I thnk I'm just going to abort everything im y queues and start over. I don't have time to check these things every day and one's been going for like 250 hours.
 
Well I went through and deleted all the WUs that were listed as the .82 application so it would get new ones as the .83. So far so good. TOo bad I didn't notice sooner. I missed out on thousands of credits. Stupid WUs.
 
Originally posted by: FrankyJunior
Well I went through and deleted all the WUs that were listed as the .82 application so it would get new ones as the .83. So far so good. TOo bad I didn't notice sooner. I missed out on thousands of credits. Stupid WUs.
Click to expand...

I hear you man. My daily results flip-flop more than John Kerry due to stuck machines.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top