What's with the Rosetta Mini 1.03 app? Crashed once, made boinc and boincmgr nonresponsive. Boinc isn't a service on this box so I logged out/in to restart. It restarted this task with high priority, according to the client, but nothing was running and boinc was again stalled.
I had to edit client_state.xml to force the project suspended to get the client running again.

This happened on 2 different pc's before I caught it. The cash dialogue comes up about 19 seconds into the wu.
Clients are 5.10.20

me too

Caught me on BOINC 5.10.30 too!

On the first pc mentioned before, BOINC stopped responding sometime overnight and I had to kill it and the boincmgr. Now boinc won't come up. The process appears but the manager can't connect. Hope that doesn't happen to others.

-- Edit: just happened to the 2nd pc also. Must leave the house for much of the day so I don't know what's going on, client_state.xml looks fine, tried rebooting and reinstalling on one of the pc's, this is not a happy crunching day.

Its also halting version 5.10.35. I've suspended it for now.

---

Finally cleaned up after this mess. Make sure nothing is left from the mini app in one of your slots dirs, or you will have a broken boinc (possibly much later) in your future.

Please let us know when we can "go back in the water" without these wus showing up. Thanks

Someone has posted at RALPH@home bug list / Rosetta Min 1.03 basically the same experience.

---

It should be enough to remove the "..Boincslots2minirosetta_database" tree, everything should be fine afterwards. (OK, if there are no uncrunched rosetta_minis in your Boinc tree anymore :-)

Peter

We are looking into this bug. We will have to send out more work units to help debug. Sorry for the troubles.

---

The saga continues in RALPH@home bug list / Rosetta Min 1.03 thread...

Peter

There was a message on the BOINC Alpha mailing list. It appears that this is due to a strange interaction with Mini and BOINC. Particularly, the previously mentioned tree has some files that are read only (SVN files). When BOINC fails to delete them, it assumes that it has been locked by another process (One that will release shortly) and tries to delete it again. They have put in a fix for Version 6, and Dr Anderson has requested that it be ported back to 5.10.x.

Of course if it was possible to remove those files from the archive, or remove the read only attribute, that would also solve the problem.

I currently have a mini working, I have removed the read only attribute from the whole tree, I will try and post again when it finishes, as to success or failure.

---

This signiture stolen from somewhere.

We are looking into this bug. We will have to send out more work units to help debug. Sorry for the troubles.

Don't SEND OUT more WU's of this. It locks up the system. Rosetta and RALPH are bothe suspended for now until I see that this is fixed in this forum and the BOINCalpha forums.

Fix this internally FIRST.

EDIT: never mind. Ii see that in another thread that David A is aware and has a fix. But WHY were these files included in the system anyway?

Don't SEND OUT more WU's of this. It locks up the system.

Does it really? How exactly? If, then something else must bee happening too. Can you please explain? Noone except me mentioned such system behavior.

Ii see that in another thread that David A is aware and has a fix. But WHY were these files included in the system anyway?

You have read it yourself: by accident.

Peter

One thing is not clear to me...

Is this really a windows-only problem? If we are talking about read-only files unable to be deleted, doesn't that hit all OS?

---

Reno, NV
Team: SETI.USA

Is this really a windows-only problem? If we are talking about read-only files unable to be deleted, doesn't that hit all OS?

I think it should pertain to all Boinc versions. Except it did not :-)

What does your Mac say to Rosetta mini?

Possibly the reason is a rather small count of non-Windows hosts to receive AND notice such problematic WU?

Peter

What does your Mac say to Rosetta mini?

Nothing yet. It has not yet started.

---

Reno, NV
Team: SETI.USA

Installed BOINC 5.10.38 on a system (Windows XP) that has been seeing the Rosetta mini "lock-up". The work unit that was running did fail at completion but BOINC didn't exhibit the previously seen problems.

The specific error with Rosetta mini was:
1/17/2008 11:17:46 AM|ralph@home|Computation for task mini_abrelax-1scjB-test_james_2847_3_1 finished
1/17/2008 11:17:46 AM|ralph@home|Output file mini_abrelax-1scjB-test_james_2847_3_1_0 for task mini_abrelax-1scjB-test_james_2847_3_1 absent

Note that I had not changed attributes on any files in the slots directory.

I don't have any Rosetta mini work queued and Ralph currently doesn't have any work for this system so I can't tell if the problem seen will reoccur or if it was an outgrowth of all the terminating of BOINC I forced to do when BOINC would stall.

Just had one lock up on my Intel Core Duo Mac running OSX 10.4.11 and Boinc 5.10.34