Why am I not getting anymore work units?

Why am I not getting anymore work units?

I exit BOINC then wait a few minutes and then restart BOINC... still no new work units. I had to exit BOINC then reboot my PC and then restart BOINC to get new work units. Does Rosetta@Home have a bug that prevents getting new work units after a certain period of time?

Why am I not getting anymore work units?

I exit BOINC then wait a few minutes and then restart BOINC... still no new work units. I had to exit BOINC then reboot my PC and then restart BOINC to get new work units. Does Rosetta@Home have a bug that prevents getting new work units after a certain period of time?

BOINC controls getting tasks. There might be a server-side timeout but it shouldn't be noticable under normal circumstances (i.e. you've returned valid results for work collected).

D

---

My boxes are also not able to get any work units, if I try to manually get new tasks, they go into 24hour back-offs.. here's what the event log says

3/7/2016 10:59:46 AM | rosetta@home | update requested by user
3/7/2016 10:59:48 AM | rosetta@home | Sending scheduler request: Requested by user.
3/7/2016 10:59:48 AM | rosetta@home | Reporting 16 completed tasks
3/7/2016 10:59:48 AM | rosetta@home | Requesting new tasks for CPU
3/7/2016 10:59:50 AM | rosetta@home | Scheduler request completed: got 0 new tasks
3/7/2016 10:59:50 AM | rosetta@home | No work sent
3/7/2016 10:59:50 AM | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

... it then goes into 24 hour project backoff. I've repointed my boxes to Mapping Cancer Markers (World Community Grid) in the meantime.

---

**38 cores crunching for R@H on behalf of cancercomputer.org - a non-profit supporting High Performance Computing in Cancer Research

My boxes are also not able to get any work units, if I try to manually get new tasks, they go into 24hour back-offs.. here's what the event log says

3/7/2016 10:59:46 AM | rosetta@home | update requested by user
3/7/2016 10:59:48 AM | rosetta@home | Sending scheduler request: Requested by user.
3/7/2016 10:59:48 AM | rosetta@home | Reporting 16 completed tasks
3/7/2016 10:59:48 AM | rosetta@home | Requesting new tasks for CPU
3/7/2016 10:59:50 AM | rosetta@home | Scheduler request completed: got 0 new tasks
3/7/2016 10:59:50 AM | rosetta@home | No work sent
3/7/2016 10:59:50 AM | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

... it then goes into 24 hour project backoff. I've repointed my boxes to Mapping Cancer Markers (World Community Grid) in the meantime.

I have several machines with much the same story.
Someone let the children play with the key to the Rosetta job dispatcher. 8-)

I have several machines with much the same story.
Someone let the children play with the key to the Rosetta job dispatcher. 8-)

:) I saw high project TFLOPS yesterday, and no tasks available on my own system this morning. Looks like tasks are coming in now and being sent out, but the sometimes gets flooded with requests after work is exhausted. So getting new work may still be a bit hit and miss over the next couple of hours.

---

Rosetta Moderator: Mod.Sense

Your daily quota is reduced by one for each failed task and it is possible that you could run out of work while the server refuses to send you more until the next "day" starts. If that were the case you should have seen (before you restarted the computer) a message in the event log indicating as much. Something like, "You have reached your daily quota of x (number of) tasks". We can't see your task list since your computers are hidden so I have no idea if this theory has merit in your case.

There is another possibility. Both of my computers received 24 hour backs after a single request for work resulted in this reply:

Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

When I noticed the problem several hours after the back-off began I simply hit the update button and successfully retrieved new tasks.

Steve, no one on the forum has access to your task list or your event log; we only have your forum post to go by. If you don't know how to access the information via your BOINC Manager post back with your OS and your BOINC version number (if you know it) and hopefully someone will be able to walk you through it.

There has been a few mentions of this "Rosetta Mini for Android is not available for your type of computer." back-off so I've posted a further response in the Minirosetta 3.71 thread

Best,
Snags

edit: I see several others have posted since I started thinking about my reply (and posted in the other thread) : ) Did they actually run out of cpu tasks?

Did they actually run out of cpu tasks?

Yes, appears there was a surge of new hosts added over the weekend and available CPU tasks either was very low, or exhausted for some period of time.

Looks like we are now up to 50,000 available, which is the normal level, implying the servers have now caught up to much of the demand for new tasks.

---

Rosetta Moderator: Mod.Sense

Did they actually run out of cpu tasks?

Yes, appears there was a surge of new hosts added over the weekend and available CPU tasks either was very low, or exhausted for some period of time.

Looks like we are now up to 50,000 available, which is the normal level, implying the servers have now caught up to much of the demand for new tasks.

Rosetta communication for my machines is only deferred by 21 hours.
I will pickup more work .... tomorrow.

Any thoughts why Rosetta thinks machines are Android? Rosetta told me this in response to Windows 8.1 and Linux 32-bit and 64-bit machines (Fedora and Ubuntu)?

Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Mine said that too. Can only speculate that there were only Android WUs left in the scheduler cache. And so this is really more an indication of why you got no work, than the server thinking your machine was Android.

---

Rosetta Moderator: Mod.Sense

Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Mine said that too. Can only speculate that there were only Android WUs left in the scheduler cache. And so this is really more an indication of why you got no work, than the server thinking your machine was Android.

If I see no "Ready to start" tasks, I simply close BOINC and reboot PC. Then weh BOINC runs again, it loads up a set of tasks read to start. Closing BOINC and restarting without a reboot appears not to work.

Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Mine said that too. Can only speculate that there were only Android WUs left in the scheduler cache. And so this is really more an indication of why you got no work, than the server thinking your machine was Android.

I suspect that Rosetta is confused because I cannot seem to assign different IP addresses to VM machines. I would hope that Rosetta uses more than just IP address to distinguish a machine.


State Approximate #results
Ready to send 39,696
In progress 984,500



Mon 07 Mar 2016 08:21:14 AM PST | | cc_config.xml not found - using defaults
Mon 07 Mar 2016 08:21:14 AM PST | | Starting BOINC client version 7.2.42 for x86_64-pc-linux-gnu
Mon 07 Mar 2016 08:21:14 AM PST | | log flags: file_xfer, sched_ops, task
Mon 07 Mar 2016 08:21:14 AM PST | | Libraries: libcurl/7.43.0 NSS/3.22 Basic ECC zlib/1.2.8 libidn/1.32 libssh2/1.6.0 nghttp2/1.7.1
Mon 07 Mar 2016 08:21:14 AM PST | | Data directory: /var/lib/boinc
Mon 07 Mar 2016 08:21:14 AM PST | | No usable GPUs found
Mon 07 Mar 2016 08:21:14 AM PST | | Using state file client_state_next.xml
Mon 07 Mar 2016 08:21:14 AM PST | | Host name: saberfed2364
Mon 07 Mar 2016 08:21:14 AM PST | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU X7560 @ 2.27GHz [Family 6 Model 46 Stepping 6]
Mon 07 Mar 2016 08:21:14 AM PST | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc pni ssse3 sse4_1 sse4_2 lahf_lm
Mon 07 Mar 2016 08:21:14 AM PST | | OS: Linux: 4.4.3-300.fc23.x86_64
Mon 07 Mar 2016 08:21:14 AM PST | | Memory: 31.42 GB physical, 1.80 GB virtual
Mon 07 Mar 2016 08:21:14 AM PST | | Disk: 15.34 GB total, 6.65 GB free
Mon 07 Mar 2016 08:21:14 AM PST | | Local time is UTC -8 hours
Mon 07 Mar 2016 08:21:14 AM PST | rosetta@home | URL https://boinc.bakerlab.org/rosetta/; Computer ID 2476156; resource share 20
Mon 07 Mar 2016 08:21:14 AM PST | | Reading preferences override file
Mon 07 Mar 2016 08:21:14 AM PST | | Preferences:
Mon 07 Mar 2016 08:21:14 AM PST | | max memory usage when active: 28958.07MB
Mon 07 Mar 2016 08:21:14 AM PST | | max memory usage when idle: 28958.07MB
Mon 07 Mar 2016 08:21:14 AM PST | | max disk usage: 4.57GB
Mon 07 Mar 2016 08:21:14 AM PST | | (to change preferences, visit a project web site or select Preferences in the Manager)
Mon 07 Mar 2016 08:21:14 AM PST | | Using proxy info from GUI
Mon 07 Mar 2016 08:21:14 AM PST | | Using HTTP proxy http://www-proxy.us.oracle.com:80
Mon 07 Mar 2016 08:21:43 AM PST | rosetta@home | Sending scheduler request: To fetch work.
Mon 07 Mar 2016 08:21:43 AM PST | rosetta@home | Reporting 2 completed tasks
Mon 07 Mar 2016 08:21:43 AM PST | rosetta@home | Requesting new tasks for CPU
Mon 07 Mar 2016 08:21:46 AM PST | rosetta@home | Scheduler request completed: got 0 new tasks
Mon 07 Mar 2016 08:21:46 AM PST | rosetta@home | No work sent
Mon 07 Mar 2016 08:21:46 AM PST | rosetta@home | Rosetta Mini for Android is not available for your type of computer.
Mon 07 Mar 2016 11:28:05 AM PST | rosetta@home | Computation for task rb_03_07_63547_107681__t000__0_C1_SAVE_ALL_OUT_IGNORE_THE_REST_331455_398_0 finished
Mon 07 Mar 2016 11:28:07 AM PST | rosetta@home | Started upload of rb_03_07_63547_107681__t000__0_C1_SAVE_ALL_OUT_IGNORE_THE_REST_331455_398_0_0
Mon 07 Mar 2016 11:28:10 AM PST | rosetta@home | Finished upload of rb_03_07_63547_107681__t000__0_C1_SAVE_ALL_OUT_IGNORE_THE_REST_331455_398_0_0
Mon 07 Mar 2016 11:39:45 AM PST | rosetta@home | Computation for task rb_03_07_63547_107681__t000__0_C1_SAVE_ALL_OUT_IGNORE_THE_REST_331455_439_0 finished





Tue 08 Mar 2016 07:15:57 AM PST | rosetta@home | Finished upload of rb_03_07_63355_107705_ab_stage0_t000___robetta_IGNORE_THE_REST_04_09_331500_24_0_0
Tue 08 Mar 2016 07:17:27 AM PST | rosetta@home | update requested by user
Tue 08 Mar 2016 07:17:28 AM PST | rosetta@home | Sending scheduler request: Requested by user.
Tue 08 Mar 2016 07:17:28 AM PST | rosetta@home | Reporting 3 completed tasks
Tue 08 Mar 2016 07:17:28 AM PST | rosetta@home | Requesting new tasks for CPU
Tue 08 Mar 2016 07:17:30 AM PST | rosetta@home | Scheduler request completed: got 0 new tasks
Tue 08 Mar 2016 07:17:30 AM PST | rosetta@home | No work sent
Tue 08 Mar 2016 07:17:30 AM PST | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Only just noticed this. I've got a few tasks left so I'm increasing runtime to eke them out until this is resolved.

---

I've also run into this issue... (No work sent/Rosetta mini for android not available for you type of computer/24hr back off) on some of my setups over the last few days. Yesterday I was able to get them cleared out and the work units coming in again but not much luck today. All my setups are running W7 and W10. I've gone ahead and switched over one out of work rig to WCG. If problem persists I'll switch over others as they continue to run out of work.

Only just noticed this. I've got a few tasks left so I'm increasing runtime to eke them out until this is resolved.

It may already be too late. After you get the "Android" message, the machine backs off 24 hours. I was able to manually update after "some period of time" and the 24 hours was changed to ~4 minutes.

computer 2341353
Windows 8.1, 24gb memory, free disk space 500gb,


State
Approximate #results

Ready to send 39,240
In progress 939,764

3/8/2016 8:56:01 AM | rosetta@home | Starting task tj_2_18_insert_X_DHR49_DHR81_l3_h21_l3_0_v8_fragments_abinitio_SAVE_ALL_OUT_329586_921_0
3/8/2016 8:56:02 AM | rosetta@home | Starting task FFF_d960105a16ebad478cc31a550593296e_b895FFdesBakL_p2of2_Wed_Feb_10_14_14_37_PST_2016_0000419_abinitio_SAVE_ALL_OUT_327296_134_0
3/8/2016 8:56:03 AM | rosetta@home | Starting task tj_2_18_insert_X_DHR53_DHR14_l3_h14_l2_0_v8_fragments_abinitio_SAVE_ALL_OUT_329859_788_0
3/8/2016 8:56:06 AM | rosetta@home | Starting task NTF2_2373_E79Q16E117_5_2_2_impSS_fold_SAVE_ALL_OUT_330866_843_0
3/8/2016 8:56:12 AM | rosetta@home | Sending scheduler request: To fetch work.
3/8/2016 8:56:12 AM | rosetta@home | Reporting 1 completed tasks
3/8/2016 8:56:12 AM | rosetta@home | Requesting new tasks for CPU and NVIDIA GPU
3/8/2016 8:56:14 AM | rosetta@home | Scheduler request completed: got 0 new tasks
3/8/2016 8:56:14 AM | rosetta@home | No work sent
3/8/2016 8:56:14 AM | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

No new work here too. It is going on for about a week now. All tasks ready and then not reported or new work.
Do a manual Update helps sometimes.
Now it says: Communication deferred 23:55:55 so a whole day.
This happened to me two times earlier in the last week or so.
So the project won't my computers anymore.

---

Greetings,
TJ.

I've also run into this issue... (No work sent/Rosetta mini for android not available for you type of computer/24hr back off) on some of my setups over the last few days. Yesterday I was able to get them cleared out and the work units coming in again but not much luck today. All my setups are running W7 and W10. I've gone ahead and switched over one out of work rig to WCG. If problem persists I'll switch over others as they continue to run out of work.

Well it looks like more work units have now come in this afternoon... I've gone ahead and tweaked/increased my work buffer preferences for my setups. Hopefully a little greater backlog on the machines will help smooth things out moving forward.

I've also run into this issue... (No work sent/Rosetta mini for android not available for you type of computer/24hr back off) on some of my setups over the last few days. Yesterday I was able to get them cleared out and the work units coming in again but not much luck today. All my setups are running W7 and W10. I've gone ahead and switched over one out of work rig to WCG. If problem persists I'll switch over others as they continue to run out of work.

Well it looks like more work units have now come in this afternoon... I've gone ahead and tweaked/increased my work buffer preferences for my setups. Hopefully a little greater backlog on the machines will help smooth things out moving forward.

Just as well I forgot to do what I said I was going to do because I've now had 18 tasks come down in 4 lots over the last 7 hours and my buffer looks like it's filled up again.

Probably worth monitoring over the next few days, just in case it's a temporary fix, but looks fine at this precise moment.

---

Hi.
I've not received any task since Feb. 15.

Hi.
I've not received any task since Feb. 15.

16 Mar 2016 10:18:03 UTC
name A3U8D3_PF16267_30-170_EN_MAP_hyb_cst_v02_t000__krypton_SAVE_ALL_OUT_03_09_336360_167

It looks like you got a workload for one of your machines about 35 minutes after posting this. I have encountered problems with the BOINC disk configuration settings on a couple of my virtual machines.



There are 3 different disk settings that ALL need to be met.
1. USE NO MORE THAN XXX GB
2. LEAVE AT LEAST YYY GB free
3. USE NO MORE THAN ZZ % of total


All 3 requirements need to be met or a machine will not be allocated work.

Check the COMPUTING PREFERENCES tab of the BOINC OPTIONS tab to make sure there is enough disk. Rosetta will be complaining about lack of space in the EVENT LOG about disk space.