Page 1 of 1

Can't upload 171.64.65.62 or 171.67.108.25

Posted: Tue Sep 14, 2010 12:59 pm
by More_Fiber
I have one machine that can't upload to either 171.64.65.62 or 171.67.108.25.
I've checked both IP addresses on both port 80 and port 8080 from IE on that machine and get an "OK" back on both ports on each address.

Server stats shows both servers to be up:
Tue Sep 14 05:20:10 PDT 2010 171.64.65.62 classic vspg10c vvoelz full Accepting
Tue Sep 14 05:20:10 PDT 2010 171.67.108.25 CS 5 vsp19v pande accept Accepting

The machine has been in this condition for about 12 hours.
Other machines have been getting work units from other IP addresses.

Code: Select all

# Windows CPU Systray Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: D:\Folding@home\paladin.1
Arguments: -send all -verbosity 9 

[12:19:51] - Ask before connecting: No
[12:19:51] - User name: More_FIber (Team 4)
[12:19:51] - User ID: 56586DEA559F6797
[12:19:51] - Machine ID: 1
[12:19:51] 
[12:19:52] Loaded queue successfully.
[12:19:52] Initialization complete
[12:19:52] Attempting to return result(s) to server...
[12:19:52] Trying to send all finished work units
[12:19:52] Project: 6509 (Run 14, Clone 185, Gen 14)
[12:19:52] - Read packet limit of 540015616... Set to 524286976.


[12:19:52] + Attempting to send results [September 14 12:19:52 UTC]
[12:19:52] - Reading file work/wuresults_02.dat from core
[12:19:52]   (Read 851171 bytes from disk)
[12:19:52] Connecting to http://171.64.65.62:8080/
[12:19:52] - Couldn't send HTTP request to server
[12:19:52] + Could not connect to Work Server (results)
[12:19:52]     (171.64.65.62:8080)
[12:19:52] + Retrying using alternative port
[12:19:52] Connecting to http://171.64.65.62:80/
[12:19:52] - Couldn't send HTTP request to server
[12:19:52] + Could not connect to Work Server (results)
[12:19:52]     (171.64.65.62:80)
[12:19:52] - Error: Could not transmit unit 02 (completed September 14) to work server.
[12:19:52] - 7 failed uploads of this unit.
[12:19:52] - Read packet limit of 540015616... Set to 524286976.


[12:19:52] + Attempting to send results [September 14 12:19:52 UTC]
[12:19:52] - Reading file work/wuresults_02.dat from core
[12:19:52]   (Read 851171 bytes from disk)
[12:19:52] Connecting to http://171.67.108.25:8080/
[12:19:52] - Couldn't send HTTP request to server
[12:19:52] + Could not connect to Work Server (results)
[12:19:52]     (171.67.108.25:8080)
[12:19:52] + Retrying using alternative port
[12:19:52] Connecting to http://171.67.108.25:80/
[12:19:52] - Couldn't send HTTP request to server
[12:19:52] + Could not connect to Work Server (results)
[12:19:52]     (171.67.108.25:80)
[12:19:52]   Could not transmit unit 02 to Collection server; keeping in queue.
[12:19:52] + Sent 0 of 1 completed units to the server
[12:19:52] - Failed to send all units to server
[12:19:52] ***** Got a SIGTERM signal (2)
[12:19:52] Killing all core threads

Folding@Home Client Shutdown.
[/size]

Re: Can't upload 171.64.65.62 or 171.67.108.25

Posted: Wed Sep 15, 2010 12:06 am
by More_Fiber
Update 20:00 ET. Still not uploading to either server.

Re: Can't upload 171.64.65.62 or 171.67.108.25

Posted: Wed Sep 15, 2010 5:25 am
by bruce
That's not an easy problem to diagnose, but one of the most common causes is overly zealous security software. Do you have any anti-spyware software or a security suite which might include antispyware? Have you tried disabling that function to see if it's related?

Re: Can't upload 171.64.65.62 or 171.67.108.25

Posted: Thu Sep 16, 2010 5:06 pm
by sortofageek
For the record, this issue was caused by an overzealous McAfee. To date we're not sure if it was due to a McAfee update or what. The clients on that computer had worked fine for quite awhile.