[QUOTE=retina;418082]Does the latest addition to the milestones page show some DB corruption?
[code]# Countdown to first time checking all exponents below 62M: 275 (1 still unassigned)
# Countdown to first time checking all exponents below 63M: 509 (3 still unassigned)[/code]Checking the [url=http://www.mersenne.org/primenet/]hourly report[/url] does not show any exponents in those ranges as available.

[size=1]I am aware of the different schedules that these pages are updated. But this has persisted for more than a few hours now and the milestones page always shows that number exponents waiting to be assigned.[/size][/QUOTE]

Just spitballing here, but maybe they're checked out for something besides LL at the moment (TF, P-1, ECM).

I can check in detail later on when I have time.

[QUOTE=Madpoo;418084]Just spitballing here, but maybe they're checked out for something besides LL at the moment (TF, P-1, ECM).[/QUOTE]The hourly report would show that in the "Assigned" column but those are all blank except for the LL section.

[QUOTE=cuBerBruce;418083]I note that the highest sub-60M exponent remaining for first LL testing got recycled. With the new assignee of [url=http://www.mersenne.org/M59969537]M59969537[/url] having an ETA of 46 days, I think it's unlikely that the new assignee will beat the old assignee to completing the test. The old assignee was at least 92.7% done with the test.[/QUOTE]

I checked my "assignment history" stats and I'm projecting that original assignment will finish in 4.7 more days.

I don't know... he had 3 months and almost made it, but again, I'm pretty sure when it was assigned it was a priority assignment and that user did have the "preferred assignment" option checked.

I wonder if we could look at users who have that option checked and see how many assignments they've let expire... maybe turn that option off. After all, sometimes users might check that with the best of intentions and then life happens... unchecking that box probably isn't high on their list of priorities if they even remember it's there at all.

Well, not a huge problem, probably, but that is the second time in one day that we've seen this come up.

[QUOTE=Madpoo;418084]I can check in detail later on when I have time.[/QUOTE]

Looked into it. Weird... these 3 exponents were set to be available for *double* checking even though no first time check has been done yet:
61535039
62121131
62327819

I think I just need to change the "availability type" on those to be first-time instead of double checks and they should get assigned out pretty quick.

Reasons for that happening? Could be someone had checked in a suspicious looking LL test that George invalidated, but that "make available for DC" never got set back. That was my first thought, but it could have been something else entirely... no idea.

This sounds familiar, like the same thing happened recently with something in the 57M or 58M range... I should probably just check and see if there are any other exponents in that situation.

[QUOTE=Madpoo;418133]... I should probably just check and see if there are any other exponents in that situation.[/QUOTE]

Checked, found 4 more between 63M and 100M.

63316289
63316753
63344161
65035609

I'll move those to first-time checks as well since I don't see any reason why they'd be available for double-checks when no first-time check has been done yet.

EDIT: Searched above 100M as well and didn't see any others. That should take care of it.

[QUOTE=Madpoo;418169]That should take care of it.[/QUOTE]Except that the underlying problem appears to have not been discovered, so it could happen again in the future?

[QUOTE=retina;418171]Except that the underlying problem appears to have not been discovered, so it could happen again in the future?[/QUOTE]

Yes. I have no idea why this would happen. There is a stored procedure that determines how to add rows to the available assignments table. I don't see how that procedure could list an exponent for DC when there are no LL tests completed.

[QUOTE=Prime95;418172]Yes. I have no idea why this would happen. There is a stored procedure that determines how to add rows to the available assignments table. I don't see how that procedure could list an exponent for DC when there are no LL tests completed.[/QUOTE]Has it happened in the past and no one spotted it? Are there "DC"ed exponents with only one LL test completed?

[QUOTE=retina;418173]Has it happened in the past and no one spotted it? Are there "DC"ed exponents with only one LL test completed?[/QUOTE]

That's done independently (determining when an exponent has been DC'd) and it's pretty thorough, taking into account that it needs matching residues from different shift counts (or for the old code before shift counts, they had to come from different software).

What George referred to is a process that will take exponents that perhaps were expired assignments and makes them available again. When it makes them available it looks at the available data and sets the proper first time or DC work type along with some other useful stats like how far it's been factored and thus it's "difficulty" level (which also varies based on if it's a first time or DC work type).

To "reset" them I actually ran the stored procedure to make them available again, and it did it correctly, setting them to first time work and setting the difficulty appropriately. So I'd lean more towards something funky happened with the first time check, and by then they'd already been made available as a DC.

Now that we know there aren't any more like that, if it happens again we'll know that it was something that got muddled between now and then so we'll have something to go on. With those other ones, it would be hard or impossible to say when they got put into that weird state. I might peek back at any logs available since we moved to the new server in case anything shows up, but I won't hold my breath. :smile:

EDIT: Searched the web server logs, didn't see any activity on those exponents in the past year so whatever happened predated the new server setup at least.

[QUOTE=Madpoo;418086]I checked my "assignment history" stats and I'm projecting that original assignment will finish in 4.7 more days.[/QUOTE]

That user has now finished it, so the new assignee now has exponent 59969537 as a double-check. It came in sooner than Madpoo's prediction.

[url=http://www.mersenne.org/report_exponent/?exp_lo=46842001&full=1]M46842001[/url] could use a triple check :)

DoubleCheck=46842001,72,1