I completed a work unit (SMP:4) around 2.5 hours ago and have been assigned work and collection servers 0.0.0.0
It's a long time since I have had a machine sit idle. Does anyone know if there is a problem or shortage of appropriate WU's?
Work Server 0.0.0.0
Moderators: Site Moderators, FAHC Science Team
Re: Work Server 0.0.0.0
Being assigned to server 0.0.0.0 instead of a WU means several things. Posting your log would add some important details about what's actually happening, but I'll start by suggesting that you need to update your client. V7 would be good the absolute minimum would be V6.34. A lot of projects won't run on clients older than that.
Specific servers might be having temporary shortages of some projects but I'm not aware of any permanent restrictions other than from having an older client. There was a temporary outage and I'm not sure how long it was.
Specific servers might be having temporary shortages of some projects but I'm not aware of any permanent restrictions other than from having an older client. There was a temporary outage and I'm not sure how long it was.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 28
- Joined: Thu Dec 08, 2011 5:24 am
- Hardware configuration: Intel i5 650, 4GB RAM, Win 7 Pro 64-bit
- Location: Christchurch, New Zealand
- Contact:
Re: Work Server 0.0.0.0
Thanks for the reply Bruce.
I now have four machines affected. All are running v7 (7.1.52 & 7.1.48). Two are XP machines and 2 are Win7. One of these machines runs both SMP and GPU units. The GPU is still getting new units. My 5th machine (an iMac at a different location) is also still happily plugging away.
Here is a representative chunk from my day to day work machine. It does not show the previous WU upload because I took advantage of the outage to run some updates and reboot. Next week (I'm away for a few days) if this is still ongoing I can get logs from other machines.
I now have four machines affected. All are running v7 (7.1.52 & 7.1.48). Two are XP machines and 2 are Win7. One of these machines runs both SMP and GPU units. The GPU is still getting new units. My 5th machine (an iMac at a different location) is also still happily plugging away.
Here is a representative chunk from my day to day work machine. It does not show the previous WU upload because I took advantage of the outage to run some updates and reboot. Next week (I'm away for a few days) if this is still ongoing I can get logs from other machines.
Code: Select all
*********************** Log Started 2012-09-26T06:25:12Z ***********************
06:25:12:************************* Folding@home Client *************************
06:25:12: Website: http://folding.stanford.edu/
06:25:12: Copyright: (c) 2009-2012 Stanford University
06:25:12: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:25:12: Args: --lifeline 1088 --command-port=36330
06:25:12: Config: C:/ProgramData/FAHClient/config.xml
06:25:12:******************************** Build ********************************
06:25:12: Version: 7.1.52
06:25:12: Date: Mar 20 2012
06:25:12: Time: 19:37:42
06:25:12: SVN Rev: 3515
06:25:12: Branch: fah/trunk/client
06:25:12: Compiler: Intel(R) C++ MSVC 1500 mode 1200
06:25:12: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
06:25:12: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT
06:25:12: Platform: win32 XP
06:25:12: Bits: 32
06:25:12: Mode: Release
06:25:12:******************************* System ********************************
06:25:12: CPU: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz
06:25:12: CPU ID: GenuineIntel Family 6 Model 37 Stepping 2
06:25:12: CPUs: 4
06:25:12: Memory: 3.80GiB
06:25:12: Free Memory: 1.77GiB
06:25:12: Threads: WINDOWS_THREADS
06:25:12: On Battery: false
06:25:12: UTC offset: 12
06:25:12: PID: 6092
06:25:12: CWD: C:/ProgramData/FAHClient
06:25:12: OS: Windows 7 Professional
06:25:12: OS Arch: AMD64
06:25:12: GPUs: 0
06:25:12: CUDA: Not detected
06:25:12:Win32 Service: false
06:25:12:***********************************************************************
06:25:12:<config>
06:25:12: <!-- FahCore Control -->
06:25:12: <checkpoint v='30'/>
06:25:12:
06:25:12: <!-- Network -->
06:25:12: <proxy v=':8080'/>
06:25:12:
06:25:12: <!-- User Information -->
06:25:12: <passkey v='********************************'/>
06:25:12: <user v='RLHay'/>
06:25:12:
06:25:12: <!-- Folding Slots -->
06:25:12: <slot id='0' type='SMP'/>
06:25:12:</config>
06:25:12:Trying to access database...
06:25:12:Successfully acquired database lock
06:25:12:Enabled folding slot 00: READY smp:4
06:25:12:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:25:16:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
06:25:33:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:25:33:WU00:FS00:Connecting to assign4.stanford.edu:80
06:25:35:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:25:35:ERROR:WU00:FS00:Exception: Could not get an assignment
06:25:35:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:25:56:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:25:56:WU00:FS00:Connecting to assign4.stanford.edu:80
06:25:58:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:25:58:ERROR:WU00:FS00:Exception: Could not get an assignment
06:26:35:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:26:56:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:26:56:WU00:FS00:Connecting to assign4.stanford.edu:80
06:26:58:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:26:58:ERROR:WU00:FS00:Exception: Could not get an assignment
06:28:13:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:28:34:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:28:34:WU00:FS00:Connecting to assign4.stanford.edu:80
06:28:35:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:28:35:ERROR:WU00:FS00:Exception: Could not get an assignment
06:30:50:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:31:11:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:31:11:WU00:FS00:Connecting to assign4.stanford.edu:80
06:31:13:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:31:13:ERROR:WU00:FS00:Exception: Could not get an assignment
06:35:04:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:35:25:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:35:25:WU00:FS00:Connecting to assign4.stanford.edu:80
06:35:27:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:35:27:ERROR:WU00:FS00:Exception: Could not get an assignment
06:41:55:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:42:16:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:42:16:WU00:FS00:Connecting to assign4.stanford.edu:80
06:42:18:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:42:18:ERROR:WU00:FS00:Exception: Could not get an assignment
06:53:01:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:53:22:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:53:22:WU00:FS00:Connecting to assign4.stanford.edu:80
06:53:24:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: No connection could be made because the target machine actively refused it.
06:53:24:ERROR:WU00:FS00:Exception: Could not get an assignment
07:10:58:WU00:FS00:Connecting to assign3.stanford.edu:8080
07:11:19:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Re: Work Server 0.0.0.0
When you cannot connect to assign3.stanford.edu or assign4.stanford.edu that problem must be fixed first. I can currently connect to one of them through by browser in the form http://assign3.stanford.edu:8080 or http://assign3.stanford.edu:80 but not to http://assign4.stanford.edu. I'll notify the Pande Group about the fact that the latter server has been down since 18:20:00 PDT last evening.
Most people can get their assignments through http://assign3.stanford.edu but it may be blocked by your security hardware or software, so testing in in your browser is the first step to seeing if you have a local problem that can be fixed.
Most people can get their assignments through http://assign3.stanford.edu but it may be blocked by your security hardware or software, so testing in in your browser is the first step to seeing if you have a local problem that can be fixed.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 28
- Joined: Thu Dec 08, 2011 5:24 am
- Hardware configuration: Intel i5 650, 4GB RAM, Win 7 Pro 64-bit
- Location: Christchurch, New Zealand
- Contact:
Re: Work Server 0.0.0.0
Bruce, just letting you know that all the machines appear to be receiving and returning work units again without any intervention at my end (I've been away for a few days). So, thanks for your help but I'm pretty certain whatever the issue and solution was it was at PG's end.