I haven't gotten any work units in at least a week now. I've tried resetting the project. I've now got other stuff running instead of Rosetta. I see no news that it's been down. Anything else I can do to figure out why I'm not receiving work units?

Check if you have virtualization enabled, and check if BOINC was installed with vbox.

Some of this information appears near the start of the BOINC log file, if it was started recently enough.

Also, check the server status at:

https://boinc.bakerlab.org/rosetta/server_status.php

The number of available tasks is currently rather low, and it's possible that all of these require different hardware than you have.

Mine was because those machines all produced errors so I had to go to details and hit "Allow" for each one.

---

Mine was because those machines all produced errors so I had to go to details and hit "Allow" for each one.

---

Mine was because those machines all produced errors so I had to go to details and hit "Allow" for each one.

---

The jobs that run forever and use very little CPU power ("0 CPU") are only on Linux that I have found.
They have been around since half the age of the universe, not that anyone at Rosetta is around to care.

As I mention somewhere, they are easy to spot using BoincTask. I just abort them. But they do not seem to be a problem on Windows.

I just had my first 0 CPU job on Win10, so I aborted it. Too bad.
I was going to convert another Ubuntu machine to Windows, but I don't think so. I will wait until they fix it.

---

Is anyone getting any work? I'm not picking up any python tasks at the moment.

I see I'm not the only one! I've been getting work most of the week until now, but the server status shows there should be work available.

I got hit with the same thing.
A load of BS if you ask me.
Any errors is on the RAH team.
I run other VM projects no problems.

The jobs that run forever and use very little CPU power ("0 CPU") are only on Linux that I have found.
They have been around since half the age of the universe, not that anyone at Rosetta is around to care.

As I mention somewhere, they are easy to spot using BoincTask. I just abort them. But they do not seem to be a problem on Windows.

I just had my first 0 CPU job on Win10, so I aborted it. Too bad.
I was going to convert another Ubuntu machine to Windows, but I don't think so. I will wait until they fix it.

I run them in about 4 to 7 hours on my Ryzen 9 3900XT. But one of them got up to 2 days and slowed right down past 99% complete. I aborted it.

I've given up running them on slower machines, I just use the Ryzen and the i5. The others keep going over the deadline.

@dcdc: Thank you for your answer!
In my case, there are ~14 GB free on the disk. That's too little to get additional tasks, I can see entries like this in the syslog:

Dec 30 14:57:40 i5-be-quiet boinc[2340611]: 30-Dec-2021 14:57:40 [Rosetta@home] Sending scheduler request: To fetch work.
Dec 30 14:57:40 i5-be-quiet boinc[2340611]: 30-Dec-2021 14:57:40 [Rosetta@home] Requesting new tasks for CPU
Dec 30 14:57:42 i5-be-quiet boinc[2340611]: 30-Dec-2021 14:57:42 [Rosetta@home] Scheduler request completed: got 0 new tasks
Dec 30 14:57:42 i5-be-quiet boinc[2340611]: 30-Dec-2021 14:57:42 [Rosetta@home] No tasks sent
Dec 30 14:57:42 i5-be-quiet boinc[2340611]: 30-Dec-2021 14:57:42 [Rosetta@home] rosetta python projects needs 5292.79MB more disk space.  You currently have 13780.69 MB available and it needs 19073.49 MB.

I have been getting the `disk space` messages for some time even with 200GBG "free available to boinc"
I have spent a lot of time messing about with the the thing to try and fix it with no affect.
That "19073.49MB" message is always the same size on either system I run, whatever the other `want more` / `have got` variable size (MB) is.
I think it has to be something written into the app itself,
I also have difficulty getting more tasks if the `disk space` message is recently in the event log.

The jobs that run forever and use very little CPU power ("0 CPU") are only on Linux that I have found.
They have been around since half the age of the universe, not that anyone at Rosetta is around to care.

As I mention somewhere, they are easy to spot using BoincTask. I just abort them. But they do not seem to be a problem on Windows.

I just had my first 0 CPU job on Win10, so I aborted it. Too bad.
I was going to convert another Ubuntu machine to Windows, but I don't think so. I will wait until they fix it.

I run them in about 4 to 7 hours on my Ryzen 9 3900XT. But one of them got up to 2 days and slowed right down past 99% complete. I aborted it.

I've given up running them on slower machines, I just use the Ryzen and the i5. The others keep going over the deadline.

Ryzen 7 3700x (auto overclock) takes 4.8 hrs max to chew through Python.

The estimated time of 8 hours was completely unrealistic. I aborted 3 wu from 6 wu. Checkpoints are missing, I do not consider using the virtual box happy. The units below run a second time, the first time after 4 hours and a subsequent restart, the crunching has started again from the beginning.

How come my i5 is running them continuously, but when my Ryzen asks for them It says got no new tasks? There seems to be a continuous supply in server status.

Have you checked on the Ryzen computer's page to see whether the "allow" button is showing? It should say "skip".

---

Duplicate...

---

Have you checked on the Ryzen computer's page to see whether the "allow" button is showing? It should say "skip".

I don't think I can. It's running through gridcoin on grcpool.com.

I assume you're telling me to override some blockage because it's been blacklisted? That would be strange as it processed many many workunits and only 1 was aborted by me when it ran several times longer than normal.

Correction, I found it's ID in client state, but I see no allow or skip.
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=6167614
By the way, there should be about 50 completed tasks in there.

I do see allow on my old page, for when I wasn't in the pool:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3772248

I will attempt to connect it to Rosetta outside the pool to change the button....
No, that failed, I got the other ID.

The odd thing is it used to get them fine, why would that have been disallowed?

And this is weird:
https://boinc.bakerlab.org/rosetta/host_app_versions.php?hostid=6167614
89 tasks completed none valid?
My i5 has completed 100 successfully, and they show there ok.

Ryzen has the latest Vbox - 6.1, the i5 has 5.2. Is there a problem with the new Vbox?

Duplicate...

If you edit your duplicate post and just put two space characters in it, it gets deleted immediately.

Have you checked on the Ryzen computer's page to see whether the "allow" button is showing? It should say "skip".

I don't think I can. It's running through gridcoin on grcpool.com.

I assume you're telling me to override some blockage because it's been blacklisted? That would be strange as it processed many many workunits and only 1 was aborted by me when it ran several times longer than normal.

Could that mean that grcpool.com is blacklisted, rather than your computer? If so, it could be due to other users also using grcpool.com.

Could that mean that grcpool.com is blacklisted, rather than your computer? If so, it could be due to other users also using grcpool.com.

No, my other computer, glass, an i5, also on grcpool, receives them normally. I detached then reattached the offending Ryzen, and it received a huge number of non-Vbox tasks, which means either it's still banned, but only for vbox, or I cleared the ban but the non-vbox tasks just happened to appear at that point (since my i5 then got 50% tasks as non-vbox - however the Ryzen was 100% non-vbox).

I've been a Rosetta@home participant since the beginning. And, never had I had problems getting new WU's . Now, it appears I have to jump
through new hoops? It shouldn't be that difficult. SiDock@home hands out new WU's like candy. Am counting on Dr. Baker to bring back
the good old days.

---

Am counting on Dr. Baker to bring back the good old days.

The Good Old Days were pre-AI (artificial intelligence). The world has changed.
They have not bothered to update us though.

---