14:33:39:Trying to send results to collection server
14:33:39:Unit 01: Uploading 2.37MiB to 171.67.108.26
14:33:39:Connecting to 171.67.108.26:8080
14:33:41:WARNING: WorkServer connection failed on port 8080 trying 80
14:33:41:Connecting to 171.67.108.26:80
14:33:41:WARNING: WorkServer connection failed on port 8080 trying 80
14:33:41:Connecting to 171.67.108.26:80
14:33:42:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
14:33:43:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
WS 171.64.65.56 connection failed (CS 171.67.108.26 too)
Moderators: Site Moderators, FAHC Science Team
WS 171.64.65.56 connection failed (CS 171.67.108.26 too)
I've been having problems reporting WUs during the past day or two. I get the following messages in the logs.
-
- Posts: 6
- Joined: Fri Dec 09, 2011 3:33 pm
Re: WorkServer connection failed to 171.67.108.26
Hello,
I have the exact same problem; with the exact same log. Therefore i didn't want to repeatedly post it. In the server status page, the server is in STANDBY mode which is described as not serving FAH wus. As I use V7 client, could this be a bug? I haven't encountered such lasting issue until two days ago; nor any configuration change. So something should have happened at that time.
I have the exact same problem; with the exact same log. Therefore i didn't want to repeatedly post it. In the server status page, the server is in STANDBY mode which is described as not serving FAH wus. As I use V7 client, could this be a bug? I haven't encountered such lasting issue until two days ago; nor any configuration change. So something should have happened at that time.
-
- Site Admin
- Posts: 3110
- Joined: Fri Nov 30, 2007 8:06 pm
- Location: Team Helix
- Contact:
Re: WorkServer connection failed to 171.67.108.26
Welcome to the Folding@Home Support Forums. I don't think we're seeing enough log info to be able to help. Checking the Server Status page, it appears 171.67.108.26 is a collection server.
There is a stickied topic at the top of this forum here ---> Troubleshooting Server Connectivity Issues (Do This First)
Please work through the suggestions there and then let us know what you have tried and if anything there helped.
If you still need help, please post the first 20-25 lines of the log where the client starts up, then post the part of the log that shows all the relevant info about the WU starting, finishing, trying to send, etc.
There is a stickied topic at the top of this forum here ---> Troubleshooting Server Connectivity Issues (Do This First)
Please work through the suggestions there and then let us know what you have tried and if anything there helped.
If you still need help, please post the first 20-25 lines of the log where the client starts up, then post the part of the log that shows all the relevant info about the WU starting, finishing, trying to send, etc.
-
- Posts: 6
- Joined: Fri Dec 09, 2011 3:33 pm
Re: WorkServer connection failed to 171.67.108.26
Hello again, I did what you've asked and here are results.
The WS is 171.64.65.56. My browser were able to open the sites and i saw OK in all of them. I set the verbosity to 5 (in v7 couldn't know how to set the -verbosity 9 in slot-add section). The issue happens in my two rigs; each with client-advanced set and receive fah core 16. One with 5970 and other with 3x6970. Here is the log:
The WS is 171.64.65.56. My browser were able to open the sites and i saw OK in all of them. I set the verbosity to 5 (in v7 couldn't know how to set the -verbosity 9 in slot-add section). The issue happens in my two rigs; each with client-advanced set and receive fah core 16. One with 5970 and other with 3x6970. Here is the log:
Code: Select all
16:17:29:Unit 00:Preparing to commence simulation
16:17:29:Unit 00:- Ensuring status. Please wait.
16:17:29:Unit 04:
16:17:29:Unit 04:*------------------------------*
16:17:29:Unit 04:Folding@Home GPU Core
16:17:29:Unit 04:Version 2.11 (Thu Dec 9 15:00:14 PST 2010)
16:17:29:Unit 04:
16:17:29:Unit 04:Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
16:17:29:Unit 04:Build host: user-f6d030f24f
16:17:29:Unit 04:Board Type: AMD/OpenCL
16:17:29:Unit 04:Core : x=16
16:17:29:Unit 04: Window's signal control handler registered.
16:17:29:Unit 04:Preparing to commence simulation
16:17:29:Unit 04:- Ensuring status. Please wait.
16:17:30:WARNING: WorkServer connection failed on port 8080 trying 80
16:17:30:Connecting to 171.64.65.56:80
16:17:30:WARNING: WorkServer connection failed on port 8080 trying 80
16:17:30:Connecting to 171.64.65.56:80
16:17:32:Started thread 9 on PID 2360
16:17:32:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
16:17:32:WARNING: Exception: Failed to send results to work server: Failed to connect to 171.64.65.56:80: No connection could be made because the target machine actively refused it.
16:17:32:Trying to send results to collection server
16:17:32:Unit 01: Uploading 2.37MiB to 171.67.108.26
16:17:32:WARNING: Exception: Failed to send results to work server: Failed to connect to 171.64.65.56:80: No connection could be made because the target machine actively refused it.
16:17:32:Connecting to 171.67.108.26:8080
16:17:32:Trying to send results to collection server
16:17:32:Unit 02: Uploading 2.37MiB to 171.67.108.26
16:17:32:Connecting to 171.67.108.26:8080
16:17:34:WARNING: WorkServer connection failed on port 8080 trying 80
16:17:34:Connecting to 171.67.108.26:80
16:17:34:WARNING: WorkServer connection failed on port 8080 trying 80
16:17:34:Connecting to 171.67.108.26:80
16:17:35:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
16:17:35:Sending unit results: id:01 state:SEND error:OK project:11294 run:6 clone:248 gen:72 core:0x16 unit:0x000000540a3b1e5c4d9a1ce679756840
16:17:35:Unit 01: Uploading 2.37MiB to 171.64.65.56
16:17:35:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
16:17:35:Connecting to 171.64.65.56:8080
16:17:36:Sending unit results: id:02 state:SEND error:OK project:11294 run:5 clone:172 gen:181 core:0x16 unit:0x000000c50a3b1e5c4d9a1cbdafa95cbe
16:17:36:Unit 02: Uploading 2.37MiB to 171.64.65.56
16:17:36:Connecting to 171.64.65.56:8080
-
- Posts: 48
- Joined: Thu Dec 01, 2011 12:31 am
- Hardware configuration: @UK: Win7 Ultimate x64, Intel i5-2500K @ 4.2 GHz, Asus P8P67, 8 GB DDR3-1600, MSI R6870 Hawk, Crucial M4 128GB SSD, Samsung 1.5TB HDD.
@LUX: Win7 Professional x64, Intel Core 2 Duo E6600, Asus P5W DH Deluxe, 3 GB DDR2-800, Leadtek WinFast PX8800GT, over 9000 HDDs. - Location: Clervaux, LUX; Brighton, UK; Heidelberg, GER
Re: WorkServer connection failed to 171.67.108.26
171.64.65.56 is still rejecting connections according to the server status page. Yesterday the server had been suffering from high CPU load, but that has been fixed it seems. See viewtopic.php?f=18&t=20140
Steam profile | Perfection consists not in doing extraordinary things, but in doing ordinary things extraordinarily well. -Angelique Arnauld
-
- Posts: 6
- Joined: Fri Dec 09, 2011 3:33 pm
Re: WS 171.64.65.56 connection failed (CS 171.67.108.26 too)
Much better. All wus have been uploaded. Thank you for the clarification.