I recently put Rosetta onto a ubuntu machine using the boinc version from synaptic. However, 4 of the 5 WUs that it has actually run so far have ended with a client error giving "process exited with code 193 (0xc1)". The machine in question is here: https://boinc.bakerlab.org/rosetta/results.php?hostid=584624

I searched the forums for other people getting this error, but the only posts were from about a month ago and no actual solution I could see. Could the version of boinc I have be wrong, or does anybody have any ideas.

I have paused rosetta on there for now and let it run other projects, seti and Einstein, both of which are running fine and returning good WUs.

Not sure what causes this issue, but it seems most common on Linux boxes.

Looking at your host, I see you are running 5.4.9 BOINC? So I'd suggest you start there, and get up to the current stable release 5.8 and see if that helps.

---

Rosetta Moderator: Mod.Sense

I updated my client version to 5.8.16, and the same thing happened with the first 2 WUs it processed:
https://boinc.bakerlab.org/rosetta/result.php?resultid=101443749 and https://boinc.bakerlab.org/rosetta/result.php?resultid=101442357

The problem seems to occur after 1 hour into computation when boinc tries to pause the WU and start a different project, so I'll try running just rosetta for a while and see if that works, unless anybody has a better idea?

Just running rosetta seemed to make the WUs complete successfully, as did setting rosetta to leave the applications in the memory when suspended. Neither of these is exactly ideal. Has anybody got any other suggestions?

Just running rosetta seemed to make the WUs complete successfully, as did setting rosetta to leave the applications in the memory when suspended. Neither of these is exactly ideal. Has anybody got any other suggestions?

Yeah, I had this exact problem if leave applications in memory = no. They haven't fixed it yet. It pisses me off that the R@H application doesn't uninitialize properly as all other projects do. I guess it doesn't use checkpoints properly or something.

What you could help is the switching applications behavior of BOINC. Set your Rosetta Target CPU Run Time to 2 hours and set your global preference Switch Between Applications to 2 hours (the same value or higher). That way it won't switch while Rosetta is working.

Add me and my Linux-Box to the list of affected machines ;-)

Regards
Andy

I have the same problem on my linux machine, but it is not consistent.
Some WUs finish without problems, but others, after running fine for a while, just sit around doing nothinig, until they error out eventually with error 139.
This is a dual core AMD machine and the error makes one core sit completely idle.

---

After some system update (Debian x64) all new WU's ends with exit code 193 https://boinc.bakerlab.org/result.php?resultid=993426232.
How it happens: WU download ends, computation starts and after few seconds finish with computation error. Event log says that output file ___ for task ___ absent.
All previously started WU's was finished fine.

Additional information:
This behavior was with Rosetta 4.07 WU's.
Today WU's for Rosetta Mini starts fine but some time later BOINC lose connection and now there is no project in project list and no possibility to add it.

I can confirm this problem.
Running Debian-Testing.
Seems like others have got the same problem.
https://boinc.bakerlab.org/rosetta/forum_thread.php?id=12242&postid=88775#88775

Just a confirmation from my side. The problem seem to be with Rosetta 4.0x WUs and on Debian 10 (aka "testing", "buster"). I have had the issue on various machines, re-install doesn't help either. BOINC and other BOINC projects are working fine.

Update: The latest Ubuntu 18.04 is affected too (definitely kubuntu 18.04).

Rosetta Mini works fine. Rosetta 4.07 still generates computation errors.
Debian GNU/Linux testing (buster) [4.16.0-2-amd64|libc 2.27 (Debian GLIBC 2.27-3)]
BOINC 7.10.2

Same here. Sometimes (but very seldom) it finishes Rosetta 4.07 tasks complete without error but 90% of them have status "Error while computing". But there is no problem with Rosetta Mini. Is there any way to switch to Rosetta mini only tasks?

My system is Ubuntu Server 16.04