My dual Opteron 64bit Linux system (Ubuntu 7.04) is not receiving any work. It keeps requesting, but not getting anything. If I can help you out with additional information, please reply and say so :)

Regards,
BorkesComputers

In the output from my first successful result, from version 5.63, SEARCH_PAIRINGS_-1dhn_-round2_1976_120 I see:

Rosetta score is stuck or going too long. Watchdog is ending the run!
CPU time: 14813 seconds. Greater than 4X preferred time: 3600 seconds

Does this mean I should increase my preferred run-length? (At the moment I’ve left the project preferences at their default settings.) BOINC’s initial to-completion estimate was something like 24 hours. Are these messages fairly common here, or might this be indicative of a problem?

1. the cpu time & progress looks good, but the time to completion is meaningless.
the time allowed is 2H but the To completion shows 5H with 5% done

2. I closed BOINC manager (right click - exit) via the task bar icon, at about 7% & 12min then reloaded BOINC, but the running task started from 0 CPU time & 0% Progress, so it lost any results that should have been saved?

save to disk is set to 120sec.

Anders n, I think the behavior you observe is partly due to an additional "correction" that the BOINC API applies when estimating time to completion -- it should never really be over 4 hours, right? We really don't have any control over that extra "correction".

But we do have control over percent complete, and that shouldn't go to zero upon resuming ralph! So I'm still worried. On my mac intel machine, I just tried to suspend a ralph WU, and ran einstein@home for a few minutes; then suspended the einstein@home workunit, and resumed the ralph WU. Everything was fine (pct complete never dropped to zero)... when you try this, does pct complete drop to zero?

[edit]
Another question: you posted that 5.57 was fine; are you seeing an issue only with 5.58? If so, this is totally puzzling, since the small change I made to the Mac app shouldn't affect behacior of pct complete.

OK, just talked to David K about this. Right now we keep track of time crunched based on a call to the BOINC API ... i.e. the BOINC manager keeps track of how much time was spent on each workunit. If you preempt after an hour and resume later, the BOINC manager will tell Rosetta about the hour already spent.

But if you shut BOINC down and restart that could cause a problem in a lot of estimates... we can try to make the Rosetta app more self-sufficient, keeping track of cpu time spent so far, but that might be a can of worms. Worth the time?

Just so we have all the facts right. When a Ralph Wu 5.58 is resumed after preemt the % done goes back to 0 and time to complete goes very high.
I just had one it preemted at 2 H and when restarted time to complete was
at nearly 6 H (rapidly going down as % was going up). I have a 4 H setting for
Ralph on that computer.

Anders n

OK, just talked to David K about this. Right now we keep track of time crunched based on a call to the BOINC API ... i.e. the BOINC manager keeps track of how much time was spent on each workunit. If you preempt after an hour and resume later, the BOINC manager will tell Rosetta about the hour already spent.

But if you shut BOINC down and restart that could cause a problem in a lot of estimates... we can try to make the Rosetta app more self-sufficient, keeping track of cpu time spent so far, but that might be a can of worms. Worth the time?

Anders n, actually, wait, when did this start happening for you? Is there a discussion thread on this?

I haven't been able to reproduce the Mac issue (process not found) noted on the R@H message boards yet. But I'm hoping to find a fix for the next update

How about the other MAC issue where Ralph/Rosetta hangs after beening preemted and then resumed.
I just checked my MAC and 1 WU on each project was hanging.

Anders n

I haven't been able to reproduce the Mac issue (process not found) noted on the R@H message boards yet. But I'm hoping to find a fix for the next update