Page 1 of 4
128.143.48.226 : server reports problem with unit
Posted: Mon Mar 02, 2009 11:03 pm
by Trotador
Hi,
I'm getting the logs below when trying to return the results of several WUs of these proteins. They have been folded at work either on a centrino laptop or a P4 and I'm returning the data at home. No clue what is the problem, if i try to send them again the client says there is no unsent unit ...
I tried several times and always got the same message, on the other hand I was able to return succesfully one 3861 (Run 396, Clone 0, Gen 0) folded on another P4 of the office
Thanks for the help.
Code: Select all
--- Opening Log file [March 2 22:40:15 UTC]
# Windows CPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\PROTEINAS\SpaceFolder
Executable: C:\PROTEINAS\SpaceFolder\[email protected]
Arguments: -local -forceasm -verbosity 9 -advmethods -send all
Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.
[22:40:15] - Ask before connecting: No
[22:40:15] - User name: SpaceFolder (Team 130187)
[22:40:15] - User ID: 615588894D171545
[22:40:15] - Machine ID: 3
[22:40:15]
[22:40:16] Loaded queue successfully.
[22:40:16] Attempting to return result(s) to server...
[22:40:16] Trying to send all finished work units
[22:40:16] Project: 3861 (Run 399, Clone 0, Gen 0)
[22:40:16] + Attempting to send results [March 2 22:40:16 UTC]
[22:40:16] - Reading file work/wuresults_01.dat from core
[22:40:16] (Read 1066194 bytes from disk)
[22:40:16] Connecting to http://128.143.48.226:8080/
[22:40:49] Posted data.
[22:40:49] Initial: 0000; - Uploaded at ~31 kB/s
[22:40:49] - Averaged speed for that direction ~31 kB/s
[22:40:49] - Server reports problem with unit.
[22:40:49] + Sent 0 of 1 completed units to the server
[22:40:49] - Failed to send all units to server
[22:40:49] ***** Got a SIGTERM signal (2)
[22:40:49] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [March 2 22:47:08 UTC]
# Windows CPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\PROTEINAS\SpaceFolder
Executable: C:\PROTEINAS\SpaceFolder\[email protected]
Arguments: -local -verbosity 9 -send all
[22:47:08] - Ask before connecting: No
[22:47:08] - User name: SpaceFolder (Team 130187)
[22:47:08] - User ID: 615588894D171545
[22:47:08] - Machine ID: 3
[22:47:08]
[22:47:08] Loaded queue successfully.
[22:47:08] Deleting incompletely fetched item (4) from queue position #2
[22:47:08] - Warning: Could not delete all work unit files (2): Core file absent
[22:47:08] Attempting to return result(s) to server...
[22:47:08] Trying to send all finished work units
[22:47:08] Project: 3860 (Run 391, Clone 0, Gen 0)
[22:47:08] + Attempting to send results [March 2 22:47:08 UTC]
[22:47:08] - Reading file work/wuresults_01.dat from core
[22:47:08] (Read 2651508 bytes from disk)
[22:47:08] Connecting to http://128.143.48.226:8080/
[22:48:29] Posted data.
[22:48:29] Initial: 0000; - Uploaded at ~31 kB/s
[22:48:29] - Averaged speed for that direction ~31 kB/s
[22:48:29] - Server reports problem with unit.
[22:48:29] + Sent 0 of 1 completed units to the server
[22:48:29] - Failed to send all units to server
[22:48:29] ***** Got a SIGTERM signal (2)
[22:48:29] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [March 2 22:51:50 UTC]
# Windows CPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\PROTEINAS\SpaceFolder
Executable: C:\PROTEINAS\SpaceFolder\[email protected]
Arguments: -local -verbosity 9 -send all
[22:51:50] - Ask before connecting: No
[22:51:50] - User name: SpaceFolder (Team 130187)
[22:51:50] - User ID: 615588894D171545
[22:51:50] - Machine ID: 3
[22:51:50]
[22:51:51] Loaded queue successfully.
[22:51:51] Deleting incompletely fetched item (4) from queue position #2
[22:51:51] - Warning: Could not delete all work unit files (2): Core file absent
[22:51:51] Attempting to return result(s) to server...
[22:51:51] Trying to send all finished work units
[22:51:51] Project: 3860 (Run 384, Clone 0, Gen 0)
[22:51:51] + Attempting to send results [March 2 22:51:51 UTC]
[22:51:51] - Reading file work/wuresults_01.dat from core
[22:51:51] (Read 2653106 bytes from disk)
[22:51:51] Connecting to http://128.143.48.226:8080/
[22:53:12] Posted data.
[22:53:12] Initial: 0000; - Uploaded at ~31 kB/s
[22:53:12] - Averaged speed for that direction ~31 kB/s
[22:53:12] - Server reports problem with unit.
[22:53:12] + Sent 0 of 1 completed units to the server
[22:53:12] - Failed to send all units to server
[22:53:12] ***** Got a SIGTERM signal (2)
[22:53:12] Killing all core threads
Folding@Home Client Shutdown.
Re: P3860 and P3861 : server reports problem with unit
Posted: Wed Mar 04, 2009 7:26 pm
by only4u
I met the same issue. I could send result a few days ago but now I cannot send result of WU 3864. Server status is full acepting
.
Re: 128.143.48.226 : server reports problem with unit
Posted: Thu Mar 05, 2009 12:17 am
by toTOW
Thread title edited, and thread moved to "Issues with specific server" forum.
Re: 128.143.48.226 : server reports problem with unit
Posted: Thu Mar 05, 2009 10:57 pm
by Trotador
Thanks for editing and puting in due form the post toTOW. I hesitated where to write the post but i guess it is now where it should have been .).
So another guess is that you are looking to the server, aren´t you?
Re: 128.143.48.226 : server reports problem with unit
Posted: Wed Mar 11, 2009 10:10 am
by only4u
Noone else met this issue???
Re: 128.143.48.226 : server reports problem with unit
Posted: Sat Mar 14, 2009 11:37 am
by Trotador
Same message still. No news?
Re: 128.143.48.226 : server reports problem with unit
Posted: Sun Mar 15, 2009 3:46 pm
by dnamechanic
only4u wrote:Noone else met this issue???
Similar observations here.
Log indications for several work units: p3860 through p3864, are similar to those initially posted by Trotador.
This is an example:
[16:34:15] Loaded queue successfully.
[16:34:15] Attempting to return result(s) to server...
[16:34:15] Trying to send all finished work units
[16:34:15] Project: 3864 (Run 485, Clone 4, Gen 0)
[16:34:15] + Attempting to send results [March 15 16:34:15 UTC]
[16:34:15] - Reading file work/wuresults_01.dat from core
[16:34:15] (Read 2562762 bytes from disk)
[16:34:15] Connecting to
http://128.143.48.226:8080/
[16:34:26] Posted data.
[16:34:26] Initial: 0000; - Uploaded at ~227 kB/s
[16:34:26] - Averaged speed for that direction ~227 kB/s
[16:34:26] - Server reports problem with unit.
[16:34:26] + Sent 0 of 1 completed units to the server
[16:34:26] - Failed to send all units to server
Re: 128.143.48.226 : server reports problem with unit
Posted: Mon Mar 16, 2009 1:37 pm
by dnamechanic
This problem may be related to differing Machine ID: #'s (or possibly other parameters) on the download computer versus the computer that actually folded the work units.
On a few troublesome work units (work units that "Server reports problem with unit");
This was tried:
- Changing the sending computer's Machine ID: # to match the download Machine ID: # for the same work unit, then
- Resend of an original copy of the completed work unit, (before being rejected by the server 128.143.48.226:8080)
The work units were then received OK at the Stanford server.
The example log below, shows the same work unit that was rejected by the server in the previous post.
[12:54:00] Loaded queue successfully.
[12:54:00] Attempting to return result(s) to server...
[12:54:00] Trying to send all finished work units
[12:54:00] Project: 3864 (Run 485, Clone 4, Gen 0)
[12:54:00] + Attempting to send results [March 16 12:54:00 UTC]
[12:54:00] - Reading file work/wuresults_01.dat from core
[12:54:00] (Read 2562762 bytes from disk)
[12:54:00] Connecting to
http://128.143.48.226:8080/
[12:54:11] Posted data.
[12:54:11] Initial: 0000; - Uploaded at ~227 kB/s
[12:54:11] - Averaged speed for that direction ~227 kB/s
[12:54:11] + Results successfully sent
[12:54:11] Thank you for your contribution to Folding@Home.
[12:54:11] + Number of Units Completed: 1083
[12:54:12] + Sent 1 of 1 completed units to the server
The difference between this re-send and the previous (posted yesterday) was that the Machine ID: # of the sending client was changed to match the Machine ID: # of the client that downloaded the work unit.
Re: 128.143.48.226 : server reports problem with unit
Posted: Mon Mar 16, 2009 7:58 pm
by toTOW
I don't know what your username is, but there is only one report in the DB for 0 points of credit for Project: 3864 (Run 485, Clone 4, Gen 0).
Re: 128.143.48.226 : server reports problem with unit
Posted: Mon Mar 16, 2009 8:40 pm
by Trotador
I've tried with different IDs from different locations (i.e. ISPs) and always the same result already posted.
Re: 128.143.48.226 : server reports problem with unit
Posted: Mon Mar 16, 2009 11:25 pm
by mrshirts
Hi, all-
I didn't see this because it wasn't in the specific server section -- apologies. This server is using the newest code, and might have a few quirks that were not present in the older server code.
Am I correct in summarizing by saying that the problem seems to be that the machine ID did not match -- when it was changed to match the machine it was downloaded on, then it worked? If so, is this different than behavior that was present before?
Thanks!
Re: 128.143.48.226 : server reports problem with unit
Posted: Tue Mar 17, 2009 12:12 am
by dnamechanic
mrshirts wrote: ...server is using the newest code, and might have a few quirks that were not present in the older server code.
Am I correct in summarizing by saying that the problem seems to be that the machine ID did not match -- when it was changed to match the machine it was downloaded on, then it worked?
Yes, your summary is correct for the work units mentioned in my earlier post.
Apparently that does not always work (based on Trotador's comments), and I have since tried a couple of other completed work units that matching ID #'s seem make no difference.
If so, is this different than behavior that was present before?
Yes it is quite different.
In the past, as I recall, it did not seem to matter where a work unit was downloaded and where it was completed. Credit was seen to be obtained if the username and team name matched (whether from an entirely different machine, different ISP, different machine ID #, or even a different registry UserID).
toTOW wrote:... but there is only one report in the DB for 0 points of credit for Project: 3864 (Run 485, Clone 4, Gen 0).
Could it be that once the server has rejected a work unit, that it no longer issues credit for that work unit from that contributor?
For example, I recall a few years back a certain type of work unit would occasionally fail on an Intel notebook, and if the notebook happened to have Internet connectivity, it would send partial results back to Stanford. I would notice and move the original unworked work unit to an AMD machine and complete the work unit properly. Afterward, I would carefully watch points accredited, no credit was ever given for the finally completed work unit.
Re: 128.143.48.226 : server reports problem with unit
Posted: Tue Mar 17, 2009 7:00 am
by only4u
Any workaround to fix this issue? I have some offline PCs without internet connection so I copied the WUs from online PC to fold. A few WUs result are waiting.
Re: 128.143.48.226 : server reports problem with unit
Posted: Tue Mar 17, 2009 11:13 am
by toTOW
If you follow these recommendations to copy your WUs, you shouldn't have issue returning them :
http://fahwiki.net/index.php/Sneakernetting
Re: 128.143.48.226 : server reports problem with unit
Posted: Tue Mar 17, 2009 12:46 pm
by dnamechanic
Thanks toTOW, for the link to the FahWiki, it is a great resource.
I never specifically used this "sneakernetting" procedure, in fact it did not exist when I started using non-Internet connected computers for folding.
But, have successfullly "sneakernetted" WUs for several years, from notebook computers at same ISP, and computers with intermittent connectivity at separate ISPs, and earlier from full-up lab computers that had no internet connectivity at all.
The several "flags tips" and the "client.cfg tips" given in the Wiki are usually necessary for any non-standard client setup, so they probably do not directly affect the acceptance of usual work units.
Most of the tips seem helpful and even necessary to fold a work unit at all on a separate machine.
Currently my machines use the same ISP and the sneakernetted notebooks have the cloned "UserID" in the registry. In other words the registry "UserID" in the notebooks is identical to the "UserID" in the machine that downloads the work units.
So, it doesn't seem that any existing "general rules" will help with these troublesome WUs.
These work units from 128.143.48.226 are the only ones that have ever (meaning ~6 years) demonstrated this particular behaviour.