171.64.65.102

[kzaske]

I don't see this being reported anywhere else so here goes. The server located at 171.64.65.102 has been rejecting work units since 16:15:10 today (Saturday). This is affecting GPU work units using V7 client.

[bruce]

Post moved to the section on Server problems and title changed to conform with recommendations.

[bruce]

From what I've heard, this will not be fixed until morning, California time, and will probably take longer than that.

Are you being assigned work from another server?

Please post your log, including the system description at the top and representative error messages after that.

[kzaske]

From what I've heard, this will not be fixed until morning, California time, and will probably take longer than that.

Are you being assigned work from another server?

Please post your log, including the system description at the top and representative error messages after that.

Sorry about putting my post in the wroing location.
System Description: I had to type this in from the System info tab.

Code: Select all

OS:Windows 7 Home Premium x64
CPU:AMD Phenom II x6 1090T
CPU ID: AMD Family 16 Model 10 Stepping 0
CPUs: 6
Memory: 8.00GiB
Free Memory: 6.02GiB
Threads: WINDOWS_THREADS
GPU:1
GPU:0 ATI:4 Caymon PRO (AMD Radeon 6900 Series)
CUDA: Not detected
On Battery: False
UTC offset: -6
PID: 5080
Win32 Service: False

Log:

Code: Select all

05:42:25:News: Welcome to Folding@Home
05:42:25:WARNING: Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
05:42:25:Connecting to assign-GPU.stanford.edu:8080
05:42:25:News: Welcome to Folding@Home
05:42:25:WARNING: Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
05:42:25:ERROR: Exception: Could not get an assignment
05:42:29:Sending unit results: id:00 state:SEND project:5734 run:4 clone:555 gen:391 core:0x11 unit:0x340bf64d4dd7fa8c0187022b00041666
05:42:29:Unit 00: Uploading 255.05KiB
05:42:29:Connecting to 171.64.65.102:8080
05:42:30:WARNING: WorkServer connection failed on port 8080 trying 80
05:42:30:Connecting to 171.64.65.102:80
05:42:30:Unit 03:Completed 30000 out of 500000 steps  (6%)
05:42:31:WARNING: Exception: Failed to send results to work server: Failed to connect to 171.64.65.102:80: No connection could be made because the target machine actively refused it.
05:42:31:Trying to send results to collection server
05:42:31:Unit 00: Uploading 255.05KiB
05:42:31:Connecting to 171.67.108.17:8080
05:42:32:WARNING: WorkServer connection failed on port 8080 trying 80
05:42:32:Connecting to 171.67.108.17:80
05:42:33:ERROR: Exception: Failed to connect to 171.67.108.17:80: No connection could be made because the target machine actively refused it.

[dpp4me@gmail.com]

So after reading this thread I guess I should just wait ?


This machine has been running GPU3 for 2 weeks, I have another machine that has been running GPU3 for a couple of days. Changed from GPU2 to GPU3.
Yesterday they stopped working. Both machine are having the same problem.
Can''t connect to work server.


[14:21:03] Folding@home Core Shutdown: FINISHED_UNIT
[14:21:06] CoreStatus = 64 (100)
[14:21:06] Unit 1 finished with 77 percent of time to deadline remaining.
[14:21:06] Updated performance fraction: 0.883013
[14:21:06] Sending work to server
[14:21:06] Project: 5737 (Run 4, Clone 607, Gen 408)
[14:21:06] - Read packet limit of 540015616... Set to 524286976.


[14:21:06] + Attempting to send results [May 22 14:21:06 UTC]
[14:21:06] - Reading file work/wuresults_01.dat from core
[14:21:06] (Read 263222 bytes from disk)
[14:21:06] Gpu type=1 species=4.
[14:21:06] Connecting to http://171.64.65.102:8080/
[14:21:07] - Couldn't send HTTP request to server
[14:21:07] + Could not connect to Work Server (results)
[14:21:07] (171.64.65.102:8080)
[14:21:07] + Retrying using alternative port
[14:21:07] Connecting to http://171.64.65.102:80/
[14:21:08] - Couldn't send HTTP request to server
[14:21:08] + Could not connect to Work Server (results)
[14:21:08] (171.64.65.102:80)
[14:21:08] - Error: Could not transmit unit 01 (completed May 22) to work server.
[14:21:08] - 1 failed uploads of this unit.

[VijayPande]

It's back up now.

[Eldest_One]

It's back up now.

Thank you

[kzaske]

Thank you. Completed work units have been uploaded and it's happly folding again. Thanks.

[PantherX]

...System Description: I had to type this in from the System info tab.

Code: Select all

OS:Windows 7 Home Premium x64
CPU:AMD Phenom II x6 1090T
CPU ID: AMD Family 16 Model 10 Stepping 0
CPUs: 6
Memory: 8.00GiB
Free Memory: 6.02GiB
Threads: WINDOWS_THREADS
GPU:1
GPU:0 ATI:4 Caymon PRO (AMD Radeon 6900 Series)
CUDA: Not detected
On Battery: False
UTC offset: -6
PID: 5080
Win32 Service: False

...

We all appreciate the effort that you put into typing this information. However, there is a much easier way and that is to open the log file and copy the *******System***** section of the log which should be near the top of the log. If you're unsure of the location of the log, please read this (https://fah-web.stanford.edu/projects/F ... #DataFiles). I hope that you find this useful in the future.

[bruce]

I'm curious: Did you copy it from the middle of the FAHControl screen or did you find it on disk?

Did you consider doing a Copy/Paste from the log screen? Highlight the section that you want to copy and use the standard keyboard shortcuts. In Windows, that's CTRL-C for Copy and CTRL-V for paste.

[kzaske]

I used the System Info tab, Expert interface mode.
As for the system information in the log, there was nothing there. I just checked again, still no system information there.

[GreyWhiskers]

on the LOG tab, did you press the RELOAD button? That's usually what it takes to bring up the whole log. Otherwise, you only get a small snippet of the log.

[GreyWhiskers]

Actually, I just now looked at the v7 status for my HD4670 AGP GPU and saw that the client has been trying to upload/download WUs unsuccessfully for about 12 hours now. Snore.

I haven't posted the log - it shows that the GPU slot is stalled now - trying to upload/download. The server log shows how long the server has been down.

Any news on this?

Code: Select all

Thu Jun 2 11:15:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Accepting
Thu Jun 2 11:50:10 PDT 2011	171.64.65.102	GPU	vspg2v2	-	No Response	Accepting
Thu Jun 2 12:25:10 PDT 2011	171.64.65.102	GPU	vspg2v2	-	full	DOWN
Thu Jun 2 13:05:11 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 13:40:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 14:15:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 14:50:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 15:25:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 16:00:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 16:35:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 17:10:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject						
Thu Jun 2 17:45:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 18:20:11 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 18:55:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 19:30:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 20:05:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 20:40:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 21:15:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Thu Jun 2 21:50:10 PDT 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject