[QUOTE=Madpoo;408868]...blah blah...[/QUOTE]

Well, I looked again at the web logs, and comparing the different updates (t=ap) to the unassign request (t=au) revealed something interesting.

The assignment updates all had the CPU guid of kladner's machine. The unassign request actually came from a different user's machine: KYOJI_KAMEI, and the public CPU name of the machine in question is "unreserve"

Which is weird, because it had that assignment ID. Now, the assignment ID's are 128-bit GUIDs so the odds of any 2 being the same are pretty astronomically low... and all of them did come through the GPU72 proxy.

I'll once again assume the best intentions, especially since that other user is a prolific contributor, and somehow maybe it got the wrong assignment ID and that got things jumbled up when it was trying to unassign one of it's actual exponents? Especially since you didn't see that specific request when you ran the query... makes it sound like that wasn't the AID his machine sent (but that's definitely the AID that Primenet received).

Here's the partial GUID of the other cpu so you could query for anything from it around that UTC time when it was removed:
20fc911afa622d279ac97...

Oh, and I remembered where I saw the Primenet API info:
[URL="http://v5.mersenne.org/v5design/v5webAPI_0.97.html"]Web API Specification[/URL] ... it's in the menu of the site under the more info/help area.

[QUOTE]The unassign request actually came from a different user's machine: KYOJI_KAMEI, and the public CPU name of the machine in question is "unreserve"

Which is weird, because it had that assignment ID.[/QUOTE]

Having a machine name of 'unreserve' is kind of strange. It reminds me of the instance of P95 I keep named 'P95_Stress.' Still, this user did not complete the assignment. Apparently, this user just caused it to be thrown back. :unsure:

[QUOTE=kladner;408874]Having a machine name of 'unreserve' is kind of strange. It reminds me of the instance of P95 I keep named 'P95_Stress.' Still, this user did not complete the assignment. Apparently, this user just caused it to be thrown back. :unsure:[/QUOTE]

KYOJI_KAMEI is one of those other very prolific TF contributors. 1595 factors found by TF (and > 88K "no factor by TF" entries).

I think it was those times when that user was checking in a bunch of factors in one batch that was causing the old server to get a little choked up, prompting the whole idea of updating the server with newer gear. If I remember correctly.

EDIT: I'm wrong, it was the dumps from user TJAOI that would sometimes bog down the old server. Never mind. :) TJAOI has an impressive 3,207,726 factors (for 2,968,090 exponents) under their belt. Whew.