Please reset host ID 150. It is not getting new tasks with error "Not accepting requests from this host." It had a 100 day old task to report, (I assume you've been down for months because I've only just seen new tasks on my other machines), maybe the old task annoyed your server? I have tried detaching and reattaching the project.

Same for my host ID=66.

I don't know why is ban.

My others hosts work fine.

Kali.

I have resetted hosts 66 and 150.

I have resetted hosts 66 and 150.

Thank You.

Kali.

@Nikolay - please reset host 126. And can this problem be fixed so we don't have to keep getting to reset them?

I have resetted host 126

Thankyou. What is causing this, can you fix it?

I have restarted the scheduling algorithms for node 126. It has now started receiving tasks and calculating them successfully.

This host has to been able to get tasks csince November of last year. I am guessing it is because it's been banned. Can it please be un-banned?

https://uspex-at-home.ru/prediction/show_host_detail.php?hostid=83

Nikolay,

I have a new host, that I added recently. For some reason, it cannot get any work, even though there is plenty available. I am not sure if the host is maybe banned? Or maybe something else? I have never seen this error before. FWIW, I have tried detaching and reattaching.

https://uspex-at-home.ru/prediction/show_host_detail.php?hostid=381

prediction 4/21/2025 11:28:20 AM [sched_op] CPU work request: 61273.65 seconds; 32.00 devices
prediction 4/21/2025 11:28:20 AM [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
prediction 4/21/2025 11:28:20 AM [sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices
prediction 4/21/2025 11:28:24 AM Scheduler request to url failed: Couldn't resolve host name

Thanks!

Dear, Zombie67[MM]!

We very rarely use temporary blocking for those nodes that give continuous errors.
This is done primarily to save the resource of the nodes themselves. That is, so that the nodes do not do unnecessary work. After some time, the nodes are unblocked again if the problem is fixed.

However, node 381 is not blocked. The problem is somewhere else. Perhaps the reason is disabled hardware virtualization in BIOS/UEFI.

Host 121 is banned. Can you please unban it.

And please, tell me why this is happening and if either you or me can do something to stop this happening. It's only noticeable if I happen to look at the messages log, as I run other projects and nothing looks wrong if it isn't running this one.

Host 380 also needs unbanning.