flyinion...after letting it sit for a couple hours Friday night when I installed things, it never actually started.
slurm1flyinion...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 '184.108.40.206: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.
castrator86I 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.
flyinioncastrator86I 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.
slurm1I'm not sure who recommended me for a blue ribbon, but thank you sir, it's my first one!
ipkhaPause and start the client is sufficient. Use sparingly. Say every 4 hours to not contribute to the overload oroblem.