Posts by Rob Lilley

1) Message boards : Number crunching : Not getting any work units (Message 64792)
Posted 4 Jan 2010 by Rob Lilley
Post:
I have two computers linked to the same account. A few days ago, I stopped getting work units. I have not changed any account settings. I have reinstalled BOINC / attached and detached from the Rosetta@Home Project. But I keep seeing:

"Requesting New Tasks"
followed by
"Scheduler Request completed: got 0 new tasks"

Both computers are Core2Duo machines running Windows XP. I am using Boinc 6.10.18 which is the installer linked on Rosetta@Home website. What's up?


For further info, see this thread

It's not you, it's the project :)
2) Message boards : Number crunching : Minirosetta 1.98 (Message 63893)
Posted 31 Oct 2009 by Rob Lilley
Post:
Error on this WU after a couple of wasted hours of crunching, as follows:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00436BD8 read attempt to address 0x016AE000

I was using this machine, running XP SP3 and usinb BOINC version 6.6.41

Will suspend work fetch and await developments...
3) Message boards : Number crunching : Minirosetta 1.82/1.88 (Message 62418)
Posted 25 Jul 2009 by Rob Lilley
Post:
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x006C1C6D read attempt to address 0x00000000

Happened on this WU after 2 hrs 50 min. This machine worked fine with Rosetta Mini v1.80.


Another access violation for this WU, and it's definitely not just me, as my wingman got the same error.
4) Message boards : Number crunching : Minirosetta 1.82/1.88 (Message 62269)
Posted 17 Jul 2009 by Rob Lilley
Post:
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x006C1C6D read attempt to address 0x00000000

Happened on this WU after 2 hrs 50 min. This machine worked fine with Rosetta Mini v1.80.
5) Message boards : Number crunching : Minirosetta v1.40 bug thread (Message 57229)
Posted 25 Nov 2008 by Rob Lilley
Post:
This Minirosetta v1.40 Work Unit is another one that won't suspend and continues running when pre-empted by a QMC WU.

Should I abort the Minirosetta Work Unit or suspend all the other projects that play nice until the Minirosetta WU finishes?



try what i did, exit boinc manager and then reopen. however i did a complete reboot of the system after that so i have no idea if just the closing and reopening of boinc manager will solve that problem.


I tried that, and it doesn't seem to work. I am running BOINC as a service, so there's a different method for stopping it anyway, according to a thread I found somwhere on the BOINC message boards, but that doesn't work either. If I do stop both the BOINC Manager and the BOINC Core Client, Minirosetta continues to run. The Windows Task Manager shows the minirosetta task hasn't unloaded, and the CPU usage stays at 100%. I could end the Minirosetta process, but I am reluctant to do that.


try exiting the boinc, do not delete anything from your folders. goto add/remove software and unistall boinc. then reinstall. kind of drastic, but thats all i can think of. maybe someone else has an different idea.



Didn't do that, just suspended all other projects then restarted the computer. Turns out it was probably a bad WU anyway, as it worked for a while then came to a dead stop and woudln't restart. After I tried restarting BOINC, it then errored out and came up with the lockfile error others are experiencing, as you will see here.

Ah well, some other poor sap will get that nasty WU now :(
6) Message boards : Number crunching : Minirosetta v1.40 bug thread (Message 57210)
Posted 24 Nov 2008 by Rob Lilley
Post:
This Minirosetta v1.40 Work Unit is another one that won't suspend and continues running when pre-empted by a QMC WU.

Should I abort the Minirosetta Work Unit or suspend all the other projects that play nice until the Minirosetta WU finishes?



try what i did, exit boinc manager and then reopen. however i did a complete reboot of the system after that so i have no idea if just the closing and reopening of boinc manager will solve that problem.


I tried that, and it doesn't seem to work. I am running BOINC as a service, so there's a different method for stopping it anyway, according to a thread I found somwhere on the BOINC message boards, but that doesn't work either. If I do stop both the BOINC Manager and the BOINC Core Client, Minirosetta continues to run. The Windows Task Manager shows the minirosetta task hasn't unloaded, and the CPU usage stays at 100%. I could end the Minirosetta process, but I am reluctant to do that.
7) Message boards : Number crunching : Minirosetta v1.40 bug thread (Message 57204)
Posted 24 Nov 2008 by Rob Lilley
Post:
This Minirosetta v1.40 Work Unit is another one that won't suspend and continues running when pre-empted by a QMC WU.

Should I abort the Minirosetta Work Unit or suspend all the other projects that play nice until the Minirosetta WU finishes?
8) Message boards : Number crunching : Boinc 5.8.15 is out and odd (Message 37351)
Posted 4 Mar 2007 by Rob Lilley
Post:
Looks as though they've fixed this in 5.8.16

Thay've also reinstated the tick next to snooze when it's snoozing.
9) Message boards : Number crunching : Problems with rosetta 5.48 (Message 37350)
Posted 4 Mar 2007 by Rob Lilley
Post:
My machine has 512mb of memory too, and I had the same message come up when Rosetta 5.48 appeared.

It seems that in General Preferences you can now determine what percentage of memory (actual not virtual) a project can use. I just increased the percentage to use when the computer is idle from 90 to 95% and it downloaded just fine.

Now let's see what happens when the crunching / fun starts!
10) Message boards : Number crunching : New host ID being created at every connect (Message 17233)
Posted 27 May 2006 by Rob Lilley
Post:
Just a thought...

I have two machines, one with no location set and one with the location set to "work" in order to have one working all the time and the other only when the user is not active. The machine with no location set is not creating new host IDs but the one with the "work" location is.

I originally set the "work" location up on BAM, but it seems not to create a new "work" location on any projects (not just Rosetta) where no "work" location had been set up beforehand. I have now manually created a "work" location on each of the offending projects (Rosetta, LHC and Predictor). However, this doesn't seem to have helped, as "new" host IDs are still being created, but with a location of "home".

Would it help to delete the "work" location and all references to it, and set the location for the second machine to "home" or to no location? I guess that if I wanted to set no location I'd have to either detach that machine from BAM, or else maybe set an unrecognised location for that machine on BAM to stop it resetting back to "home". The first machine was originally set up pre-BAM with no location, and I created a "home" location on BAM, with the result that all projects (including Rosetta) now have a location of "home" with no problems. Hmmmm.....
11) Message boards : Number crunching : New host ID being created at every connect (Message 17180)
Posted 26 May 2006 by Rob Lilley
Post:
Thanks! I don't think we can merge right now in Rosetta though.


True I'm afraid! My machine contacts Rosetta once an hour and creates a new host each time. It's doing the same on LHC, but at least they are allowing us to merge hosts.

Anyone know when the merge facility will be turned back on?






©2021 University of Washington
https://www.bakerlab.org