Search found 25 matches
- Mon Apr 08, 2019 1:46 pm
- Forum: Issues with a specific WU
- Topic: No WUs available for this configuration
- Replies: 10
- Views: 20745
Re: No WUs available for this configuration
I'm also having the same error for my GPU slot since a few hours ago. Tried: Restart PC, change FAH proxy, delete & re-add GPU slot but still couldn't fix it. *********************** Log Started 2019-04-08T13:22:17Z *********************** 13:22:17:************************* Folding@home Client *...
- Fri Aug 10, 2018 2:14 am
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: FAH config doesn't take effect until FAHClient is restarted
- Replies: 13
- Views: 5344
Re: FAH config doesn't take effect until FAHClient is restar
i would suggest to terminate FAHCore gracefully using pause and unpause after FAHClient is restarted, so that you don't lose any unsaved progress, and also to have assembly optimization enabled (fahcore will auto disable optimization in case of improper termination) FAHClient --send-pause Pause a sl...
- Thu Aug 09, 2018 3:43 pm
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: FAH config doesn't take effect until FAHClient is restarted
- Replies: 13
- Views: 5344
Re: FAH config doesn't take effect until FAHClient is restar
Some settings are applied immediately and others are only applied during startup. Unfortunately, networking is initialized during startup and is not restarted until FAHClient, itself, is restarted. :( Getting a new feature added generally takes a long time, but I did open a ticket for it. https://g...
- Thu Aug 09, 2018 2:56 am
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: FAH config doesn't take effect until FAHClient is restarted
- Replies: 13
- Views: 5344
Re: FAH Configuration: New proxy doesn't take effect
Have you tried restarting the fah client? (easiest but not fastest way is to reboot). Just a thought as I don't use a proxy. You are correct. I have just checked the old logs and found out that the new proxy setting didn't take effect untill I restarted my PC. I have changed the topic title. Is the...
- Thu Aug 09, 2018 2:35 am
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: FAH config doesn't take effect until FAHClient is restarted
- Replies: 13
- Views: 5344
FAH config doesn't take effect until FAHClient is restarted
I have set FAHClient to connect to the internet via proxy (because my country's firewall makes the connections to FAH servers very slow). Because sometimes the proxy server is offline or slow, I frequently change the proxy. Below is FAH configuration: 01:25:32:<config> 01:25:32: <!-- Folding Core --...
- Thu Aug 09, 2018 2:03 am
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
you are correct, it's one of the proxies that i've set. Full log: http://pastebin.com/raw/ZwX6SLkG however, i have changed to many other proxies as you can see in the log. somehow the old proxy 144.217.51.236:8080 still keeps sticking to new connections, so i've thought it is another fah server. thi...
- Thu Aug 09, 2018 1:01 am
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
Recently FAHClient usually connects to 144.217.51.236:8080 to download new WU although there is no such server in the list here http://fah-web.stanford.edu/pybeta/serverstat.html Is this added recently? 23:08:45:WU00:FS01:Connecting to 144.217.51.236:8080 23:08:47:WU00:FS01:Assigned to work server 1...
- Thu Aug 02, 2018 7:17 am
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
i have set up HTTP proxy for FAHClient (randomly picked an US proxy with port 80 or 8080 from this list http://www.gatherproxy.com/proxylist/co ... d%20States), although the proxy only has 1 opened port (80 or 8080), FAHClient still can connect and download/upload WU sucessfully (sometimes after 2nd...
- Mon Jul 30, 2018 1:54 pm
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
here is more log from MyRepublic ISP: *********************** Log Started 2018-07-29T19:26:13Z *********************** 19:26:13:************************* Folding@home Client ************************* 19:26:13: Website: https://foldingathome.org/ 19:26:13: Copyright: (c) 2009-2018 foldingathome.org 1...
- Sun Jul 29, 2018 7:51 pm
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
Did you try to use FAHClient on the MyRepublic ISP ? My old laptop is very slow and it doesn't have a discrete GPU, so I can't provide a side-by-side comparison but here is a short log showing the download speed of FahCore a7 on MyRepublic: *********************** Log Started 2018-07-29T19:26:13Z *...
- Sun Jul 29, 2018 5:26 pm
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
So it's really another similar case to "Great Firewall of China" as bruce mentioned.
- Sun Jul 29, 2018 12:06 pm
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
here is tracert from another ISP "MyRepublic" tracert plfah1-1.mskcc.org Tracing route to plfah1-1.mskcc.org [140.163.4.231] over a maximum of 30 hops: 1 2 ms 1 ms 20 ms Linksys [192.168.1.1] 2 12 ms 37 ms 7 ms 101.100.160.2 3 3 ms 3 ms 2 ms 40GE-103-6-148-45.myrepublic.com.sg [103.6.148.4...
- Sun Jul 29, 2018 5:44 am
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
Tracert details to 140.163.4.231 Tracing route to plfah1-1.mskcc.org [140.163.4.231] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.254 2 2 ms 2 ms 2 ms bb119-74-45-254.singnet.com.sg [119.74.45.254] 3 4 ms 2 ms 2 ms 202.166.123.134 4 16 ms 2 ms 4 ms 202.166.123.133 5 2 ms 2 ms 2 ms ae8-0...
- Fri Jul 27, 2018 6:39 pm
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
That's very interesting to know - thanks for enlightening me.
Maybe I will dig more about this satellite hopping (for personal knowledge) when I have time.
Maybe I will dig more about this satellite hopping (for personal knowledge) when I have time.
- Fri Jul 27, 2018 6:08 pm
- Forum: Issues with a specific server
- Topic: Slow WU downloads & failed transfer [140.163.4.231]
- Replies: 75
- Views: 30761
Re: Slow WU downloads & failed transfer [140.163.4.231]
for me, tracert also stopped at step 15 - 74.8.57.6 - but maybe the numbers can tell something. They're dropping pings and traceroutes - you won't get anything from those. tracert 140.163.4.231 Tracing route to plfah1-1.mskcc.org [140.163.4.231] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1....