latest version according to BOINC D/Load page is BOINC 5.8.9.which is a 'Development version - may be unstable use only for testing'. is this info out of date?

That is the BOINC client version and though increments at the same rate as the server versions the 5.9.2 is not released to testing (client) BUT server versions are always considered current and release as they have gone through testing and will more than likely be deployed at seti@home already.
The client needs a lot more testing before an official release.

Confusing, yep but not when you know what happens.

---

Team mauisun.org

Running boinc on a Mac (dual 2g) with plenty of memory and drive space.

I have been getting Rosetta jobs recently (past 2-3 months) that get part way through and then just stop.

I have had to abort them to get them out of the queue, as no other manner of suspend, resume, reboot, etc seems to work.

Please let me know if there is a problem that I should be aware of or if I need to upgrade, etc.

Thanks!

---

If you can post a link to any of the problematic workunits, it will be much easier for us to track down what had happened. Thanks. BTW, since the server update just happend less than one week ago, the problem you have experienced might only be relevant to Rosetta application, if so, please report it here

Running boinc on a Mac (dual 2g) with plenty of memory and drive space.

I have been getting Rosetta jobs recently (past 2-3 months) that get part way through and then just stop.

I have had to abort them to get them out of the queue, as no other manner of suspend, resume, reboot, etc seems to work.

Please let me know if there is a problem that I should be aware of or if I need to upgrade, etc.

Thanks!

---

Running boinc on a Mac (dual 2g) with plenty of memory and drive space.

I have been getting Rosetta jobs recently (past 2-3 months) that get part way through and then just stop.

I have had to abort them to get them out of the queue, as no other manner of suspend, resume, reboot, etc seems to work.

Please let me know if there is a problem that I should be aware of or if I need to upgrade, etc.

Thanks!

You need to unhide your computer (see the FAQ's as to why you should do that) so we can look at them. It could be a Rosetta problem, it could be a problem with memory settings kicking in with 5.8.8, it could be ....

---

Team mauisun.org

08/02/2007 12:04:12|rosetta@home|Reporting 1 tasks
08/02/2007 12:04:14||Project communication failed: attempting access to reference site
08/02/2007 12:04:15||Access to reference site succeeded - project servers may be temporarily down.
08/02/2007 12:04:17|rosetta@home|Scheduler request failed: Transferred a partial file
08/02/2007 12:04:17|rosetta@home|Deferring scheduler requests for 1 minutes and 0 seconds
08/02/2007 12:05:17|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
08/02/2007 12:05:17|rosetta@home|Reporting 1 tasks
08/02/2007 12:05:22|rosetta@home|Scheduler request succeeded
08/02/2007 12:05:22|rosetta@home|Message from server: Completed result 1bq9A_BOINC_NOFILTERS_ABRELAX_SAVE_ALL_OUT_NEWRELAXFLAGS_frags83__1505_10737_1 refused: result already reported as success
08/02/2007 12:17:37||Rescheduling CPU: application exited

Hi

Any explanation as to the above please? Looks like I lost three hours of computation due to an issue at the server end on uploading. It was rejected on second load but the first load had failed.

Thanks

---

David, using the internet to communicate between computers is a lot like communicating with your wife (or anyone else). You THINK sometimes that she didn't hear you, but later see evidence that she did. TCP sends acknowledgements of every transmission. Sometimes the transmission is received but the acknowledgement doesn't reach the sender, and so the sender doesn't think the data was "heard". So, your PC took steps to retry the transmission. When this transmission did reach the server, the server's response DID reach you this time, and indicate it already received the report you had sent.

There should not have been any credit (work) lost here, as this was just the "report" portion of the process. The WU results were sent prior to the messages you've shown.

If you'd provide a link to the result page for that one (or unhide your computers), the project team might have more information.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

David, using the internet to communicate between computers is a lot like communicating with your wife (or anyone else). You THINK sometimes that she didn't hear you, but later see evidence that she did. TCP sends acknowledgements of every transmission. Sometimes the transmission is received but the acknowledgement doesn't reach the sender, and so the sender doesn't think the data was "heard". So, your PC took steps to retry the transmission. When this transmission did reach the server, the server's response DID reach you this time, and indicate it already received the report you had sent.

There should not have been any credit (work) lost here, as this was just the "report" portion of the process. The WU results were sent prior to the messages you've shown.

If you'd provide a link to the result page for that one (or unhide your computers), the project team might have more information.

Hi

How can I translate the name in the log to the actual Result ID?

Edit >> found it via time stamp. Looks like credit was granted. Thanks for the explanation.