129.74.85.16 Not accepting

[SomeStones]

One of my machines has been trying to send a work unit for several hours to this server on ports :80 and :8080. While the Server Status does not show any errors, it looks like the server is idle. When accessed directly, port :8080 returns nothing while port :80 does not connect.

Code: Select all

--- Opening Log file [August 22 00:34:16 UTC] 


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

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory: C:\Documents and Settings\van estes\Application Data\Folding@home-x86


[00:34:16] - Ask before connecting: No
[00:34:16] - User name: SomeStones (Team 48083)
[00:34:16] - User ID: 7773D66008A59343
[00:34:16] - Machine ID: 1
[00:34:16] 
[00:34:16] Loaded queue successfully.
[00:34:16] Initialization complete
[00:34:16] 
[00:34:16] + Processing work unit
[00:34:16] Core required: FahCore_78.exe
[00:34:16] Core found.
[00:34:16] Project: 7007 (Run 0, Clone 30, Gen 23)


[00:34:16] + Attempting to send results [August 22 00:34:16 UTC]
[00:34:16] Working on queue slot 08 [August 22 00:34:16 UTC]
[00:34:16] + Working ...
[00:34:16] - Couldn't send HTTP request to server
[00:34:16] + Could not connect to Work Server (results)
[00:34:16]     (129.74.85.15:8080)
[00:34:16] + Retrying using alternative port
[00:34:16] 
[00:34:16] *------------------------------*
[00:34:16] Folding@Home Gromacs Core
[00:34:16] Version 1.90 (March 8, 2006)
[00:34:16] 
[00:34:16] Preparing to commence simulation
[00:34:16] - Looking at optimizations...
[00:34:16] - Files status OK
[00:34:17] - Expanded 377062 -> 1807444 (decompressed 479.3 percent)
[00:34:17] 
[00:34:17] Project: 6883 (Run 140, Clone 17, Gen 19)
[00:34:17] 
[00:34:17] Assembly optimizations on if available.
[00:34:17] Entering M.D.
[00:34:18] - Couldn't send HTTP request to server
[00:34:18] + Could not connect to Work Server (results)
[00:34:18]     (129.74.85.15:80)
[00:34:18] - Error: Could not transmit unit 05 (completed August 21) to work server.


[00:34:18] + Attempting to send results [August 22 00:34:18 UTC]
[00:34:18] - Couldn't send HTTP request to server
[00:34:18] + Could not connect to Work Server (results)
[00:34:18]     (129.74.85.16:8080)
[00:34:18] + Retrying using alternative port
[00:34:19] - Couldn't send HTTP request to server
[00:34:19] + Could not connect to Work Server (results)
[00:34:19]     (129.74.85.16:80)
[00:34:19]   Could not transmit unit 05 to Collection server; keeping in queue.
[00:34:37] (Starting from checkpoint)
[00:34:37] Protein: ALZHEIMERS DISEASE AMYLOID
[00:34:37] 
[00:34:37] Writing local files
[00:35:19] Completed 27500 out of 250000 steps  (11%)
[00:35:19] Extra SSE boost OK.
[00:42:03] Writing local files
[00:42:03] Completed 30000 out of 250000 steps  (12%)
[00:47:21] Writing local files
[00:47:21] Completed 32500 out of 250000 steps  (13%)

(First time I've tried posting a log - hope it works.)

[bruce]

Welcome to foldingforum.org, SomeStones.

Please note that you're talking about a Collection Server. Your real interest should be in the work server at 129.74.85.15. See the "do this first" topic at the top of this forum.

When a server returns nothing (as http://129.74.85.16:8080 does) that means the server is working. When it returns an error (as http://129.74.85.16 does) something is wrong with the port 80 connection, but that's not necessarily a serious problem unless you're behind a firewall that blocks port 8080 -- and if you are, you probably can't be assigned WUs from that server so there would be no need to return them there. Moreover, that server has no WUs to assign, so I can't see a problem.

On the other hand, server 129.74.85.15 does have WUs to assign and appears to be sending and receiving between 350 and 400 WUs per hour on port 8080, so there doesn't seem to be a problem there, either.

[modern_sky_angel]

same issue today

Code: Select all

[19:47:25] + Attempting to send results [May 21 19:47:25 UTC]
[19:47:46] - Couldn't send HTTP request to server
[19:47:46] + Could not connect to Work Server (results)
[19:47:46]     (129.74.246.143:8080)
[19:47:46] + Retrying using alternative port
[19:47:51] Completed 1540000 out of 2000000 steps  (77%)
[19:48:07] - Couldn't send HTTP request to server
[19:48:07] + Could not connect to Work Server (results)
[19:48:07]     (129.74.246.143:80)
[19:48:07] - Error: Could not transmit unit 08 (completed May 21) to work server.


[19:48:07] + Attempting to send results [May 21 19:48:07 UTC]
[19:48:09] - Couldn't send HTTP request to server
[19:48:09] + Could not connect to Work Server (results)
[19:48:09]     (129.74.85.16:8080)
[19:48:09] + Retrying using alternative port
[19:48:10] - Couldn't send HTTP request to server
[19:48:10] + Could not connect to Work Server (results)
[19:48:10]     (129.74.85.16:80)
[19:48:10]   Could not transmit unit 08 to Collection server; keeping in queue.
[20:01:48] Completed 1560000 out of 2000000 steps  (78%)

this message repeated every 5 hour in my logs
my network is configured properly, so problems is not on my side

[abdulwahidc]

The CS should be back up now, though there still seems to be a problem with the WS.
I'm working to sort this out.
viewtopic.php?f=24&t=24265&p=242871#p242871

Thanks for reporting this issue.