Other Factordb Problems - Page 42

chris2be8 · 2020-10-27, 17:08

And the status page show the system load as:

Code:

  Load average, last minute   	25.69
 Load average, last 5 minutes 	32.11
Load average, last 15 minutes 	32.41

Which does not look right!

I've had occasional timeouts and proxy errors waiting for factordb to respond as well.

Chris

MDaniello · 2020-10-27, 19:34

I noticed the slowdowns/timeouts yesterday, and the disk usage this morning.

About the sequences, i tried looking for a short one (for example the aliquot one starting from 100) and it showed "Checked, new" as the status for all the terms (except the first).
My guess is that it fails to save and/or retrieve the sequence, so regenerates the sequence each time i ask the DB to show me the sequence: this could explain why asking for certain sequences slows the DB down.

Could it be that some tables in the db failed? After all, the numbers seem to be still there.

Stargate38 · 2020-10-27, 20:02

Also, the graph feature on the Sequences page isn't working:

http://www.factordb.com/aliquot.php?...10&pow=2&big=1

It gives a broken image.

Stargate38 · 2020-10-29, 22:42

Quote:

Originally Posted by Stargate38

I started with this prime that I had bookmarked:

http://factordb.com/index.php?id=1100000000636891196

When I try to open the More Information section, it won't respond. After that the DB wouldn't respond...

Still happening. Hopefully it gets fixed someday. Also, if I just wait it out, I get a Fehler (Error) 502.

EDIT: Also happens with 112648156947159943866724620^8-1.

EDIT2: Somehow, I ended up using 4749.4 seconds of CPU time, more than double my 2000 second limit. Please fix the problem with 112648156947159943866724620^x-1, as it wastes CPU time, even if you restart your browser.

Happy5214 · 2020-10-29, 23:26

The sequence pages are also returning 502 errors after several minutes. By the way, the limit and help pages should be exempt from the server limits, because they're useless if you can't load them if you've exceeded your limit.

yoyo · 2020-10-30, 16:55

The table which caches the sequences was marked as crashed. So the sequence table was deleted. Now on first access to a secuence the entries are recreated. This takes cpu time and many DB queries which might exceed your limit. But the second access should be fast.
It will take some time until frequently accessed sequences are recreated.

RichD · 2020-11-01, 14:52

Quote:

Originally Posted by frmky

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.

And it also has a factor of 655699597151565630884615214644435550853.

Stargate38 · 2021-01-17, 16:28

It appears the DB is down for a full backup. I'm glad that Syd's doing that, in case the server crashes.

2020-10-27, 17:08	#452
chris2be8 Sep 2009 2³×13×19 Posts	And the status page show the system load as: Code: Load average, last minute 25.69 Load average, last 5 minutes 32.11 Load average, last 15 minutes 32.41 Which does not look right! I've had occasional timeouts and proxy errors waiting for factordb to respond as well. Chris

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A suggestion for factordb.	enzocreti	FactorDB	10	2021-01-05 19:49
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

2020-10-27, 19:34	#453
MDaniello May 2019 Rome, Italy 2×17 Posts	I noticed the slowdowns/timeouts yesterday, and the disk usage this morning. About the sequences, i tried looking for a short one (for example the aliquot one starting from 100) and it showed "Checked, new" as the status for all the terms (except the first). My guess is that it fails to save and/or retrieve the sequence, so regenerates the sequence each time i ask the DB to show me the sequence: this could explain why asking for certain sequences slows the DB down. Could it be that some tables in the db failed? After all, the numbers seem to be still there.

2020-10-27, 20:02	#454
Stargate38 "Daniel Jackson" May 2011 14285714285714285714 277₁₆ Posts	Also, the graph feature on the Sequences page isn't working: http://www.factordb.com/aliquot.php?...10&pow=2&big=1 It gives a broken image.

2020-10-29, 23:26	#456
Happy5214 "Alexander" Nov 2008 The Alamo City 2³·5·11 Posts	The sequence pages are also returning 502 errors after several minutes. By the way, the limit and help pages should be exempt from the server limits, because they're useless if you can't load them if you've exceeded your limit.

2020-10-30, 16:55	#457
yoyo Oct 2006 Berlin, Germany 593 Posts	The table which caches the sequences was marked as crashed. So the sequence table was deleted. Now on first access to a secuence the entries are recreated. This takes cpu time and many DB queries which might exceed your limit. But the second access should be fast. It will take some time until frequently accessed sequences are recreated.

2021-01-17, 16:28	#459
Stargate38 "Daniel Jackson" May 2011 14285714285714285714 631₁₀ Posts	It appears the DB is down for a full backup. I'm glad that Syd's doing that, in case the server crashes.