March 20, 20206 yr Application Name: Folding@home Application Site: https://foldingathome.org/ Docker Hub: https://hub.docker.com/r/linuxserver/foldingathome/ Github: https://github.com/linuxserver/docker-foldingathome Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support.
March 20, 20206 yr This one doesn't require any manual edits to the config.xml. By default, both the web gui and remote access via FAHControl on a different device allow all connections and there is no password. The built-in webserver provides very basic control (ie. GPUs are only active when set to Medium or higher) and its cache management is very finicky. If you have issues connecting, try an incognito window. For more fine grained control of individual devices, you can use the FAHControl app on a different device and connect remotely via port 36330 (no password).
March 20, 20206 yr The web gui is a bit finnicky and refuses to open for me in a regular chrome window (perhaps a conflict with cookies?). I can open it in an incognito window, though. Just fyi
March 20, 20206 yr 1 hour ago, aptalca said: The web gui is a bit finnicky and refuses to open for me in a regular chrome window (perhaps a conflict with cookies?). I can open it in an incognito window, though. Just fyi Refuses to load or continually reloads? Common problem across all platforms. Clearing your history fixes it
March 20, 20206 yr Usually when the container restarts, it continuously tries to reload. Force refresh (shft+F5 or ctrl+F5) seems to take care of that one. But on one machine, I get an "empty response" from the site. On that machine, I have to use incognito (without cache or cookies). No idea why.
March 20, 20206 yr Another quirk, even if the user doesn't use nvidia runtime, or enable all the gpus, all nvidia gpus on the system are still detected, but they can't be started to fold. You'll see errors in the log. Don't be surprised.
March 20, 20206 yr And, unlike the other F@H app, it won't automatically join Team unRaid (quite understandable). The team # if you care is 227802 Edited March 20, 20206 yr by dockerPolice
March 21, 20206 yr Keep getting these errors on loading docker or restart of server and reload docker errors.txt
March 21, 20206 yr I had to restart the container a couple of times to get past that. Unfortunately it appears that F@H (on all platforms) has a bug (or their servers are simply overwhelmed) where occasionally it gets into a loop where it doesn't pick up anything at all. Keep restarting the app, or also install BOINC which never seems to suffer the same ill effects
March 21, 20206 yr 2 minutes ago, Squid said: I had to restart the container a couple of times to get past that. Unfortunately it appears that F@H (on all platforms) has a bug (or their servers are simply overwhelmed) where occasionally it gets into a loop where it doesn't pick up anything at all. Keep restarting the app, or also install BOINC which never seems to suffer the same ill effects seems like they need a little upgrade themselves
March 21, 20206 yr 2 hours ago, Titus said: seems like they need a little upgrade themselves I think their servers are getting overloaded. Way too many people started folding recently due to coronavirus (myself included).
March 21, 20206 yr It seems to be that way, just saw the latest WAN-show by linustechtips where they mentioned just that in the beginning of the episode.
March 21, 20206 yr https://www.tomshardware.com/news/folding-at-home-worlds-top-supercomputers-coronavirus-covid-19 https://cointelegraph.com/news/foldinghome-surpasses-400-000-users-amid-crypto-contribution
March 23, 20206 yr I joined the team last night. My Nvidia GPU was doing some work right after I installed it, but now it is sitting idle. I found this in the logs: 13:07:53:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104 [GeForce GTX 1060 6GB] from 13.90.152.57 13:07:53:WU01:FS01:Connecting to 13.90.152.57:8080 13:08:28:ERROR:WU01:FS01:Exception: Failed to remove directory './work/01': boost::filesystem::remove: Directory not empty: "./work/01" Is this an error on my end or on their end? Thanks. Edited March 23, 20206 yr by BradJ spelling
March 23, 20206 yr @linuxserver.io Thank you for making this application available to the Unraid community! Great work as always! I think we all should be running F@H with our always on machines now more than ever as we fight COVID-19 if you can spare the clock cycles, and we each individually can justify the extra cost of the higher power draw and component degradation. For those that may not want to run this container because it might "steal" compute resources from the server tasks, be advised that the docker app will run the CPU folding processes with a nice level of 19 (i.e. a LOW scheduler priority). So, this is not an issue and everything else on the system will have a CPU priority higher than the folding tasks even when operating in "Full Power" mode. The GPU doesn't work on a scheduler like the CPU, so yes, the GPU will work hard. BUT, I was able to fold and run 10+ Plex hardware transcoded streams on my GTX 1060 6GB card at the same time. So really, it's a non-issue as well. There's more than enough juice to go around! Hope this alleviates some concern! Join the UnRAID folding team and do your part! Service guarantees citizenship! UnRAID Folding Team: 227802 -JesterEE Edited March 23, 20206 yr by JesterEE
March 23, 20206 yr 5 hours ago, JesterEE said: @linuxserver.io Thank you for making this application available to the Unraid community! Great work as always! I think we all should be running F@H with our always on machines now more than ever as we fight COVID-19 if you can spare the clock cycles, and we each individually can justify the extra cost of the higher power draw and component degradation. For those that may not want to run this container because it might "steal" compute resources from the server tasks, be advised that the docker app will run the CPU folding processes with a nice level of 19 (i.e. a LOW scheduler priority). So, this is not an issue and everything else on the system will have a CPU priority higher than the folding tasks even when operating in "Full Power" mode. The GPU doesn't work on a scheduler like the CPU, so yes, the GPU will work hard. BUT, I was able to fold and run 10+ Plex hardware transcoded streams on my GTX 1060 6GB card at the same time. So really, it's a non-issue as well. There's more than enough juice to go around! Hope this alleviates some concern! Join the UnRAID folding team and do your part! Service guarantees citizenship! UnRAID Folding Team: 227802 -JesterEE Don't quote me on this, but I believe this container uses the main gpu cores whereas plex/emby/jellyfin use a separate dedicated hardware video acceleration core. So they shouldn't compete for the same resource (except for maybe ram, but this container uses little) Same way live streaming does not degrade the gaming experience as the livestream part uses the dedicated video acceleration core.
March 23, 20206 yr 6 hours ago, BradJ said: I joined the team last night. My Nvidia GPU was doing some work right after I installed it, but now it is sitting idle. I found this in the logs: 13:07:53:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104 [GeForce GTX 1060 6GB] from 13.90.152.57 13:07:53:WU01:FS01:Connecting to 13.90.152.57:8080 13:08:28:ERROR:WU01:FS01:Exception: Failed to remove directory './work/01': boost::filesystem::remove: Directory not empty: "./work/01" Is this an error on my end or on their end? Thanks. Haven't seen that. Try deleting it manually?
March 23, 20206 yr 2 queries 1) Via the Web GUI, under 'I support research fighting', I don't see an option for COVID19 so I've selected Any Disease, this right? 2) In any case, I can't seem to connect, which I presume is due to overload on the FAH end?? Logs: 22:06:13:50:192.168.86.33:New Web connection 22:06:37:WU00:FS00:Connecting to 65.254.110.245:8080 [93m22:06:37:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 22:06:37:WU00:FS00:Connecting to 18.218.241.186:80 [93m22:06:38:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m22:06:38:ERROR:WU00:FS00:Exception: Could not get an assignment[0m 22:08:14:WU00:FS00:Connecting to 65.254.110.245:8080 [93m22:08:15:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 22:08:15:WU00:FS00:Connecting to 18.218.241.186:80 22:08:15:WU00:FS00:Assigned to work server 40.114.52.201 22:08:15:WU00:FS00:Requesting new work unit for slot 00: READY cpu:15 from 40.114.52.201 22:08:15:WU00:FS00:Connecting to 40.114.52.201:8080 [93m22:08:47:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80[0m 22:08:47:WU00:FS00:Connecting to 40.114.52.201:80 [91m22:09:18:ERROR:WU00:FS00:Exception: Failed to connect to 40.114.52.201:80: Connection timed out[0m
March 24, 20206 yr 3 hours ago, quinctilius said: 2 queries 1) Via the Web GUI, under 'I support research fighting', I don't see an option for COVID19 so I've selected Any Disease, this right? 2) In any case, I can't seem to connect, which I presume is due to overload on the FAH end?? Logs: 22:06:13:50:192.168.86.33:New Web connection 22:06:37:WU00:FS00:Connecting to 65.254.110.245:8080 [93m22:06:37:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 22:06:37:WU00:FS00:Connecting to 18.218.241.186:80 [93m22:06:38:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m22:06:38:ERROR:WU00:FS00:Exception: Could not get an assignment[0m 22:08:14:WU00:FS00:Connecting to 65.254.110.245:8080 [93m22:08:15:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 22:08:15:WU00:FS00:Connecting to 18.218.241.186:80 22:08:15:WU00:FS00:Assigned to work server 40.114.52.201 22:08:15:WU00:FS00:Requesting new work unit for slot 00: READY cpu:15 from 40.114.52.201 22:08:15:WU00:FS00:Connecting to 40.114.52.201:8080 [93m22:08:47:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80[0m 22:08:47:WU00:FS00:Connecting to 40.114.52.201:80 [91m22:09:18:ERROR:WU00:FS00:Exception: Failed to connect to 40.114.52.201:80: Connection timed out[0m Yup, any disease will prioritize covid-19 It looks like the servers are overloaded and it may be a while before you're assigned a job
March 24, 20206 yr 22 hours ago, aptalca said: Haven't seen that. Try deleting it manually? Just a FYI... the issue has corrected itself. I believe this was an error related to the massive growth they have seen over the past few weeks.
March 25, 20206 yr 2 hours ago, aussie_huddo said: im guessing integrated intel GPU does not work with this? F@H does not support Intel gpus
March 25, 20206 yr So, for some reason, it does one WU and then it all basically dies. If i delete the container, delete the appdata folder and download it again, it works right away, once. No WU for almost 24 hours seems just, not right. 21:12:06:68:192.168.1.57:New Web connection 21:40:27:WU01:FS00:Connecting to 65.254.110.245:8080 [93m21:40:27:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 21:40:27:WU01:FS00:Connecting to 18.218.241.186:80 [93m21:40:28:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m21:40:28:ERROR:WU01:FS00:Exception: Could not get an assignment[0m ******************************* Date: 2020-03-24 ******************************* 23:43:27:WU01:FS00:Connecting to 65.254.110.245:8080 [93m23:43:27:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 23:43:27:WU01:FS00:Connecting to 18.218.241.186:80 [93m23:43:28:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m23:43:28:ERROR:WU01:FS00:Exception: Could not get an assignment[0m 03:02:27:WU01:FS00:Connecting to 65.254.110.245:8080 [93m03:02:28:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 03:02:28:WU01:FS00:Connecting to 18.218.241.186:80 [93m03:02:28:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m03:02:28:ERROR:WU01:FS00:Exception: Could not get an assignment[0m ******************************* Date: 2020-03-25 ******************************* 08:24:27:WU01:FS00:Connecting to 65.254.110.245:8080 [93m08:24:28:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 08:24:28:WU01:FS00:Connecting to 18.218.241.186:80 [93m08:24:28:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m08:24:28:ERROR:WU01:FS00:Exception: Could not get an assignment[0m ******************************* Date: 2020-03-25 ******************************* 14:24:27:WU01:FS00:Connecting to 65.254.110.245:8080 [93m14:24:28:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration[0m 14:24:28:WU01:FS00:Connecting to 18.218.241.186:80 [93m14:24:28:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m [91m14:24:28:ERROR:WU01:FS00:Exception: Could not get an assignment[0m My other f&h system that runs W10 and the client keeps getting WU's so it's, confusing...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.