usually with assigned to 0.0.0.0 message.
occasionally assign to 171.67.108.13 but also can't get wu,checking in browser it says states OK
I'm running client v5.3 OS is win2k(with sp4)
this has happened for more than 4hours,down blow is the error logs
it begins at 18:39:39
[18:36:23] Done: 6705176 -> 4797607 (compressed to 71.5 percent)
[18:36:23] ... Done.
[18:36:23] - Shutting down core
[18:36:23]
[18:36:23] Folding@home Core Shutdown: FINISHED_UNIT
[18:36:27] CoreStatus = 64 (100)
[18:36:27] Sending work to server
[18:36:27] + Attempting to send results
[18:39:33] + Results successfully sent
[18:39:33] Thank you for your contribution to Folding@Home.
[18:39:33] + Number of Units Completed: 643
[18:39:37] - Preparing to get new work unit...
[18:39:37] + Attempting to get work packet
[18:39:37] - Connecting to assignment server
[18:39:39] - Successful: assigned to (0.0.0.0).
[18:39:39] + News From Folding@Home: Welcome to Folding@Home
[18:39:39] Work Unit has an invalid address.
[18:39:39] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
and 4hours later it still persists
[22:00:40] + Attempting to get work packet
[22:00:40] - Connecting to assignment server
[22:00:41] - Successful: assigned to (0.0.0.0).
[22:00:41] + News From Folding@Home: Welcome to Folding@Home
[22:00:41] Work Unit has an invalid address.
[22:00:41] - Error: Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
that 171.67.108.13 error
[22:11:32] + Attempting to get work packet
[22:11:32] - Connecting to assignment server
[22:11:33] - Successful: assigned to (171.67.108.13).
[22:11:33] + News From Folding@Home: Welcome to Folding@Home
[22:11:33] Loaded queue successfully.
[22:11:34] - Error: Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
can't get new WU 171.67.108.13 or 0.0.0.0
Moderators: Site Moderators, FAHC Science Team
Re: can't get new WU 171.67.108.13 or 0.0.0.0
I see that you're running the obsolete V5 client because you're running Windows 2000. If you could upgrade to the current FAH version it would make a big difference for this problem, but you would have to upgrade Windows, too.
Many of the active projects use features that are not available in V5 so you're limited to very few choices of projects. When you are assigned to 0.0.0.0, it means that the Assignment Server has determined that there are no WUs available which can be processed by by your client so you just have to wait. (It may be possible to change settings you're using and find some, but I doubt it.)
Server 171.67.108.13 has a few WUs from time to time as new ones are generated whenever results are returned, but those often go out immediately leaving none to be assigned. The Assignment Server has difficulty keeping up-to-date whether it should assign you to that server or not.
Some of the other servers seem to have WUs which are not being assigned and I don't know why. I'll contact somebody who can figure it out.
If you're not running with the -advmethods flag, then I suggest you add it. Sometimes it helps.
Many of the active projects use features that are not available in V5 so you're limited to very few choices of projects. When you are assigned to 0.0.0.0, it means that the Assignment Server has determined that there are no WUs available which can be processed by by your client so you just have to wait. (It may be possible to change settings you're using and find some, but I doubt it.)
Server 171.67.108.13 has a few WUs from time to time as new ones are generated whenever results are returned, but those often go out immediately leaving none to be assigned. The Assignment Server has difficulty keeping up-to-date whether it should assign you to that server or not.
Some of the other servers seem to have WUs which are not being assigned and I don't know why. I'll contact somebody who can figure it out.
If you're not running with the -advmethods flag, then I suggest you add it. Sometimes it helps.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: can't get new WU 171.67.108.13 or 0.0.0.0
how can I enbale advmethods flag?I don't see such option in my config panel.BTW I still can't get new WU
Re: can't get new WU 171.67.108.13 or 0.0.0.0
Flags are added to the shortcut that starts the client. The WIKI shows other flags, but -advmethods works the same way.
fahwiki.net/index.php/How_do_I_add_flags_using_a_shortcut
Have you made any recent changes to your security software or firewall settings?
fahwiki.net/index.php/How_do_I_add_flags_using_a_shortcut
Have you made any recent changes to your security software or firewall settings?
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: can't get new WU 171.67.108.13 or 0.0.0.0
I have the problem solved temporal,seems it's something to do with my network.The strange thing is after I have enable advmethods and reinstalled client problm still persist.Since the client can connect assign server and transmit the previous finished WU so I don't think my firewall blocked the connection,after disable the it problem still the same.Only after reboot and redial(adsl) finally the client get an WU
assign server is 171.64.65.111
[09:19:18] + Attempting to get work packet
[09:19:18] - Connecting to assignment server
[09:19:18] - Successful: assigned to (0.0.0.0).
[09:19:18] + News From Folding@Home: Welcome to Folding@Home
[09:19:18] Work Unit has an invalid address.
[09:19:18] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[09:19:32] + Attempting to get work packet
[09:19:32] - Connecting to assignment server
Folding@Home Client Shutdown.
--- Opening Log file [August 12 09:25:46]
# Windows Graphical Edition ###################################################
###############################################################################
Folding@Home Client Version 5.03
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: E:\Folding@Home2
Arguments: -advmethods
[09:25:46] - Ask before connecting: No
[09:25:46] - Use IE connection settings: Yes
[09:25:46] - User name: Hisui (Team 0)
[09:25:46] - User ID: 5D4AFA2030185375
[09:25:46] - Machine ID: 1
[09:25:46]
[09:25:46] Loaded queue successfully.
[09:25:46] Initialization complete
[09:25:46] + Benchmarking ...
[09:25:50] - Preparing to get new work unit...
[09:25:50] + Attempting to get work packet
[09:25:50] - Connecting to assignment server
[09:25:51] - Successful: assigned to (171.64.65.111).
[09:25:51] + News From Folding@Home: Welcome to Folding@Home
[09:25:51] Loaded queue successfully.
[09:26:00] + Closed connections
[09:26:00]
[09:26:00] + Processing work unit
[09:26:00] Core required: FahCore_78.exe
[09:26:00] Core found.
[09:26:00] Working on Unit 03 [August 12 09:26:00]
[09:26:00] + Working ...
assign server is 171.64.65.111
[09:19:18] + Attempting to get work packet
[09:19:18] - Connecting to assignment server
[09:19:18] - Successful: assigned to (0.0.0.0).
[09:19:18] + News From Folding@Home: Welcome to Folding@Home
[09:19:18] Work Unit has an invalid address.
[09:19:18] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[09:19:32] + Attempting to get work packet
[09:19:32] - Connecting to assignment server
Folding@Home Client Shutdown.
--- Opening Log file [August 12 09:25:46]
# Windows Graphical Edition ###################################################
###############################################################################
Folding@Home Client Version 5.03
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: E:\Folding@Home2
Arguments: -advmethods
[09:25:46] - Ask before connecting: No
[09:25:46] - Use IE connection settings: Yes
[09:25:46] - User name: Hisui (Team 0)
[09:25:46] - User ID: 5D4AFA2030185375
[09:25:46] - Machine ID: 1
[09:25:46]
[09:25:46] Loaded queue successfully.
[09:25:46] Initialization complete
[09:25:46] + Benchmarking ...
[09:25:50] - Preparing to get new work unit...
[09:25:50] + Attempting to get work packet
[09:25:50] - Connecting to assignment server
[09:25:51] - Successful: assigned to (171.64.65.111).
[09:25:51] + News From Folding@Home: Welcome to Folding@Home
[09:25:51] Loaded queue successfully.
[09:26:00] + Closed connections
[09:26:00]
[09:26:00] + Processing work unit
[09:26:00] Core required: FahCore_78.exe
[09:26:00] Core found.
[09:26:00] Working on Unit 03 [August 12 09:26:00]
[09:26:00] + Working ...
Re: can't get new WU 171.67.108.13 or 0.0.0.0
That's really strange but I'm glad y ou got it sorted out.
Since we really don't have an explanation, i'll give you one more thing to try in case the problem returns.
How much RAM do you have?
Generally there are two client settings that can limit which WUs will be assigned. One is -advmethods. It probably won't hurt if you leave that flag, but you may also choose to remove it since it does enable the assignment of some projects that may be less "mature" so you may see a higher frequency of WUs that contain errors. For this client, that's rarely a big thing either way.
If you create a second shortcut and add the -config flag, it will cause the client to ask you the setup questions again before restarting work. You probably have said you didn't want to receive big WUs. Changing that setting to enable big WUs will also give you access to a wider variety of assignments. With adsl you shouldn't be worried about the size of the upload/download and as long as you have atl least 1MB of RAM, you shouldn't be worried about the demands on real memory.
Since we really don't have an explanation, i'll give you one more thing to try in case the problem returns.
How much RAM do you have?
Generally there are two client settings that can limit which WUs will be assigned. One is -advmethods. It probably won't hurt if you leave that flag, but you may also choose to remove it since it does enable the assignment of some projects that may be less "mature" so you may see a higher frequency of WUs that contain errors. For this client, that's rarely a big thing either way.
If you create a second shortcut and add the -config flag, it will cause the client to ask you the setup questions again before restarting work. You probably have said you didn't want to receive big WUs. Changing that setting to enable big WUs will also give you access to a wider variety of assignments. With adsl you shouldn't be worried about the size of the upload/download and as long as you have atl least 1MB of RAM, you shouldn't be worried about the demands on real memory.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.