Page 1 of 1

problems with 171.67.108.24

Posted: Wed Dec 09, 2009 9:36 pm
by matheusber
hail,

I have this queue:

Code: Select all

CURRENT QUEUE:
00  EMPTY
01  EMPTY
02  EMPTY
03  DONE      a2 171.67.108.24:8080  December 6 18:53->December 7 07:07
[   P2671R8C23G145 ]
04  DONE      a2 171.67.108.24:8080  December 7 07:55->December 7 20:51
[  P2671R36C28G145 ]
05  DONE      a2 171.67.108.24:8080  December 7 20:52->December 8 09:14
[   P2671R42C3G145 ]
06  DONE      a2 171.67.108.24:8080  December 8 11:06->December 9 01:33
[  P2671R26C42G146 ]
07  DONE      a2 171.64.65.56:8080  December 9 01:34->December 9 14:50
[   P2662R1C407G24 ]
08 *READY     a2 171.67.108.24:8080  December 9 14:52 | December 12 14:52
[   P2671R3C24G147 ]
09  EMPTY
I got to see this machine just today :(

I have problems also on bigadv WU's, but regular smp is this the first time.

all appeared to be packet limit problem:

Code: Select all

matheus@pb021835:~/fd$ ./qfix
entry 9, status 0, address 171.67.108.24:8080
entry 0, status 0, address 171.67.108.24:8080
entry 1, status 0, address 171.67.108.24:8080
  Found results <work/wuresults_01.dat>: proj 2671, run 12, clone 90, gen 144
   -- queue entry: proj 2671, run 12, clone 90, gen 144
   -- already sent
entry 2, status 0, address 171.67.108.24:8080
  Found results <work/wuresults_02.dat>: proj 2671, run 40, clone 8, gen 144
   -- queue entry: proj 2671, run 40, clone 8, gen 144
   -- already sent
entry 3, status 2, address 171.67.108.24:8080
  Found results <work/wuresults_03.dat>: proj 2671, run 8, clone 23, gen 145
   -- queue entry: proj 2671, run 8, clone 23, gen 145
   -- increasing packet limit from 10484736 to 49684264
entry 4, status 2, address 171.67.108.24:8080
  Found results <work/wuresults_04.dat>: proj 2671, run 36, clone 28, gen 145
   -- queue entry: proj 2671, run 36, clone 28, gen 145
   -- increasing packet limit from 10484736 to 49644848
entry 5, status 2, address 171.67.108.24:8080
  Found results <work/wuresults_05.dat>: proj 2671, run 42, clone 3, gen 145
   -- queue entry: proj 2671, run 42, clone 3, gen 145
   -- increasing packet limit from 10484736 to 49686730
entry 6, status 2, address 171.67.108.24:8080
  Found results <work/wuresults_06.dat>: proj 2671, run 26, clone 42, gen 146
   -- queue entry: proj 2671, run 26, clone 42, gen 146
   -- increasing packet limit from 10484736 to 49643787
entry 7, status 2, address 171.64.65.56:8080
  Found results <work/wuresults_07.dat>: proj 2662, run 1, clone 407, gen 24
   -- queue entry: proj 2662, run 1, clone 407, gen 24
   -- increasing packet limit from 10484736 to 27812125
entry 8, status 1, address 171.67.108.24:8080
File needed repair.  Errors fixed: 5.
matheus@pb021835:~/fd$ ./fah6 -queueinfo
is ther eanything to do about this ? I'm loosing much work here (I got the first DONE expired just now :( )

thanks,

matheus

Re: problems with 171.67.108.24

Posted: Thu Dec 10, 2009 12:06 am
by toTOW
Make sure you answer "big" to the packet size question when you configure the client.

Re: problems with 171.67.108.24

Posted: Thu Dec 10, 2009 6:23 pm
by matheusber
did it, thanks. let's see now :)

big thanks for your time :)

matheus

Re: problems with 171.67.108.24

Posted: Thu Dec 10, 2009 6:50 pm
by bruce
Setting bigwu in the configuration will fix future assignments but I'm not sure if it will help with ones you've already completed. If they upload correctly, good. If not, you'll probably need "qfix"

Re: problems with 171.67.108.24

Posted: Sat Dec 12, 2009 3:01 am
by matheusber
bruce wrote:Setting bigwu in the configuration will fix future assignments but I'm not sure if it will help with ones you've already completed. If they upload correctly, good. If not, you'll probably need "qfix"
I did it already, thanks.

looks like it was it. still looking after it.

thanks,

matheus