Portal
Just started using FaH Tracker this week when I upgraded/added another GPU and decided to try it to make setup easier. Encountered this problem with install and setup of the clients. In browsing the evga forum, quite a few others are having this problem as well. I found a suggestion to add choices for packet size - small, normal, big in the suggestions forum, but to me this represents a bug in the setup of the client.
I have a machine with an overclocked i7-920 and run have run the SMP client for many months now without a problem. When I resetup the SMP client with FaH Tracker, on running the SMP client I got a "work packet too large" error repeatedly. Users on the evga form have as well, all when -bigadv flag is set.
The problem is that for users with large amt of memory, in order to run the larger SMP WU, file packet size MUST be set to big. (bigpackets=big in client.cfg)Once I redid the client.cfg file with another program, my 8955 point WU (WU6901) loaded without a problem. (Although FaH Tracker does not show the correct points for expected completion time of the WU, that's another bug I see reported already.)
Seems like FaH Tracker needs to either have an option to set the bigpackets in client.cfg, or automatically set it to big, with a warning to users about file size, when the -bigadv flag is set, or both.
--- Opening Log file [March 23 22:30:24 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.34
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\gary\AppData\Local\Temp\7zOB79C.tmp\SMP
Executable: C:\Users\gary\AppData\Local\Temp\7zOB79C.tmp\FAH.exe
Arguments: -oneunit -forceasm -smp -bigadv -verbosity 9
[22:30:24] - Ask before connecting: No
[22:30:24] - User name: DaBoSSs (Team 33)
[22:30:24] - User ID:
[22:30:24] - Machine ID: 2
[22:30:24]
[22:30:24] Work directory not found. Creating...
[22:30:24] Could not open work queue, generating new queue...
[22:30:24] - Preparing to get new work unit...
[22:30:24] - Autosending finished units... [March 23 22:30:24 UTC]
[22:30:24] Cleaning up work directory
[22:30:24] Trying to send all finished work units
[22:30:24] + No unsent completed units remaining.
[22:30:24] - Autosend completed
[22:30:24] + Attempting to get work packet
[22:30:24] Passkey found
[22:30:24] - Will indicate memory of 6135 MB
[22:30:24] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 4
[22:30:24] - Connecting to assignment server
[22:30:24] Connecting to http://assign.stanford.edu:8080/
[22:30:26] Posted data.
[22:30:26] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[22:30:26] + News From Folding@Home: Welcome to Folding@Home
[22:30:26] Loaded queue successfully.
[22:30:26] Sent data
[22:30:26] Connecting to http://171.67.108.22:8080/
[22:30:34] Posted data.
[22:30:34] Initial: 0000; - Error: Work packet too large
[22:30:34] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[22:30:54] + Attempting to get work packet
[22:30:54] Passkey found
[22:30:54] - Will indicate memory of 6135 MB
[22:30:54] - Connecting to assignment server
[22:30:54] Connecting to http://assign.stanford.edu:8080/
[22:30:54] Posted data.
[22:30:54] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[22:30:54] + News From Folding@Home: Welcome to Folding@Home
[22:30:54] Loaded queue successfully.
[22:30:54] Sent data
[22:30:54] Connecting to http://171.67.108.22:8080/
[22:31:06] Posted data.
[22:31:06] Initial: 0000; - Error: Work packet too large
[22:31:06] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
I have a machine with an overclocked i7-920 and run have run the SMP client for many months now without a problem. When I resetup the SMP client with FaH Tracker, on running the SMP client I got a "work packet too large" error repeatedly. Users on the evga form have as well, all when -bigadv flag is set.
The problem is that for users with large amt of memory, in order to run the larger SMP WU, file packet size MUST be set to big. (bigpackets=big in client.cfg)Once I redid the client.cfg file with another program, my 8955 point WU (WU6901) loaded without a problem. (Although FaH Tracker does not show the correct points for expected completion time of the WU, that's another bug I see reported already.)
Seems like FaH Tracker needs to either have an option to set the bigpackets in client.cfg, or automatically set it to big, with a warning to users about file size, when the -bigadv flag is set, or both.
--- Opening Log file [March 23 22:30:24 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.34
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\gary\AppData\Local\Temp\7zOB79C.tmp\SMP
Executable: C:\Users\gary\AppData\Local\Temp\7zOB79C.tmp\FAH.exe
Arguments: -oneunit -forceasm -smp -bigadv -verbosity 9
[22:30:24] - Ask before connecting: No
[22:30:24] - User name: DaBoSSs (Team 33)
[22:30:24] - User ID:
[22:30:24] - Machine ID: 2
[22:30:24]
[22:30:24] Work directory not found. Creating...
[22:30:24] Could not open work queue, generating new queue...
[22:30:24] - Preparing to get new work unit...
[22:30:24] - Autosending finished units... [March 23 22:30:24 UTC]
[22:30:24] Cleaning up work directory
[22:30:24] Trying to send all finished work units
[22:30:24] + No unsent completed units remaining.
[22:30:24] - Autosend completed
[22:30:24] + Attempting to get work packet
[22:30:24] Passkey found
[22:30:24] - Will indicate memory of 6135 MB
[22:30:24] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 4
[22:30:24] - Connecting to assignment server
[22:30:24] Connecting to http://assign.stanford.edu:8080/
[22:30:26] Posted data.
[22:30:26] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[22:30:26] + News From Folding@Home: Welcome to Folding@Home
[22:30:26] Loaded queue successfully.
[22:30:26] Sent data
[22:30:26] Connecting to http://171.67.108.22:8080/
[22:30:34] Posted data.
[22:30:34] Initial: 0000; - Error: Work packet too large
[22:30:34] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[22:30:54] + Attempting to get work packet
[22:30:54] Passkey found
[22:30:54] - Will indicate memory of 6135 MB
[22:30:54] - Connecting to assignment server
[22:30:54] Connecting to http://assign.stanford.edu:8080/
[22:30:54] Posted data.
[22:30:54] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[22:30:54] + News From Folding@Home: Welcome to Folding@Home
[22:30:54] Loaded queue successfully.
[22:30:54] Sent data
[22:30:54] Connecting to http://171.67.108.22:8080/
[22:31:06] Posted data.
[22:31:06] Initial: 0000; - Error: Work packet too large
[22:31:06] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
