Manual result submission could fail
 

I just uploaded a file with results, and the server took a long time responding.
In the end, the load screen ended (IE/FF stops loading the page), but I didn't get the summary of my submission.

Thanks to the fact that gpu272 informed me that I had 21 exponents left and not the 10 I saw, I could see that only half of my submitted results were loaded.

I re-uploaded the file and now it's ok.
Maybe a warning on the manual results submission (files) should be displayed, so people know to resend their files upon failed/partial check-in. I was happy with the 353% CPU for 24h, but the 797% was more accurate :).

[QUOTE=sonjohan;297114]Maybe a warning on the manual results submission (files) should be displayed, so people know to resend their files upon failed/partial check-in. I was happy with the 353% CPU for 24h, but the 797% was more accurate :).[/QUOTE]

Yeah...

Unfortunately PrimeNet has been having problems for the last few weeks (and the last few years).

Scott is no where to be found.

George listens, but doesn't always react.

Guys, it's time to reboot the Mersenne server....

[QUOTE=sonjohan;297114]
Maybe a warning on the manual results submission (files) should be displayed, so people know to resend their files upon failed/partial check-in. [/QUOTE]

A warning is just as hard to get out as the success message is, so if the latter doesn't work, nor would the former. [strike]There's not much we can do about it, except perhaps do uploads in smaller batches (or use the submission spider, which does them one at a time and waits specifically for the success message before moving on to the next one).[/strike]
(Edit) I take it back. I cannot even submit one result at a time with my spider. The server definitely needs a reboot. (Edit2: I got the "CGI timeout/deleted process" error. Could a mod move these posts to the server problems thread?)

As I said before, that's part of the why I report "by hand" :smile:. I can afford 5 minutes in the evening when I arrive home, to report whatever mfaktc harvested during the day, and sometimes (like now) 5 minutes in the morning to report the overnight results. Don't trust the spiders :razz:

Well... sometimes I have to try many times. But that's the part of the fun... And you say that a reboot solves the problem? Hmmm... I am thinking now to some virus to reboot every 24 hours, the question is how to cheat George to run it on the server... :razz:

[QUOTE=LaurV;297147]As I said before, that's part of the why I report "by hand" :smile:. I can afford 5 minutes in the evening when I arrive home, to report whatever mfaktc harvested during the day, and sometimes (like now) 5 minutes in the morning to report the overnight results. Don't trust the spiders :razz:
[/QUOTE]...I fail to see what's wrong with spiders. My spider (based on chalsall's) observed that it wasn't working, and aborted gracefully. Btw, it did work fine 20 minutes ago.

Just teasing you man... (but I do report by hand, I am a skeptical sob, hehe).
Edit: and yes, it is worse and worse and worse day by day when I report my mfaktc stuff. Yesterday, after trying 3-4 times to send the whole file without success, I had to split the file in 5 or 6 parts. There was no way to report all-at-once, it always ended with timeout error. The most of the reported lines were recorded. When I reported the "splits" afterthat I got error 40, result not needed, for most of the lines, this means they were recorded, only the communication timeouted. But some of them were not recorded, in quite a random fashion (when I reported the "splits", random lines gave me the right credit, meaning they were not recorded first/second/third time when I tried to report the whole file). These "trials" also generate server traffic, and not only a little! If the things would go well at the first trial, then the traffic would also be less, we won't need to try and try. But here we run in circles... or in cascade, if it starts to go wrong, we try and try (by hand or by spiders, I think that the "more and more" spiders in the last time contribute to process, with their number and their "auto-retry" functions, more then the pure manual-reporting workers, like me:razz:) and make the things worse and worse.

Such tedious work, reporting completed work.

Alas, we have resorted to only reporting factors.

:max:

[QUOTE=Xyzzy;297157]Such tedious work, reporting completed work.

Alas, we have resorted to only reporting factors.

:max:[/QUOTE]

...but that screws up both GPU272 and PrimeNet. PrimeNet has no idea that there isn't a factor if you don't report it... meaning the work will be duplicated anyways, so you may as well have not done it.

We will dump the no factor results someday once the server is in a better mood.

:poop:

Per Scott K. (email to me, Mon. Apr 23, 2012 5:17 PM [New York time(?)]): "I paused the web service a minute to let the database catch up and resumed the web. We are upgrading the server soon -- we've outgrown our data center host's server -- probably the next few months." (also posted in 'OFFICIAL "SERVER PROBLEMS" THREAD')

[QUOTE=Xyzzy;297197]We will dump the no factor results someday once the server is in a better mood.

:poop:[/QUOTE]

But it seems that even submitting just factors won't catch you up with Craig on the "Work Saved" charts.:no:

Maybe you need a couple more GTX 580s?