Out of Work?
 

I noticed that the work queue was empty, and machines arent crunching. Just a heads up.

Number of pairs in work queue: 0

I think, you are just too fast for the server :grin:

When i am back home i have to check why the database job does not produce new work. There is enough work available for sure. It is defenitely no problem of the LLRnet server, there must be something wrong with one of my jobs.

Sorry,

Lars

I know what happened and it is indead my fault. Sometimes i am such a stupid idiot. :furious: :furious: :furious: :furious:

To speed up the search access for new WU i have put a upper limit for the value of n into the scripts.

Now i have optimized the DB so there is no real need for that limit anymore but guess what i forgot the remove. And due to the fact that we have some powerusers at work at the moment we reached the limit much earlier as i would have believed.

Again sorry and i will fix this as soon as i am home.

Lars

Who hopes that there is not to much disapointement about the lost cycles.

[QUOTE=ltd;92034]I know what happened and it is indead my fault. Sometimes i am such a stupid idiot. :furious: :furious: :furious: :furious:

To speed up the search access for new WU i have put a upper limit for the value of n into the scripts.

Now i have optimized the DB so there is no real need for that limit anymore but guess what i forgot the remove. And due to the fact that we have some powerusers at work at the moment we reached the limit much earlier as i would have believed.

Again sorry and i will fix this as soon as i am home.

Lars

Who hopes that there is not to much disapointement about the lost cycles.[/QUOTE]

Looks like it doesn´t select work with n >= 150000

Sierpinski queue is sstill going fine :>:grin:

Lars,

no worries, we all make mistakes sometimes, just looking forward to getting some more work!:cool:

It will take a little bit longer to reactivate the firstpass checks.
Therefore i will hand out all the missing low tests for riesel.

Lars

Status report:

Stats will be off for the next two hours.
The first new tests have entered the DB but due to some locking between the stats script and the insert script they enter the system to slow.

Should be solved in the next half hour.

Lars

@Birdman:
How many systems do you use?!
15 tests in about 20 seconds? I know, the n is really low, but this is FAST.

News update:

There is enough work again.
I will switch on the scripts within the next hour.

Lars