• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

P4s are getting little or no work! Why?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

orion456

Member
Joined
May 31, 2004
Recently my p4s on V6 have been getting almost no work to do. Today I tried switching to v7 but still no work is received. Normally SMPs would pour in, but that isn't happening despite the fact that my i7 machines are working steadily on SMPs.

Any theories why?
 
Mine was that way as well for the last few days. Prior to that I was getting A4 WUs for very low ppd. This morning on my way out to work, I saw that I had gotten an A3 WU on it.
 
If you have V7, try this, set the core count to 8 and let it get a WU (A3,A4) after it get's it, set the core count back to 64, I don't know it if will get WU's on it's own after that but you can get some work out of it.
 
If you have V7, try this, set the core count to 8 and let it get a WU (A3,A4) after it get's it, set the core count back to 64, I don't know it if will get WU's on it's own after that but you can get some work out of it.

Maybe I don't have the switches set properly for v7. Where do I tell it I want big advanced or big beta?
 
Under slot on v7 for each client you'll need to add them in.
"Client-type" I'm using beta flag right now and "max-packet-size" big


https://fah-web.stanford.edu/projects/FAHClient/wiki/ClientDifferencesV6ToV7

^ All the flags you'll ever need.


Here is what I am getting on all my p4 machines. It just keeps repeating over and over.

Code:
17:48:56:Switching to user fahclient
17:48:56:Trying to access database...
17:48:56:Successfully acquired database lock
17:48:56:Enabled folding slot 00: READY cpu:48
17:48:57:WU00:FS00:Connecting to 171.67.108.200:8080
17:48:58:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:48:58:WU00:FS00:Connecting to 171.67.108.204:80
17:48:59:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:48:59:ERROR:WU00:FS00:Exception: Could not get an assignment
17:48:59:WU00:FS00:Connecting to 171.67.108.200:8080
17:48:59:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:48:59:WU00:FS00:Connecting to 171.67.108.204:80
17:49:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:49:00:ERROR:WU00:FS00:Exception: Could not get an assignment
17:49:59:WU00:FS00:Connecting to 171.67.108.200:8080
17:49:59:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:49:59:WU00:FS00:Connecting to 171.67.108.204:80
17:50:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:50:00:ERROR:WU00:FS00:Exception: Could not get an assignment
17:51:36:WU00:FS00:Connecting to 171.67.108.200:8080
17:51:37:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:51:37:WU00:FS00:Connecting to 171.67.108.204:80
17:51:37:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:51:37:ERROR:WU00:FS00:Exception: Could not get an assignment
17:54:14:WU00:FS00:Connecting to 171.67.108.200:8080
17:54:14:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:54:14:WU00:FS00:Connecting to 171.67.108.204:80
17:54:14:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:54:14:ERROR:WU00:FS00:Exception: Could not get an assignment
17:58:28:WU00:FS00:Connecting to 171.67.108.200:8080
17:58:28:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:58:28:WU00:FS00:Connecting to 171.67.108.204:80
17:58:28:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:58:28:ERROR:WU00:FS00:Exception: Could not get an assignment
18:05:19:WU00:FS00:Connecting to 171.67.108.200:8080
18:05:20:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
18:05:20:WU00:FS00:Connecting to 171.67.108.204:80
18:05:20:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:05:20:ERROR:WU00:FS00:Exception: Could not get an assignment
18:16:25:WU00:FS00:Connecting to 171.67.108.200:8080
18:16:25:WARNING:WU00:FS00:Failed to get assignment from
 
Orion I find most of my info here: https://folding.stanford.edu/home/blog/

On may 9 they were having issues with servers 171.67.108.60 and 171.64.65.124 < Could be an on going/moving issue. If you read the 1st post on the page they have been having electrical storm issues.

Normally if a server returns nothing, then a new server is accessed to at least do simple SMP, but that isn't happening. I guess I wait to see what happens.
 
Also if your not getting any WU's, set the core count to 8, let it pickup a WU then set core count back to 64. (48 if using 61xx chips)

PG has been ignoring SMP folding for a while and this seems like one of those lack of resources problems that might not get fixed for some times. I am going to shut down the p4s and check back in the September.
 
Back