flyinion
...after letting it sit for a couple hours Friday night when I installed things, it never actually started.

It could be your system is having trouble getting work units (WU) due to the recent influx of volunteers, you can verify by going to the Advanced Control -> Log tab and looking for entries like:
 
21:27:19:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
 
If the client is unable to get a WU, it'll try again, but each time it tries, it'll increase the time. An example with made up numbers: client tries once, it fails, client waits 30 seconds, client tries again, client waits 90 seconds, etc... If this is happening, you can pause the client, then unpause it and it'll reset the timer.
 

I used to try to do the same thing. I got fed up with it never working right & I just leave the Advanced Control panel up and will start/stop it manually.

flyinion

castrator86
I used to try to do the same thing. I got fed up with it never working right & I just leave the Advanced Control panel up and will start/stop it manually.

Yeah I tried resuming the WU by having it set to when idle and it just wouldn't start on its own. Oh well. 

Same.

slurm1
I'm not sure who recommended me for a blue ribbon, but thank you sir, it's my first one!

 
go here:   https://www.evga.com/myevga/

slurm1

flyinion
...after letting it sit for a couple hours Friday night when I installed things, it never actually started.

It could be your system is having trouble getting work units (WU) due to the recent influx of volunteers, you can verify by going to the Advanced Control -> Log tab and looking for entries like:
 
21:27:19:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
 
If the client is unable to get a WU, it'll try again, but each time it tries, it'll increase the time. An example with made up numbers: client tries once, it fails, client waits 30 seconds, client tries again, client waits 90 seconds, etc... If this is happening, you can pause the client, then unpause it and it'll reset the timer.
 

Is there anyway to prevent this, other than manually having to go in there and Pausing it in order to Reset the Timer?
 
It seems to work better by Pausing and then rebooting the computer for some reason.
 
While this may be fine when it comes to say having one system running, but if you have multiple ones, it can be a pain.
 
Finally, how can these big systems seem to get all the WU's vs. everyone else?
 
Thanks!
 
 

ipkha
Pause and start the client is sufficient.
Use sparingly. Say every 4 hours to not contribute to the overload oroblem.

That's fine when it comes to say having just one system, but I have up to four different ones which I have up and running, and which I have to go and move my monitor/keyboard/mouse over to in order to pause and re-start every four (4) hours, which I can't always do.
It would be great if the FAH application had the feature which would go and say ping the server telling it that it is available for some more WU's, or even once a WU has been completed and uploaded, to either immediately have a new WU downloaded or to notify that it was available for the next available one.
 
So it sounds like it's a flaw in the application that needs to be fixed.

Restarting the client only resets the project check timers. Anyone can check the daily chart table here and see the big fat 0's from lack of work units https://folding.extremeoverclocking.com/aggregate_summary.php?s= so restarting the client is far from a guarantee.
 
My personal rig only folds a few hours a day and spends the rest idling. Until Pande Group is able to create sufficient projects to meet demand I'll only be folding occasionally. Just doesn't make sense to leave the system idle nearly all of the day.