Page 4 of 4
Re: 171.67.108.22
Posted: Tue Jul 20, 2010 7:11 pm
by B2K24
I was having trouble getting bigadv's a few days ago then PantherX gave me advice to use Arguments: -bigadv -smp -verbosity 9 in that order.
It worked right away 2 days ago and now there is P2684 and P2685 all going around
Re: 171.67.108.22
Posted: Tue Jul 20, 2010 9:20 pm
by zetachi
kasson wrote:What we see on our side is that the server decides to give you a work unit, starts the send process, and then immediately reports a failure. There are about five users for whom this is happening repeatedly; the rest of the assigns appear to be successful.
Is this a rig that was getting bigadv work units successfully before? Some obvious things to check are client configuration (work unit size set to big?), firewalls, etc.
Only started folding on this rig on Sunday. I've re-configured and set to big for WU size and set new flags as -bigadv -smp -verbosity 9 will see what happens after this WU ( A3-P6701) completes.
Re: 171.67.108.22
Posted: Thu Jul 22, 2010 2:38 pm
by zetachi
OK this seems to have resolved itself. I re did the config and changed the flags and am now getting bigadv units (well 1st one at least) will followup when the 1st one finishes.
Thanks
Re: 171.67.108.22
Posted: Thu Jul 22, 2010 4:05 pm
by kasson
Glad to know it's working now. Do you have a sense of what changed? There are a couple other rigs showing this problem, and referring the owners to this thread could be helpful. At least we can suggest a reconfig.
Re: 171.67.108.22
Posted: Thu Jul 22, 2010 4:14 pm
by zetachi
I re-started with -config made sure big units was yes, confirmed that passkey was entered and correct put no to change advmethods then re set the short cut on desktop to the -bigadv -smp -verbosity 9 flags.