![]() |
|
|
#441 |
|
May 2019
Rome, Italy
5·7 Posts |
I too noticed that. After coming back up, there were 16 workers crunching certificates instead of the usual 4.
I guess fdb was taken down momentarily to start the other workers. |
|
|
|
|
|
#442 |
|
Sep 2008
Kansas
24×211 Posts |
I am getting 503 Service Unavailable ATM.
|
|
|
|
|
|
#443 |
|
"Daniel Jackson"
May 2011
14285714285714285714
3·13·17 Posts |
Me too. I think Syd is doing maintenance on it. Maybe he's adding more disk space to help the DB run better.
|
|
|
|
|
|
#444 |
|
"Alexander"
Nov 2008
The Alamo City
24·43 Posts |
Site's down.
|
|
|
|
|
|
#445 |
|
"99(4^34019)99 palind"
Nov 2016
(P^81993)SZ base 36
5·7·83 Posts |
|
|
|
|
|
|
#446 |
|
May 2020
3·13 Posts |
Are there issues with certificate uploading at the moment? I've tried, on three separate occasions, to upload a 37 MB certificate, with no indication of validation in status. Is there a weekly maintenance I'm not aware of?
|
|
|
|
|
|
#447 |
|
"Ed Hall"
Dec 2009
Adirondack Mtns
11×347 Posts |
The following numbers appear to be cross-referenced erroneously in the db. This is shown using either the short or long form for each number, so it doesn't appear to be an expression evaluation error:
Code:
72^53 should be (72)^53 = (2^3 · 3^2)^53 rather than (2)^318 = (2)^318 72^59 should be (72)^59 = (2^3 · 3^2)^59 rather than (2)^354 = (2)^354 72^61 should be (72)^61 = (2^3 · 3^2)^61 rather than (2)^366 = (2)^366 72^67 should be (72)^67 = (2^3 · 3^2)^67 rather than (2)^402 = (2)^402 72^71 should be (72)^71 = (2^3 · 3^2)^71 rather than (2)^426 = (2)^426 72^73 should be (72)^73 = (2^3 · 3^2)^73 rather than (2)^438 = (2)^438 72^79 should be (72)^79 = (2^3 · 3^2)^79 rather than (2)^474 = (2)^474 72^83 should be (72)^83 = (2^3 · 3^2)^83 rather than (2)^498 = (2)^498 72^89 should be (72)^89 = (2^3 · 3^2)^89 rather than (2)^534 = (2)^534 72^97 should be (72)^97 = (2^3 · 3^2)^97 rather than (2)^582 = (2)^582 |
|
|
|
|
|
#448 |
|
Jul 2003
So Cal
210610 Posts |
http://factordb.com/index.php?id=1100000001046468738 is listed as PRP, but it is composite with the factor 17756960164157539411. When I report the factor, it returns that the factor is already known.
|
|
|
|
|
|
#449 |
|
Sep 2009
2·1,039 Posts |
That's a known problem due to factordb not interpreting ## the same way as the software it uses for primality testing. Syd has been told about this but hasn't found time to fix it.
In the meantime assume any PRP in factordb containing ## is probably not prime. But there's nothing else we can do about it. Chris |
|
|
|
|
|
#450 |
|
"Daniel Jackson"
May 2011
14285714285714285714
12278 Posts |
Strange problem going on at http://www.factordb.com/sequences.ph...20&fr=0&to=100
Code:
Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Warning: mysql_fetch_*(): supplied argument is not a valid MySQL result resource Sequence RSA-100 EDIT2: I can't get the More Information panel to expand. I just get an error: "Fehler:500". Apparently, it happens on all numbers (http://www.factordb.com/index.php?id=8675309 for example). Last fiddled with by Stargate38 on 2020-10-27 at 14:57 Reason: Happens on every sequence |
|
|
|
|
|
#451 | |
|
"Alexander"
Nov 2008
The Alamo City
24×43 Posts |
Quote:
As an aside, can we get English error messages instead of me having to look up "Fehler"? (In retrospect, it's an obvious cognate of "failure".) |
|
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| A suggestion for factordb. | enzocreti | FactorDB | 15 | 2021-06-24 07:15 |
| Extending Factordb | carpetpool | FactorDB | 6 | 2017-01-23 11:04 |
| FactorDB PRP's | smh | FactorDB | 231 | 2015-07-28 02:30 |
| bugged sequence in factordb | firejuggler | Aliquot Sequences | 2 | 2010-06-15 14:03 |
| FactorDB question | Raman | Factoring | 15 | 2010-01-28 10:24 |