Re: 171.67.108.22
Posted: Thu Jul 08, 2010 12:47 am
Update: My machine picked up a -bigadv 2684 today around 17:12 PDT, so it looks like all is better now. Like PantherX before me though, it took two tries.
Folding Forum
Community driven support forum for Folding@home
https://foldingforum.org/
171.67.108.22
Page 2 of 4
Re: 171.67.108.22
Posted: Thu Jul 08, 2010 9:23 am
I think it could be due to the size of these WU's - mine takes 20 minutes to return a completed WU (~100Mb) and download is ~20Mb.
Re: 171.67.108.22
Posted: Fri Jul 09, 2010 7:06 pm
Have two machines (i7 920 @ 3.8 Ghz) that I swictched to -bigadv Win SMP and could not any WU for the last three-four days.
Here is one as of yesterday:
Here is one as of yesterday:
Code: Select all
--- Opening Log file [July 7 21:31:12 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.30
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01\Folding@home-Win32-x86.exe
Arguments: -bigadv -smp 7 -verbosity 9
[21:31:12] - Ask before connecting: No
[21:31:12] - User name: bogmali (Team 50711)
[21:31:12] - User ID: 7DBDB48722B3EEB3
[21:31:12] - Machine ID: 1
[21:31:12]
[21:31:12] Loaded queue successfully.
[21:31:12] - Preparing to get new work unit...
[21:31:12] - Autosending finished units... [July 7 21:31:12 UTC]
[21:31:12] Cleaning up work directory
[21:31:12] Trying to send all finished work units
[21:31:12] + Attempting to get work packet
[21:31:12] + No unsent Restarted today and the same thing is happening:
[code]
--- Opening Log file [July 9 18:48:02 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.30
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01\Folding@home-Win32-x86.exe
Arguments: -smp 7 -bigadv -verbosity 9
[18:48:02] - Ask before connecting: No
[18:48:02] - User name: bogmali (Team 50711)
[18:48:02] - User ID: 7DBDB48722B3EEB3
[18:48:02] - Machine ID: 1
[18:48:02]
[18:48:03] Loaded queue successfully.
[18:48:03] - Preparing to get new work unit...
[18:48:03] - Autosending finished units... [July 9 18:48:03 UTC]
[18:48:03] Cleaning up work directory
[18:48:03] Trying to send all finished work units
[18:48:03] + Attempting to get work packet
[18:48:03] + No unsent completed units remaining.
[18:48:03] Passkey found
[18:48:03] - Autosend completed
[18:48:03] - Will indicate memory of 12279 MB
[18:48:03] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5
[18:48:03] - Connecting to assignment server
[18:48:03] Connecting to http://assign.stanford.edu:8080/
[18:48:03] Posted data.
[18:48:03] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[18:48:03] + News From Folding@Home: Welcome to Folding@Home
[18:48:03] Loaded queue successfully.
[18:48:03] Sent data
[18:48:03] Connecting to http://171.67.108.22:8080/
[18:48:04] Posted data.
[18:48:05] Initial: 0000; + Could not connect to Work Server
[18:48:05] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:48:07] Killing all core threads
[18:48:07] Could not get process id information. Please kill core process manually
Folding@Home Client Shutdown at user request.
[18:48:07] ***** Got a SIGTERM signal (2)
[18:48:07] Killing all core threads
[18:48:07] Could not get process id information. Please kill core process manually
Folding@Home Client Shutdown.
--- Opening Log file [July 9 18:52:55 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.30
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01\Folding@home-Win32-x86.exe
Arguments: -smp -bigadv -oneunit
[18:52:55] - Ask before connecting: No
[18:52:55] - User name: bogmali (Team 50711)
[18:52:55] - User ID: 7DBDB48722B3EEB3
[18:52:55] - Machine ID: 1
[18:52:55]
[18:52:55] Loaded queue successfully.
[18:52:55] - Preparing to get new work unit...
[18:52:55] Cleaning up work directory
[18:52:55] + Attempting to get work packet
[18:52:55] Passkey found
[18:52:55] - Connecting to assignment server
[18:52:55] - Successful: assigned to (171.67.108.22).
[18:52:55] + News From Folding@Home: Welcome to Folding@Home
[18:52:55] Loaded queue successfully.
[18:52:57] + Could not connect to Work Server
[18:52:57] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:53:07] + Attempting to get work packet
[18:53:07] Passkey found
[18:53:07] - Connecting to assignment server
[18:53:07] - Successful: assigned to (171.67.108.22).
[18:53:07] + News From Folding@Home: Welcome to Folding@Home
[18:53:07] Loaded queue successfully.
[18:53:09] + Could not connect to Work Server
[18:53:09] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[18:53:27] + Attempting to get work packet
[18:53:27] Passkey found
[18:53:27] - Connecting to assignment server
[18:53:27] - Successful: assigned to (171.67.108.22).
[18:53:27] + News From Folding@Home: Welcome to Folding@Home
[18:53:27] Loaded queue successfully.
[18:53:29] + Could not connect to Work Server
[18:53:29] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[18:54:01] + Attempting to get work packet
[18:54:01] Passkey found
[18:54:01] - Connecting to assignment server
[18:54:02] - Successful: assigned to (171.67.108.22).
[18:54:02] + News From Folding@Home: Welcome to Folding@Home
[18:54:02] Loaded queue successfully.
[18:54:03] + Could not connect to Work Server
[18:54:03] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[18:54:44] + Attempting to get work packet
[18:54:44] Passkey found
[18:54:44] - Connecting to assignment server
[18:54:44] - Successful: assigned to (171.67.108.22).
[18:54:44] + News From Folding@Home: Welcome to Folding@Home
[18:54:44] Loaded queue successfully.
[18:54:46] + Could not connect to Work Server
[18:54:46] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[18:56:17] + Attempting to get work packet
[18:56:17] Passkey found
[18:56:17] - Connecting to assignment server
[18:56:18] - Successful: assigned to (171.67.108.22).
[18:56:18] + News From Folding@Home: Welcome to Folding@Home
[18:56:18] Loaded queue successfully.
[18:56:20] + Could not connect to Work Server
[18:56:20] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[18:59:12] + Attempting to get work packet
[18:59:12] Passkey found
[18:59:12] - Connecting to assignment server
[18:59:12] - Successful: assigned to (171.67.108.22).
[18:59:12] + News From Folding@Home: Welcome to Folding@Home
[18:59:12] Loaded queue successfully.
[18:59:14] + Could not connect to Work Server
[18:59:14] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
Re: 171.67.108.22
Posted: Fri Jul 09, 2010 7:08 pm
And here is todays log:
Code: Select all
--- Opening Log file [July 9 18:48:02 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.30
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01\Folding@home-Win32-x86.exe
Arguments: -smp 7 -bigadv -verbosity 9
[18:48:02] - Ask before connecting: No
[18:48:02] - User name: bogmali (Team 50711)
[18:48:02] - User ID: 7DBDB48722B3EEB3
[18:48:02] - Machine ID: 1
[18:48:02]
[18:48:03] Loaded queue successfully.
[18:48:03] - Preparing to get new work unit...
[18:48:03] - Autosending finished units... [July 9 18:48:03 UTC]
[18:48:03] Cleaning up work directory
[18:48:03] Trying to send all finished work units
[18:48:03] + Attempting to get work packet
[18:48:03] + No unsent completed units remaining.
[18:48:03] Passkey found
[18:48:03] - Autosend completed
[18:48:03] - Will indicate memory of 12279 MB
[18:48:03] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5
[18:48:03] - Connecting to assignment server
[18:48:03] Connecting to http://assign.stanford.edu:8080/
[18:48:03] Posted data.
[18:48:03] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[18:48:03] + News From Folding@Home: Welcome to Folding@Home
[18:48:03] Loaded queue successfully.
[18:48:03] Sent data
[18:48:03] Connecting to http://171.67.108.22:8080/
[18:48:04] Posted data.
[18:48:05] Initial: 0000; + Could not connect to Work Server
[18:48:05] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:48:07] Killing all core threads
[18:48:07] Could not get process id information. Please kill core process manually
Folding@Home Client Shutdown at user request.
[18:48:07] ***** Got a SIGTERM signal (2)
[18:48:07] Killing all core threads
[18:48:07] Could not get process id information. Please kill core process manually
Folding@Home Client Shutdown.
--- Opening Log file [July 9 18:52:55 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.30
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files (x86)\Folding@Home Windows SMP Client V1.01\Folding@home-Win32-x86.exe
Arguments: -smp -bigadv -oneunit
[18:52:55] - Ask before connecting: No
[18:52:55] - User name: bogmali (Team 50711)
[18:52:55] - User ID: 7DBDB48722B3EEB3
[18:52:55] - Machine ID: 1
[18:52:55]
[18:52:55] Loaded queue successfully.
[18:52:55] - Preparing to get new work unit...
[18:52:55] Cleaning up work directory
[18:52:55] + Attempting to get work packet
[18:52:55] Passkey found
[18:52:55] - Connecting to assignment server
[18:52:55] - Successful: assigned to (171.67.108.22).
[18:52:55] + News From Folding@Home: Welcome to Folding@Home
[18:52:55] Loaded queue successfully.
[18:52:57] + Could not connect to Work Server
[18:52:57] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:53:07] + Attempting to get work packet
[18:53:07] Passkey found
[18:53:07] - Connecting to assignment server
[18:53:07] - Successful: assigned to (171.67.108.22).
[18:53:07] + News From Folding@Home: Welcome to Folding@Home
[18:53:07] Loaded queue successfully.
[18:53:09] + Could not connect to Work Server
[18:53:09] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[18:53:27] + Attempting to get work packet
[18:53:27] Passkey found
[18:53:27] - Connecting to assignment server
[18:53:27] - Successful: assigned to (171.67.108.22).
[18:53:27] + News From Folding@Home: Welcome to Folding@Home
[18:53:27] Loaded queue successfully.
[18:53:29] + Could not connect to Work Server
[18:53:29] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[18:54:01] + Attempting to get work packet
[18:54:01] Passkey found
[18:54:01] - Connecting to assignment server
[18:54:02] - Successful: assigned to (171.67.108.22).
[18:54:02] + News From Folding@Home: Welcome to Folding@Home
[18:54:02] Loaded queue successfully.
[18:54:03] + Could not connect to Work Server
[18:54:03] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[18:54:44] + Attempting to get work packet
[18:54:44] Passkey found
[18:54:44] - Connecting to assignment server
[18:54:44] - Successful: assigned to (171.67.108.22).
[18:54:44] + News From Folding@Home: Welcome to Folding@Home
[18:54:44] Loaded queue successfully.
[18:54:46] + Could not connect to Work Server
[18:54:46] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[18:56:17] + Attempting to get work packet
[18:56:17] Passkey found
[18:56:17] - Connecting to assignment server
[18:56:18] - Successful: assigned to (171.67.108.22).
[18:56:18] + News From Folding@Home: Welcome to Folding@Home
[18:56:18] Loaded queue successfully.
[18:56:20] + Could not connect to Work Server
[18:56:20] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[18:59:12] + Attempting to get work packet
[18:59:12] Passkey found
[18:59:12] - Connecting to assignment server
[18:59:12] - Successful: assigned to (171.67.108.22).
[18:59:12] + News From Folding@Home: Welcome to Folding@Home
[18:59:12] Loaded queue successfully.
[18:59:14] + Could not connect to Work Server
[18:59:14] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[19:04:40] + Attempting to get work packet
[19:04:40] Passkey found
[19:04:40] - Connecting to assignment server
[19:04:41] - Successful: assigned to (171.67.108.22).
[19:04:41] + News From Folding@Home: Welcome to Folding@Home
[19:04:41] Loaded queue successfully.
[19:04:43] + Could not connect to Work Server
[19:04:43] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
Re: 171.67.108.22
Posted: Fri Jul 09, 2010 11:00 pm
So let me get this straight, You guys shutdown the -bigadv for Linux. and now there is no work for Windows either. Unfreaking believeable. This place is going to hell in a handbag. 
Re: 171.67.108.22
Posted: Sun Jul 11, 2010 4:53 am
My machine finished a 2684 and uploaded it just fine. Now, it's waiting for a -bigadv WU. 
I guess I'll switch it to -advmethods for a while again.
I guess I'll switch it to -advmethods for a while again.Re: 171.67.108.22
Posted: Sun Jul 11, 2010 9:18 pm
Tried again for an hour today at 13:12 PDT for 10 tries to get a -bigadv WU to no avail. Switched again to -advmethods.
Re: 171.67.108.22
Posted: Mon Jul 12, 2010 3:00 am
How lovely picked up a Project 6701 running with flags -verbosity 9 -smp -bigadv
I guess it's fair to randomize it for everyone instead of people switching between -bigadv and -advmethods
looks like it's all for the better.
I guess it's fair to randomize it for everyone instead of people switching between -bigadv and -advmethods
looks like it's all for the better.
Re: 171.67.108.22
Posted: Tue Jul 13, 2010 11:21 pm
I may be wrong on this, but, does just -smp default to maximum cores/threads or do you need a number there to utilize maximum cores/threads?B2K24 wrote:How lovely picked up a Project 6701 running with flags -verbosity 9 -smp -bigadv
I guess it's fair to randomize it for everyone instead of people switching between -bigadv and -advmethods
looks like it's all for the better.
Also, been two days since I've picked up a 2684, been folding other GRO-A3's with a 7-10,000 ppd hit per computer. Usually get 17-20,000 ppd and now getting 10,000 ppd.
Fold on
Rick
Re: 171.67.108.22
Posted: Wed Jul 14, 2010 12:10 am
You're correct. -smp without a number is identical to setting it to the (maximum) number detected on your machine.rickoic wrote:I may be wrong on this, but, does just -smp default to maximum cores/threads or do you need a number there to utilize maximum cores/threads?
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 1:34 pm
any updates on this server? I have not been able to d/l a new WU in over 24hrs. I just had to reconfigure and turn off -bigadv and was able to d/l an a3 core and wu
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 4:55 pm
You didn't specify which OS you are running and you didn't include a segment of FAHlog.txt showing the problem, so I cannot be sure exactly what problem you're having. I'll make some guesses, and if I'm wrong, please give more details so we can understand your questions.zetachi wrote:any updates on this server? I have not been able to d/l a new WU in over 24hrs. I just had to reconfigure and turn off -bigadv and was able to d/l an a3 core and wu
As far as updates are concerned, you can always find them on the serverstat page (link above) where you'll see that this specific server has very few WUs to distribute right now. That's a dynamic condition, though, because when a WU is uploaded, the server generates a new one so unless you know how may WUs from that server are currently being worked on, you don't know how many new WUs will be generated. It's also possible that the projects on that server are nearing completion and different projects will appear on that server soon. It is impossible to predict whether they will be bigadv or not.
I think you're asking the wrong question, though. I don't think you really want to know about that specific single server. Apparently you really want to know about the availability of bigadv WUs and/or why you're not getting any new assignments.
The bigadv WUs have been shut off temporarily for Linux. The bigadv WUs for windows are in relatively short supply. (Those announcements are elsewhere in the forum.) Those announcements never mention a specific server.
You need to remember that the Assignment Server is responsible for finding an assignment for you, whether it's from that specific server or from some other server. If there are no assignments that match your exact request, it's also supposed to give you the nearest match to your request which may not be a -bigadv assignment.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:03 pm
Sorry. Running Windows 7 Ultimate I7-930
Code: Select all
Launch directory: C:\Users\Doug\SMP 3
Executable: C:\Users\Doug\SMP 3\SMP 3.exe
Arguments: -local -forceasm -smp -bigadv
[13:01:42] - Ask before connecting: No
[13:01:42] - User name: Zetachi (Team 734)
[13:01:42] - User ID:
[13:01:42] - Machine ID: 3
[13:01:42]
[13:01:42] Work directory not found. Creating...
[13:01:42] Loaded queue successfully.
[13:01:42] - Preparing to get new work unit...
[13:01:42] Cleaning up work directory
[13:01:42] + Attempting to get work packet
[13:01:42] Passkey found
[13:01:42] - Connecting to assignment server
[13:01:43] - Successful: assigned to (171.67.108.22).
[13:01:43] + News From Folding@Home: Welcome to Folding@Home
[13:01:43] Loaded queue successfully.
[13:01:54] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[13:02:12] + Attempting to get work packet
[13:02:12] Passkey found
[13:02:12] - Connecting to assignment server
[13:02:13] - Successful: assigned to (171.67.108.22).
[13:02:13] + News From Folding@Home: Welcome to Folding@Home
[13:02:13] Loaded queue successfully.
[13:02:26] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[13:02:49] + Attempting to get work packet
[13:02:49] Passkey found
[13:02:49] - Connecting to assignment server
[13:02:50] - Successful: assigned to (171.67.108.22).
[13:02:50] + News From Folding@Home: Welcome to Folding@Home
[13:02:50] Loaded queue successfully.
[13:03:00] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[13:03:21] + Attempting to get work packet
[13:03:21] Passkey found
[13:03:21] - Connecting to assignment server
[13:03:23] - Successful: assigned to (171.67.108.22).
[13:03:23] + News From Folding@Home: Welcome to Folding@Home
[13:03:23] Loaded queue successfully.
[13:03:34] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[13:04:20] + Attempting to get work packet
[13:04:20] Passkey found
[13:04:20] - Connecting to assignment server
[13:04:21] - Successful: assigned to (171.67.108.22).
[13:04:21] + News From Folding@Home: Welcome to Folding@Home
[13:04:21] Loaded queue successfully.
[13:04:32] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[13:06:03] + Attempting to get work packet
[13:06:03] Passkey found
[13:06:03] - Connecting to assignment server
[13:06:04] - Successful: assigned to (171.67.108.22).
[13:06:04] + News From Folding@Home: Welcome to Folding@Home
[13:06:04] Loaded queue successfully.
[13:06:13] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[13:09:06] + Attempting to get work packet
[13:09:06] Passkey foundRe: 171.67.108.22
Posted: Mon Jul 19, 2010 5:11 pm
@zetachi: you can remove the -local flag as it is by default a feature in v6 Clients and above. You can also remove the -forceasm as the FahCore_a3 is hard-coded to use maximum features of the CPU.
BTW next time you post your FAHLog, make sure to remove your User ID for security/privacy reasons and use the Code button so that the FAHLog appears like this:
BTW next time you post your FAHLog, make sure to remove your User ID for security/privacy reasons and use the Code button so that the FAHLog appears like this:
Code: Select all
FAHLogRe: 171.67.108.22
Posted: Mon Jul 19, 2010 5:15 pm
thanks for the heads up and flag help 