For me, what it means is that if I am going to be away from systems for say a few days or longer, I need to have another project ready to do work. I had been pushing work toward Rosetta over the past few months getting a RAC 24K or so, but if I am going to not be able to monitor things that is going to drop back.

1) For whatever reason, reporting gets stalled periodically and requires a manual 'push' -- which then reports 5, 10 or more work units and downloads work units -- this does not happen with any other project.

I have seen that too. I attributed it to the fact that I was coming off a CPDN work unit that took 8 or 9 days to complete, and the BOINC scheduler had not picked up on that yet. But another thought is that the BOINC server version on Rosetta is rather old (it is said), and may not work so well with the latest BOINC clients; I am using 7.6.22 or 7.6.29, depending on the machine.

I have not seen the errors yet, but just started again a week ago, with 40 successes thus far (24 hour runs).

---

@BarryAZ, it would be helpful if you could give some details on what getting stalled means. Are you saying completed work does not get reported? That no new work is requested? or both? What do the messages in the event log say?

Are any of that tasks running "high priority" at the time?

---

Rosetta Moderator: Mod.Sense

Since today (March 8th), around noon UTC, I am experiencing numerous "compute errors". Almost 80% of the tasks are terminated after various time lengths, showing this error.
Has anyone else made the same experience?

I have encountered this issue lately.

:: edit :: The following statement is now false after just after typing this response, my first computation error occurred with an older Boinc client.

I have uninstalled the latest Boinc Client and rolled back to a previous one. No issues now.

Both -- I will need to see if I can get a piece of the event log.

And no, there are no 'high priority' tasks running.

One other piece of information -- when I encounter this, on the status panel for projects, Rosetta reports a 'communication deferred with a LONG wait cycle -- 10 hours or more. Note, this happens on several different workstations and it is a relatively recent occurrence. If I am checking the workstations regularly it isn't that big a deal. But there are times workstations run for days on 'autopilot' and in that case, the Rosetta jobs don't report nor do I get new work.

I noticed that yesterday when I checked -- there were no CPU tasks left to run since I had other projects set with 'no new work'. I've changed that for now.

@BarryAZ, it would be helpful if you could give some details on what getting stalled means. Are you saying completed work does not get reported? That no new work is requested? or both? What do the messages in the event log say?

Are any of that tasks running "high priority" at the time?

---

So, is there anything more here than the server was very low on WUs available to issue earlier in the week? A host hits the scheduler, receives no new work when requested, goes in to lengthy backoff, and if the cache of work on the machine does not exceed the backoff, then the machine goes much of a day without work?

I'm not sure when such lengthy backoffs came in to BOINC Manager, but it would seem that keeping a 2 or 3 day cache of work would help weather periods when the server is backlogged or out of work.

---

Rosetta Moderator: Mod.Sense

So, is there anything more here than the server was very low on WUs available to issue earlier in the week? A host hits the scheduler, receives no new work when requested, goes in to lengthy backoff, and if the cache of work on the machine does not exceed the backoff, then the machine goes much of a day without work?

Very good thought, but the problem was closer to home for me. I had used an app_config.xml to limit the number of ATLAS tasks to 4 at a time. But unfortunately the BOINC scheduler does not know about app_configs, and so it download enough ATLAS tasks for six cores. That left no room for more Rosetta work units, and one core was left empty. I have changed the app_config, will work off the excess ATLAS tasks, and will be back to Rosetta shortly. I have seen this before, but have to learn it again each time it seems.

---

It seems that uploads are stalled -- multiple systems for me.

---

It seems that uploads are stalled -- multiple systems for me.

New database I saw was 270Mb in size. Expect every single person is downloading it over the last day or so. It should ease down shortly. Except the server is currently down for maintenance at this precise moment

On my 6 core Amd:

Rosetta Mini for Android is not available for your type of computer.

---

On my 6 core Amd:

Rosetta Mini for Android is not available for your type of computer.

Yup, I saw that yesterday too

---

I have been trying to get work from Rosetta. Installed new BOINC. Got a few jobs at first but now nothing is downloading.

There have been some issues with large numbers of new hosts coming in to the project. But, at present, it looks like there are plenty of tasks at-the-ready on the server. So, I suspect the automatic retries done in the BOINC Manager have already received some new work.

---

Rosetta Moderator: Mod.Sense

Mine seems to be locking up since Friday 4/22/16. I run both SETI and Rosetta but each time it's locked up, it's been stuck on Rosetta. It's running on an XP machine so I don't know if that's the issue. System logs don't show anything other than events stop happening. I've already uninstalled as well as completely wipe the BOINC folder then reinstalled. I have noticed in Task Manager that Minirosetta has recently been starting itself when I've been using the computer despite my preferences.

Since I haven't seen any other entries on the BOINC/SETI/Rosetta board, I presume that it is this computer or XP. As it stands, I'm going to remove BOINC for awhile since the issues with it just turning itself on while the computer is in use as well as it locking up have become too much to ignore. However, if this is happening to anyone else and they worked around it, feel free to post. I also wasn't sure which thread to post this in so I posted it in the top 2 threads concerning technical problems.

You've broken something, I'm getting this message now on all my Ubuntu rigs.

Fri 29 Apr 2016 12:13:59 AEST | rosetta@home | Sending scheduler request: Requested by user.
Fri 29 Apr 2016 12:13:59 AEST | rosetta@home | Reporting 6 completed tasks, requesting new tasks for CPU
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | Scheduler request completed: got 0 new tasks
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | No work sent
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

---

You've broken something, I'm getting this message now on all my Ubuntu rigs.

Fri 29 Apr 2016 12:13:59 AEST | rosetta@home | Sending scheduler request: Requested by user.
Fri 29 Apr 2016 12:13:59 AEST | rosetta@home | Reporting 6 completed tasks, requesting new tasks for CPU
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | Scheduler request completed: got 0 new tasks
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | No work sent
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Me too, on my Windows 7 machine.

---

All of my pred5csxxxxx w/u's terminate after 2-3 hrs. but show no error.
Is this by design and OK?

I don't want to dump good w/u's for no reason.

good luck with the server work.

/mike

---

If there are no errors, it should be fine.

If there are no errors, it should be fine.

There are errors...

Example

ERROR: Error in simple_cycpep_predict app! The imported native pose has a different number of residues than the sequence provided.
ERROR:: Exit from: src/protocols/cyclic_peptide_predict/SimpleCycpepPredictApplication.cc line: 751
[0x4485e82]
[0x480914]
[0x48925c]
[0x4025d4]
[0x46df0cb]
[0x400429]
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

I have had a persistent problem reporting work. For me, what happens on my systems is that the reporting gets a 'server offline' message from the project. OK that happens when the server is busy -- after all the work units uploading and downloading can be quite large.

What is different with Rosetta though is that when I get one of those reports, my workstation immediately shifts to 'deferred reporting for 24 hours'.

On all the other projects when a report runs into a 'server busy or offline' response, there is a progressive retry cycle starting from a try back in 10 minutes or so up to around 4 hours.

With Rosetta, and only Rosetta, I get the 24 hours defer.

When I go to the workstations to manually push the reports -- they happen every time.

What that means for me is that when I know I won't be available to manually push reports at least once during the day, I essentially end up having to shift to another project for those systems. That's what I do during a vacation away from the systems.

Again, this only happens with Rosetta and not with any of the other many projects I run cycles for.

---

You've broken something, I'm getting this message now on all my Ubuntu rigs.

Fri 29 Apr 2016 12:13:59 AEST | rosetta@home | Sending scheduler request: Requested by user.
Fri 29 Apr 2016 12:13:59 AEST | rosetta@home | Reporting 6 completed tasks, requesting new tasks for CPU
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | Scheduler request completed: got 0 new tasks
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | No work sent
Fri 29 Apr 2016 12:14:04 AEST | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Same here, on my Win7 Ultimate!!

30.04.2016 11:19:55 | rosetta@home | Sending scheduler request: To fetch work.
30.04.2016 11:19:55 | rosetta@home | Requesting new tasks for CPU and NVIDIA GPU and Intel GPU
30.04.2016 11:19:58 | rosetta@home | Scheduler request completed: got 0 new tasks
30.04.2016 11:19:58 | rosetta@home | No work sent
30.04.2016 11:19:58 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

---