OFFICIAL "SERVER PROBLEMS" THREAD

[Viliam Furik]

Screenshots. It seems to be correct now... I swear it was switched last time. I'll tell you if I see it happen again. Unless you made a stealth fix.

[James Heinrich]

Originally Posted by Viliam Furik

Screenshots. It seems to be correct now... I swear it was switched last time. I'll tell you if I see it happen again. Unless you made a stealth fix.

I have not changed anything. If you notice it showing up incorrectly again for whatever reason please do provide another screenshot.

[Zhangrc]

Originally Posted by Viliam Furik

Screenshots. It seems to be correct now... I swear it was switched last time. I'll tell you if I see it happen again. Unless you made a stealth fix.

That error "TF result was not needed" is a bug, I doubt. The TF assignments still help to find more factors, and have not previously been done, so credit should be given.

[James Heinrich]

Originally Posted by Zhangrc

That error "TF result was not needed" is a bug

Not a bug. The exponents have known factors, therefore are certainly not Mersenne Primes, therefore as far as GIMPS (Great Internet Mersenne Prime Search) is concerned no further effort should be spent on this exponent. Users can of course spend their cycles wherever they want, but for the purpose of finding the next Mersenne Prime any effort on an exponent with known factors is wasted effort.

[kriesel]

Assignments obtained today as 84M PRP DC (PRP second test of an exponent with PRP first test already reported) manually assigned are indicated in https://www.mersenne.org/workload/ as PRP, Cat 0, with 7 days allowed to start (or 7 days to complete and be reported, in the case of manual assignments on GPUs, which have no way to report progress). As PRP DC, 84M should be indicated as Cat 4, not Cat 0. (Cat 3 DC today is exponents below 63724104.)
This is the case even after they are put on prime95 instances behind other work and expected completion dates reported by PrimeNet API to the server. This issue has lingered on for years and been repeatedly reported previously. Please look into implementing a fix. Otherwise the issue will continue on for several more years. I believe it also affects automatically issued PRP DC via PrimeNet API.

CPU Name       Core  Exponent  Work type Current cat Original State% Assigned    Last update  Est. Complete Days left Expires days
Manual testing   1    84661939      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84662069      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84662239      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84662323      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84663617      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84663907      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84665089      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84665459      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84666083      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84666587      PRP       0       0              2021-07-29   2021-07-29                             7
Kilroy_was_here  1    84666823      PRP       0       0        PRP   2021-07-29   2021-07-29    2021-08-04    6         30
Kilroy_was_here  2    84666931      PRP       0       0              2021-07-29   2021-07-29    2021-08-06    8          7
Manual testing   1    84667057      PRP       0       0              2021-07-29   2021-07-29                             7
Manual testing   1    84667201      PRP       0       0              2021-07-29   2021-07-29                             7
ostrich          1    84668011      PRP       0       0              2021-07-29   2021-07-29    2021-08-05    7          7
ostrich          2    84668407      PRP       0       0        PRP   2021-07-29   2021-07-29    2021-08-04    6         30

It seems only exponents checked out as PRP DC for exponents with LL first tests already completed, which is a separate manual assignments page menu selection from ordinary PRP DC, get correctly indicated as PRP-D currently and show appropriate Cat #'s and expiration dates:

CPU Name      Core   Exponent  Work type Current cat Original State% Assigned    Last update  Est. Complete Days left Expires days
Manual testing  1    61503457      PRP-D      2       3              2021-06-28    2021-06-28                            89
Manual testing  1    61823711      PRP-D      3       3              2021-07-28    2021-07-28                           119
Manual testing  1    61823731      PRP-D      3       3              2021-07-28    2021-07-28                           119

[Uncwilly]

All PRP-CF suffer from this too.

[S485122]

5 exponents are missing in the 57M range :

 57000000 55901  1 | 36254 19211   435             |                     430 |                         |

The 430 assigned exponents can be found using the active assignment page.

5 exponents are missing and they were already missing at the end of June. Other ranges also have missing exponents.

Jacob

[S485122]

https://www.mersenne.org/report_pminus1/?exp_hi=99, M3 has three P-1 factoring attemps in the database : https://www.mersenne.org/report_expo...exp_hi=&full=1
One would say their computer, their time, their electricity, ... ;-) but I can't understand how those strange attempts found their way in the database. I strongly suspect the results in the database are fakes : the bounds are obviously inane. Why would new results be accepted for a known Mersenne prime ?

Jacob

[Prime95]

Originally Posted by S485122

5 exponents are missing and they were already missing at the end of June. Other ranges also have missing exponents.

Five exponents where the server is (too?) patiently waiting for a proof upload:

57310949
57311099
57326809
57326917
57331919

[Prime95]

Originally Posted by Prime95

Five exponents where the server is (too?) patiently waiting for a proof upload:

Something weird going on. The server is supposed to wait 60 days for a proof. At that point it deletes the assignment and makes the exponent available again. In this case, the assignment was deleted (or maybe never assigned in the first place?), but the exponent was not made available again. I've manually corrected the 5 exponents.

Two more that I did not fix:

60800659
60822823

There are also quite a few over 100 million, which does not concern me at the present time. I need to understand why this is happening to create a true fix.

[kriesel]

These are all LL first test / PRP proof tandem exponents. Three PRP userids.

57310949 tservo
57311099 tservo
57326809 tservo
57326917 tservo
57331919 tservo

60800659 nescro
60822823 Lukas_J