Official FactorDB server status thread

R.D. Silverman · 2022-09-04, 01:03

Is it down????

retina · 2022-09-04, 06:42

No.

http://factordb.com/index.php?query=666

chris2be8 · 2022-09-04, 15:52

I started having problems at about 21:05 BST yesterday, it said "You have reached the maximum of 4 parallel processing requests. Please wait a few seconds and try again." for every request until about 22:11 BST, then I got "502 Proxy Error" until about 03:22 BST this morning. Then things seemed to be back to normal.

Times are approximate because the script makes accesses every few minutes.

gd_barnes · 2022-09-30, 01:41

About 30 mins ago, FactorDB would come up but it gave an error whenever I tried to pull up an Aliquot sequence. Unfortunately I ended up with the 4 parallel processing requests error trying to figure out what happened. I'm unable to clear out the error. It has been happening ever since. Hopefully the issue will resolve itself after an hour or so. I've not had it lock me out for that reason for this long before.

EdH · 2022-09-30, 02:07

I just got:

Resources used by your IP

Page requests 4
IDs created 0
Database queries 135
CPU (Wall clock time) 10,752.4 seconds
You have reached your hourly limit of 2400 seconds CPU-time.

Batalov · 2022-09-30, 02:28

Syd (Markus) may have adjusted his allowance limits, who knows?
(If his root cause analysis from last downtime indicated too much traffic, he could have been driven to take that action.) You can ask him.

4 concurrent threads limit was there before, that doesn't seem to be new. Plus there were some hard to gauge limits, those that only come into play when one creates series for example, like "Some_expression+n" and then visits several pages of those. If that series is new, this can quickly eat up initial factoring resources that his daemons do, and that gets counted against the specific user (or, rather, IP?).

Ah! another idea - if this happens and non-logged in, then some other anonymous user could have use all allotted resources for the hour (all anonymous 's are lumped, I would guess). Try logging in into names account and repeating the request. The IP limit will still apply, though. Probably won't help. Use VPN, or multiple non-same-masqueraded-IP nodes!

gd_barnes · 2022-09-30, 07:24

The point that I was making and I think Ed was too is that we did not do anything unusual. The system locked up when we would try to display aliquot sequences.

There does not appear to be a change to the limits.

Later after I posted the first time, I got the exact message that Ed did. It appears that for a period of time, if you tried to display an aliquot sequence, it would go into an endless loop. Since I wasn't aware of what happened, I tried a few more times and ended up with 4 parallel processing requests not knowing that the others were still "running". Eventually the endless loop ate up all of the available CPU time...until it was corrected.

I had to wait for nearly an hour after the "Counting since" time on the limits page. It had cleared itself out by then.

That's my theory and I'm sticking to it. :-)

axn · 2022-10-01, 00:54

Quote:

Originally Posted by Batalov

Ah! another idea - if this happens and non-logged in, then some other anonymous user could have use all allotted resources for the hour (all anonymous 's are lumped, I would guess).

No. Anonymooses are distinguished by IP

EdH · 2022-10-01, 02:08

I had more trouble this evening, and all I did was to provide an Aliquot sequence update, for a sequence with only three terms. Something does not seem right. . .

Actually, I'm still having trouble. It won't download .elfs.

thyrex · 2022-10-01, 03:25

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request

Reason: Error reading from remote server

Happy5214 · 2022-10-25, 12:11

OK, I checked the composites <= 120dd count a few hours ago, and it was a little over 18 million. Now, it's over 19.1 million! How is this possible? Clearly, the limits aren't working/are being circumvented.

2022-09-04, 01:03	#1
R.D. Silverman "Bob Silverman" Nov 2003 North of Boston 16524₈ Posts	Official FactorDB server status thread Is it down???? Last fiddled with by Uncwilly on 2022-09-30 at 13:37 Reason: Better thread title

2022-09-30, 07:24	#7
gd_barnes "Gary" May 2007 Overland Park, KS 10111001001110₂ Posts	The point that I was making and I think Ed was too is that we did not do anything unusual. The system locked up when we would try to display aliquot sequences. There does not appear to be a change to the limits. Later after I posted the first time, I got the exact message that Ed did. It appears that for a period of time, if you tried to display an aliquot sequence, it would go into an endless loop. Since I wasn't aware of what happened, I tried a few more times and ended up with 4 parallel processing requests not knowing that the others were still "running". Eventually the endless loop ate up all of the available CPU time...until it was corrected. I had to wait for nearly an hour after the "Counting since" time on the limits page. It had cleared itself out by then. That's my theory and I'm sticking to it. :-) Last fiddled with by gd_barnes on 2022-09-30 at 07:27

2022-10-01, 02:08	#9
EdH "Ed Hall" Dec 2009 Adirondack Mtns 2·3·877 Posts	I had more trouble this evening, and all I did was to provide an Aliquot sequence update, for a sequence with only three terms. Something does not seem right. . . Actually, I'm still having trouble. It won't download .elfs. Last fiddled with by EdH on 2022-10-01 at 02:11

2022-09-04, 06:42	#2
retina Undefined "The unspeakable one" Jun 2006 My evil lair 15037₈ Posts	No. http://factordb.com/index.php?query=666

2022-09-04, 15:52	#3
chris2be8 Sep 2009 2²·607 Posts	I started having problems at about 21:05 BST yesterday, it said "You have reached the maximum of 4 parallel processing requests. Please wait a few seconds and try again." for every request until about 22:11 BST, then I got "502 Proxy Error" until about 03:22 BST this morning. Then things seemed to be back to normal. Times are approximate because the script makes accesses every few minutes.

2022-09-30, 01:41	#4
gd_barnes "Gary" May 2007 Overland Park, KS 2×5,927 Posts	About 30 mins ago, FactorDB would come up but it gave an error whenever I tried to pull up an Aliquot sequence. Unfortunately I ended up with the 4 parallel processing requests error trying to figure out what happened. I'm unable to clear out the error. It has been happening ever since. Hopefully the issue will resolve itself after an hour or so. I've not had it lock me out for that reason for this long before.

2022-09-30, 02:07	#5
EdH "Ed Hall" Dec 2009 Adirondack Mtns 2·3·877 Posts	I just got: Resources used by your IP Page requests 4 IDs created 0 Database queries 135 CPU (Wall clock time) 10,752.4 seconds You have reached your hourly limit of 2400 seconds CPU-time.

2022-09-30, 02:28	#6
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 3·7·479 Posts	Syd (Markus) may have adjusted his allowance limits, who knows? (If his root cause analysis from last downtime indicated too much traffic, he could have been driven to take that action.) You can ask him. 4 concurrent threads limit was there before, that doesn't seem to be new. Plus there were some hard to gauge limits, those that only come into play when one creates series for example, like "Some_expression+n" and then visits several pages of those. If that series is new, this can quickly eat up initial factoring resources that his daemons do, and that gets counted against the specific user (or, rather, IP?). Ah! another idea - if this happens and non-logged in, then some other anonymous user could have use all allotted resources for the hour (all anonymous 's are lumped, I would guess). Try logging in into names account and repeating the request. The IP limit will still apply, though. Probably won't help. Use VPN, or multiple non-same-masqueraded-IP nodes!

2022-10-01, 03:25	#10
thyrex Jun 2021 2×3×5 Posts	Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server

2022-10-25, 12:11	#11
Happy5214 "Alexander" Nov 2008 The Alamo City 3×307 Posts	OK, I checked the composites <= 120dd count a few hours ago, and it was a little over 18 million. Now, it's over 19.1 million! How is this possible? Clearly, the limits aren't working/are being circumvented.