No problem, I have edited my post.7im wrote:Please take care not to speculate too much. We don't want people to get the wrong idea, and then have that wrong idea perpetuated for the life of that client.
171.67.108.20
Moderators: Site Moderators, FAHC Science Team
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: Not receiving GPU3 WUs
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: Not receiving GPU3 WUs
I'm not saying that -advmethods doesn't make a difference. Clearly it does. But Core_15 WUs are set as a strictly normal WU, and if you request -adv, then -adv typically gets preference (assuming there are -adv wus available).
And checking the Server Status page (link above), GPU WU server x.x.108.20 is set to the F type program only. No A setting means no -adv, means your client will get sent to a different server when requesting -adv WUs. Empirical observation matches.
And checking the Server Status page (link above), GPU WU server x.x.108.20 is set to the F type program only. No A setting means no -adv, means your client will get sent to a different server when requesting -adv WUs. Empirical observation matches.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: Not receiving GPU3 WUs
Layman's translation: Using -advmethods flag on a Non-Fermi card running GPU3 Client will result in user obtaining FAHCore_11 WUs7im wrote:.. GPU WU server x.x.108.20 is set to the F type program only. No A setting means no -adv, means your client will get sent to a different server when requesting -adv WUs. Empirical observation matches.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: Not receiving GPU3 WUs
With the current settings, it appears that way, yes. They could change the settings on the work servers for those WUs at any time so -adv=fahcore_11 is NOT a hard fast rule.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Posts: 221
- Joined: Fri Jul 24, 2009 12:30 am
- Hardware configuration: 2 x GTX 460 (825/1600/1650)
AMD Athlon II X2 250 3.0Ghz
Kingston 2Gb DDR2 1066 Mhz
MSI K9A2 Platinum
Western Digital 500Gb Sata II
LiteOn DVD
Coolermaster 900W UCP
Antec 902
Windows XP SP3 - Location: Malvern, UK
Re: Not receiving GPU3 WUs
After setting up 5 instances of GPU3 on GTX260 216SP cards and initially getting a fahcore_15 WU, over the last 36 hours I was only getting fahcore_11 WUs.
I have just gone back and removed the advmethod flag from all the clients, the first GPU3 to load a new WU has now received a fahcore_15 WU.
I have just gone back and removed the advmethod flag from all the clients, the first GPU3 to load a new WU has now received a fahcore_15 WU.
Re: Can't get WU's: Attempt #7 to get work failed
Soo, my 480 isn't getting any work for maybe half an hour or more now. Are we already out of work?
That server is displayed as fully working in server stats though....
Code: Select all
[17:30:46] + Attempting to get work packet
[17:30:46] Passkey found
[17:30:46] Gpu type=3 species=30.
[17:30:46] - Connecting to assignment server
[17:30:47] - Successful: assigned to (171.67.108.20).
[17:30:47] + News From Folding@Home: Welcome to Folding@Home
[17:30:47] Loaded queue successfully.
[17:30:47] Gpu type=3 species=30.
[17:30:47] - Couldn't send HTTP request to server
[17:30:47] + Could not connect to Work Server
-
- Posts: 17
- Joined: Sun Jan 31, 2010 9:36 pm
Re: Can't get WU's: Attempt #7 to get work failed
I can't receive any work either
Re: Can't get WU's: Attempt #7 to get work failed
I can confirm this problem, but I don't see anything wrong either on the server status page or in the problems with servers forum.p2501 wrote:Soo, my 480 isn't getting any work for maybe half an hour or more now. Are we already out of work?
I tore apart my dual 9800GT box today to install a new GTX470. I installed the client, and got this:
Code: Select all
Note: Please read the license agreement (Folding@home-Win32-GPU.exe -license). F
urther
use of this software requires that you have read and accepted this agreement.
[17:03:58] Gpu type=3 species=30.
--- Opening Log file [June 10 17:03:58 UTC]
# Windows GPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.30r1
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: D:\Program Files\gpu3
Executable: D:\Program Files\gpu3\Folding@home-Win32-GPU.exe
Arguments: -verbosity 9
[17:03:58] - Ask before connecting: No
[17:03:58] - User name: ThunderRd (Team 45)
[17:03:58] - User ID: 1F992E945AC33820
[17:03:58] - Machine ID: 2
[17:03:58]
[17:03:58] Gpu type=3 species=30.
[17:03:58] Loaded queue successfully.
[17:03:58] - Preparing to get new work unit...
[17:03:58] - Autosending finished units... [June 10 17:03:58 UTC]
[17:03:58] Cleaning up work directory
[17:03:58] Trying to send all finished work units
[17:03:58] + No unsent completed units remaining.
[17:03:58] + Attempting to get work packet
[17:03:58] - Autosend completed
[17:03:58] Passkey found
[17:03:58] - Will indicate memory of 2047 MB
[17:03:58] Gpu type=3 species=30.
[17:03:58] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 1
1
[17:03:58] - Connecting to assignment server
[17:03:58] Connecting to http://assign-GPU.stanford.edu:8080/
[17:03:59] Posted data.
[17:03:59] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:03:59] + News From Folding@Home: Welcome to Folding@Home
[17:03:59] Loaded queue successfully.
[17:03:59] Gpu type=3 species=30.
[17:03:59] Sent data
[17:03:59] Connecting to http://171.67.108.20:8080/
[17:04:00] - Couldn't send HTTP request to server
[17:04:00] + Could not connect to Work Server
[17:04:00] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[17:04:06] + Attempting to get work packet
[17:04:06] Passkey found
[17:04:06] - Will indicate memory of 2047 MB
[17:04:06] Gpu type=3 species=30.
[17:04:06] - Connecting to assignment server
[17:04:06] Connecting to http://assign-GPU.stanford.edu:8080/
[17:04:07] Posted data.
[17:04:07] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:04:07] + News From Folding@Home: Welcome to Folding@Home
[17:04:08] Loaded queue successfully.
[17:04:08] Gpu type=3 species=30.
[17:04:08] Sent data
[17:04:08] Connecting to http://171.67.108.20:8080/
[17:04:08] - Couldn't send HTTP request to server
[17:04:08] + Could not connect to Work Server
[17:04:08] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[17:04:29] + Attempting to get work packet
[17:04:29] Passkey found
[17:04:29] - Will indicate memory of 2047 MB
[17:04:29] Gpu type=3 species=30.
[17:04:29] - Connecting to assignment server
[17:04:29] Connecting to http://assign-GPU.stanford.edu:8080/
[17:04:30] Posted data.
[17:04:30] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:04:30] + News From Folding@Home: Welcome to Folding@Home
[17:04:30] Loaded queue successfully.
[17:04:30] Gpu type=3 species=30.
[17:04:30] Sent data
[17:04:30] Connecting to http://171.67.108.20:8080/
[17:04:31] - Couldn't send HTTP request to server
[17:04:31] + Could not connect to Work Server
[17:04:31] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[17:04:55] + Attempting to get work packet
[17:04:55] Passkey found
[17:04:55] - Will indicate memory of 2047 MB
[17:04:55] Gpu type=3 species=30.
[17:04:55] - Connecting to assignment server
[17:04:55] Connecting to http://assign-GPU.stanford.edu:8080/
[17:04:56] Posted data.
[17:04:56] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:04:56] + News From Folding@Home: Welcome to Folding@Home
[17:04:56] Loaded queue successfully.
[17:04:56] Gpu type=3 species=30.
[17:04:56] Sent data
[17:04:56] Connecting to http://171.67.108.20:8080/
[17:04:56] - Couldn't send HTTP request to server
[17:04:56] + Could not connect to Work Server
[17:04:56] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[17:05:42] + Attempting to get work packet
[17:05:42] Passkey found
[17:05:42] - Will indicate memory of 2047 MB
[17:05:42] Gpu type=3 species=30.
[17:05:42] - Connecting to assignment server
[17:05:42] Connecting to http://assign-GPU.stanford.edu:8080/
[17:05:43] Posted data.
[17:05:43] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:05:43] + News From Folding@Home: Welcome to Folding@Home
[17:05:43] Loaded queue successfully.
[17:05:43] Gpu type=3 species=30.
[17:05:43] Sent data
[17:05:43] Connecting to http://171.67.108.20:8080/
[17:05:44] - Couldn't send HTTP request to server
[17:05:44] + Could not connect to Work Server
[17:05:44] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[17:07:09] + Attempting to get work packet
[17:07:09] Passkey found
[17:07:09] - Will indicate memory of 2047 MB
[17:07:09] Gpu type=3 species=30.
[17:07:09] - Connecting to assignment server
[17:07:09] Connecting to http://assign-GPU.stanford.edu:8080/
[17:07:10] Posted data.
[17:07:10] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:07:10] + News From Folding@Home: Welcome to Folding@Home
[17:07:10] Loaded queue successfully.
[17:07:10] Gpu type=3 species=30.
[17:07:10] Sent data
[17:07:10] Connecting to http://171.67.108.20:8080/
[17:07:11] - Couldn't send HTTP request to server
[17:07:11] + Could not connect to Work Server
[17:07:11] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[17:09:59] + Attempting to get work packet
[17:09:59] Passkey found
[17:09:59] - Will indicate memory of 2047 MB
[17:09:59] Gpu type=3 species=30.
[17:09:59] - Connecting to assignment server
[17:09:59] Connecting to http://assign-GPU.stanford.edu:8080/
[17:10:00] Posted data.
[17:10:00] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:10:00] + News From Folding@Home: Welcome to Folding@Home
[17:10:00] Loaded queue successfully.
[17:10:00] Gpu type=3 species=30.
[17:10:00] Sent data
[17:10:00] Connecting to http://171.67.108.20:8080/
[17:10:01] - Couldn't send HTTP request to server
[17:10:01] + Could not connect to Work Server
[17:10:01] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
I haven't been following the GPU3 news, but I have seen others with the same problem:
viewtopic.php?f=59&t=14710
I have tried both with and without the -advmethods flag, with the same results.
Has this been a common problem with this client? I hope not
Re: Can't get WU's: Attempt #7 to get work failed
Not common me thinks, my card has been blasting away for two days now. Maybe they're preparing new projects?
-
- Posts: 157
- Joined: Fri Feb 01, 2008 6:41 pm
Re: Can't get WU's: Attempt #7 to get work failed
I'm seeing the same thing. Started on my client at [16:22:46] which is 9:22am PDT.
I'm not getting any work and the error is the same as in your log above: "Couldn't send HTTP request to server" for the work server 171.67.108.20:8080 .
I'm not getting any work and the error is the same as in your log above: "Couldn't send HTTP request to server" for the work server 171.67.108.20:8080 .
No this is isn't common. We have had problems getting WU's something like 3 times since May 25th until now - about 16 days. The shortages have been resolved VERY quickly, within a couple hours. So for the duration of that 16 days, without having the exact numbers, I'd estimate about 10 hours lost to no WU's over a period of 16 days * 24 hours = 384 hours, so the down time is 10/384 = 3% in total. Not too shabby in the big picture! This GPU3 beta client and getting WU's is FAR more stable than the early days of GPU2. Pande Group has made some real progress in the reliability and stability of the Assignment and Work Servers since the early GPU2 days.p2501 wrote:Not common me thinks, my card has been blasting away for two days now. Maybe they're preparing new projects?ThunderRd wrote: Has this been a common problem with this client? I hope not
Last edited by ElectricVehicle on Thu Jun 10, 2010 6:17 pm, edited 3 times in total.
Fold On! (with 100% Renewable, 0 Carbon electricity) ElectricVehicle EV1, RAV4 EV, LEAF, Bolt EV, Volt, M3, s4 Simulator
Re: Can't get WU's: Attempt #7 to get work failed
Fun thing is that number of WUs on this server seems to go down even though it's not dishing out anything.
That was over 90k a few minutes ago.
Code: Select all
WUs AVAIL WUs to go WUs WAIT
89688 89688 89688
-
- Posts: 533
- Joined: Tue May 27, 2008 11:56 pm
- Hardware configuration: Parts:
Asus H370 Mining Master motherboard (X2)
Patriot Viper DDR4 memory 16gb stick (X4)
Nvidia GeForce GTX 1080 gpu (X16)
Intel Core i7 8700 cpu (X2)
Silverstone 1000 watt psu (X4)
Veddha 8 gpu miner case (X2)
Thermaltake hsf (X2)
Ubit riser card (X16) - Location: ames, iowa
171.67.108.20
could someone look into this?
Code: Select all
[17:32:56] + Attempting to get work packet
[17:32:56] Passkey found
[17:32:56] Gpu type=3 species=30.
[17:32:56] - Connecting to assignment server
[17:32:57] - Successful: assigned to (171.67.108.20).
[17:32:57] + News From Folding@Home: Welcome to Folding@Home
[17:32:57] Loaded queue successfully.
[17:32:57] Gpu type=3 species=30.
[17:32:57] - Couldn't send HTTP request to server
[17:32:57] + Could not connect to Work Server
[17:32:57] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
-
- Posts: 823
- Joined: Tue Mar 25, 2008 12:45 am
- Hardware configuration: Core i7 3770K @3.5 GHz (not folding), 8 GB DDR3 @2133 MHz, 2xGTX 780 @1215 MHz, Windows 7 Pro 64-bit running 7.3.6 w/ 1xSMP, 2xGPU
4P E5-4650 @3.1 GHz, 64 GB DDR3 @1333MHz, Ubuntu Desktop 13.10 64-bit
Re: Can't get WU's: Attempt #7 to get work failed
Both of my GPUs were stuck trying to get work. I restarted them with the -advmethods flag and they got GPU2 WUs. Neither is a Fermi, of course, so those with Fermis will just have to wait, but those with non-Fermis may be able to get work in the meantime.
-
- Posts: 157
- Joined: Fri Feb 01, 2008 6:41 pm
Re: 171.67.108.20
We're pushing 3 hours of no WU's. If we can get a response that the people who need to know, know, that would be nice. Shader cores are a terrible thing to idle!
Fold On! (with 100% Renewable, 0 Carbon electricity) ElectricVehicle EV1, RAV4 EV, LEAF, Bolt EV, Volt, M3, s4 Simulator
-
- Posts: 94
- Joined: Thu Nov 13, 2008 4:18 pm
- Hardware configuration: q6600 @ 3.3Ghz windows xp-sp3 one SMP2 (2.15 core) + 1 9800GT native GPU2
Athlon x2 6000+ @ 3.0Ghz ubuntu 8.04 smp + asus 9600GSO gpu2 in wine wrapper
5600X2 @ 3.19Ghz ubuntu 8.04 smp + asus 9600GSO gpu2 in wine wrapper
E5200 @ 3.7Ghz ubuntu 8.04 smp2 + asus 9600GT silent gpu2 in wine wrapper
E5200 @ 3.65Ghz ubuntu 8.04 smp2 + asus 9600GSO gpu2 in wine wrapper
E6550 vmware ubuntu 8.4.1
q8400 @ 3.3Ghz windows xp-sp3 one SMP2 (2.15 core) + 1 9800GT native GPU2
Athlon II 620 @ 2.6 Ghz windows xp-sp3 one SMP2 (2.15 core) + 1 9800GT native GPU2 - Location: Calgary, Canada
Re: 171.67.108.20
I have all 5 of my GPU3 clients down for at least 2 hours. A reply really would be appreciated.