What's wrong with my queue?

[micron]

I'm running the seti cli service and seti queue service on my win2k machine. Everything was working great until yesterday when I replenished my queue. After replenishing I had 50 WUs in my queue, later that day I had 41, and this morning 35, with only 2 WUs completed. It says there are 5 WUs distributed to one of my clients. What's up with that? Help!

-micron

 

[Assimilator1]

Is the machine which has gobbled up the WU's otherwise working ok?
(just thinking that if ,e.g. the RAM was failing that would spew out WU's in a fraction of the time they normally take)

 

[serialb]

Is this a problematic client grapping new WUs before finishing the previous one? Check your client table to see how many WUs are pending to them respectively.

serialb

 

[micron]

Assimilator1, Yes otherwise the machine is working fine, it's even completing WUs in the same amount of time.

serialb, this is what my queue's pending WU chart says:

Q0001 2000 Dec 04 12:47:48am....1.855,13.32....0.427....pc1
Q0001 2000 Dec 04 05:54:42am....6.985,13.32.....0.427....pc1
Q0001 2001 Jan 03 09:35:34pm....23.328,18.01....0.417....pc1
Q0001 2001 Jan 04 12:07:30pm....15.184,12.14....0.429....pc1
Q0001 2001 Jan 05 12:10:09am....2.169,25.48......0.499....pc1
Q0001 2001 Jan 05 01:08:20am....4.164,25.94......0.852....PC5

 

[micron]

^

 

[serialb]

On PC1, you have SETI run as a service, am I correct? If so, is that SETI Driver as a service? From your WU chart, PC1 is pulling 5 WU. That's only possible if you are running SETI Driver as a client. Otherwise, something is wrong with your SETI as a service installation.

If you know where the WU info are stored, you may try copying SETI Spy in that directory and see which WU it is working on and the progress.

Better yet, reinstall the SETI service if problem still exists.

serialb

 

[micron]

serialb, pc1 is a service, no setidriver just cli. I'll try to reinstalling the cli service.

Thanks, micron

 

[serialb]

keep us posted

 

[Electrode]

I have this problem too. It started happening after I hit the 1000 WU mark, strangely. Sometimes, I look at my stats and a client will have a ton of workunits assigned to it.

There doesn't appear to be any solution, even removing and reinstalling SetiQ doesn't help. I just find out what WU(s) the client is REALLY doing, and recycle the rest.

BTW, I use the CLI client, with no service/seti driver/etc stuff.

 

[serialb]

I actually had a similar problem of single client pulling multiple WUs. I suspect it happens when the connection between the Q and the client gets disrupted. The Q (of this release at least) is not smart enough to log lost connection to WUs.

serialb

 

[micron]

Well, I reinstalled the cli service and recycled the WUs it had, still grabs multiple WUs. Could it be the WUs?

 

[Sukhoi]

That's really an odd problem, no idea why it's happening.