[QUOTE=kladner;290563]Just for the record, I have one DC and one LL reserved through GPUto72. PrimeNet has my name on them.[/QUOTE]
I have a few other LL and DC assignments with my name as well. This problem only seems to appear for machines that never talked to primenet. Maybe because those assignments expire faster? But they should not expire within 2 months ...

mprime did only delete the lines from worktodo. Fortunately it did not delete the save files.

[QUOTE=chalsall;290556]Everything you see on the site is generated dynamically in "real-time".

The discrepency you pointed out on the P-1 graphs was a "Stupid Programmer Error" -- I wasn't including the GDs credit for factors found. This has been fixed.[/QUOTE]

Thanks, the graphs and tables now match.

Gareth

[QUOTE=Bdot;290564]I have a few other LL and DC assignments with my name as well. This problem only seems to appear for machines that never talked to primenet. Maybe because those assignments expire faster? But they should not expire within 2 months ...

mprime did only delete the lines from worktodo. Fortunately it did not delete the save files.[/QUOTE]

I thought that you had to claim the assignments from Primenet within 30 days or it would be kicked back into the queue by GPUto72?

[QUOTE=KyleAskine;290568]I thought that you had to claim the assignments from Primenet within 30 days or it would be kicked back into the queue by GPUto72?[/QUOTE]

That's only for DCTF or LLTF assignments. P-1s are valid for 90 days; DCs and LLs go by PrimeNet's expiry rules.

But the magic "two months" has lead me to the probable problem... Working it....

[QUOTE=chalsall;290574]That's only for DCTF or LLTF assignments. P-1s are valid for 90 days; DCs and LLs go by PrimeNet's expiry rules.

But the magic "two months" has lead me to the probable problem... Working it....[/QUOTE]

But he said he didn't contact primenet on those machines?

Maybe I am missing something.

[QUOTE=KyleAskine;290579]But he said he didn't contact primenet on those machines?

Maybe I am missing something.[/QUOTE]

No, you're not missing things -- I misread your post. And yes, this appears to have been the problem.

"Spidy" wasn't checking in with PrimeNet for DC and LL assignments, as I considered such assignments to be the responsibility of the "owner".

I'm doing some analysis to determine who has been affected by this, and having Spidy check in with PrimeNet for those DC/LL assignments which PrimeNet still thinks is owned by Anonymous.

Also, it appears that many which were "lost" by workers have been reclaimed by Spidy (and fortunately not yet reassigned to others).

Let me keep working the problem -- I'll report back once I've completed what I need to do.

[QUOTE=chalsall;290583]Let me keep working the problem -- I'll report back once I've completed what I need to do.[/QUOTE]

Just so everyone knows, I'm still working this. A few will have already received PMs indicating that a few of their AIDs have changed as I reclaim the assignments from "KYOJI_KAMEI" and/or "GPU Factoring" (read: Spidy).

Manually going through log files, running SQL queries, and spidering PrimeNet was not how I had hoped to spend the day.... :sad:

OK, time for bed...

I've done a sanity check on the currently available DC and LL assignments, and reactivated the DC and LL assignment pages.

Will finish off the clean-up tomorrow.

[QUOTE=chalsall;290661]OK, time for bed...

I've done a sanity check on the currently available DC and LL assignments, and reactivated the DC and LL assignment pages.

Will finish off the clean-up tomorrow.[/QUOTE]

Thanks

My "View Assignments" page states

[quote]You currently have 4568 Trial Factoring Assignments totaling 4110.091 GHz Days of work[...][/quote]at the top vs.

[quote]4297 Assignments.[/quote]at the bottom. The latter is correct; I'm not sure about the GHzd total. :smile:

[QUOTE=ckdo;290750]The latter is correct; I'm not sure about the GHzd total. :smile:[/QUOTE]

Whoops. Thanks.

While PrimeNet is suffering load issues, I turned off a bunch of spiders from the crontab. Turned off the script which recalculates this by mistake. Reactivated.