SandyG wrote: ↑Sat Sep 16, 2023 12:18 am
I have not seen many of these for a while, but did see one yesterday.
One thing I found was the back off on retry can get long. If you have the webUI up, stop processing, wait a bit for it to really stop, then restart. I think that causes the retry mechanism to start over. The down side is that you have to be watching it to know it stalled in the first place.
Still other issues with the system going on I fear...
Yeah, sometimes, hitting pause and letting it "wait" for a few hours then starting it again does work. Sometimes, it doesn't. Restarting F@H is usually a faster way, but it's not failproof as it's dependant on having avaiable WU by the time your PC tries looking for one.
As per Joe_H comment and seeing a suggestion there (or should a say, the possibility to test a theory), I moved two of my "problematic and easily movable" PC around and put them in another building with two different ISP. The exact same thing happens and they stop looking for a new WU after the servers tell there is no WU available.
It really happens once there are no WU available for a particular model range for a few minutes. If you happen to try to download a WU in that timeframe, and if no WU becomes available within the next 2-3 tries, it will hang there. Maybe this is something "Windows" related or all ISP do that around here, even those that worked just fine on that end over the past few years.
In the last few days, it's been way more common on my RX 6000 cards than on the Nvidia ones (all of my AMD rigs will stop at one point during the day). On the Nvidia side, I've seen it once or twice with a RTX 3090 and once with a RTX 3080.
I guess that the only reason I see that more often now is that there are less WU available for AMD RX 6000 cards. There's a lot of 0x22 jobs available at all times, but these must be for either Nvidia cards or other AMD models.
I'll just have to babysit the AMD rigs