There are now 48,978 C100s in factordb (about 44k more than C99s or C101s). Does anyone know where they are coming from?

If anyone wants a range to work on C100s would be a nice choice.

Chris

[QUOTE=chris2be8;467712]There are now 48,978 C100s in factordb (about 44k more than C99s or C101s). Does anyone know where they are coming from?

If anyone wants a range to work on C100s would be a nice choice.

Chris[/QUOTE]
At my present rate, it will be quite a while before I get up to there. I'm a little slowed because my primary interest (PRPs) just got a few hundred additions between 2000 and 3800. I'd like to clear that area a bit before I come back with more cores, although I do still have some working here.

[ vent ]

[code]
You have reached the maximum of 4 parallel processing requests ([URL="http://www.factordb.com/help.php?page=2"]?[/URL]). Please wait a few seconds and try again.


[SIZE=-1] factordb.com - 12 queries to generate this page (0.00 seconds) ([URL="http://www.factordb.com/res.php"]limits[/URL]) ([URL="http://www.factordb.com/imp.html"]Imprint[/URL])[/SIZE][/code][LEFT]on all my machines this morning. I shut down all the composite workers and the one submitting primo certificates and have waited a couple hours with no change. I can get into the db via an anonymous proxy, but I'm not going to. If the db does not wish to communicate with me, so be it!

[ /vent ]
[/LEFT]

[url]http://factordb.com/functioncheck.php[/url]
[CODE]
Checking yafu: ..Passed

Checking pfgw: ..Passed

Checking sorted locking tool (s_lock): ..[/CODE]

Looks like it's broken.

factordb.com broken
 

[QUOTE=EdH;468264] ...
[code]
You have reached the maximum of 4 parallel processing requests ([URL="http://www.factordb.com/help.php?page=2"]?[/URL]). Please wait a few seconds and try again.


[SIZE=-1] factordb.com - 12 queries to generate this page (0.00 seconds) ([URL="http://www.factordb.com/res.php"]limits[/URL]) ([URL="http://www.factordb.com/imp.html"]Imprint[/URL])[/SIZE][/code]...
[/QUOTE]

Same here, can't access the database.

I can't even get to the functioncheck.php page. All I get is this:

[code]This page isn't working.

factordb.com didn't send any data.

ERR_EMPTY_RESPONSE[/code]

Hopefully it'll be fixed so I can continue work on 132048.

Markus has replied to an email I sent him: [quote]
Hello,

thanks for writing me. The database needs some maintenance, I´m on it.

Markus
[/quote]
So it's being fixed.

Chris

Thanks Chris,

In the case of PRPs, I had a stash of awaiting Primo Input files so they are still in work, but for the composites, I was working one at a time with each machine so they are on hold for me.

It's working now:

[code]Checking yafu: ..Passed

Checking pfgw: ..Passed

Checking sorted locking tool (s_lock): ..Passed

Checking gp: ..Passed

Checking gmp_fib: ..Passed

Checking gmp_luc: ..Passed

Checking gmp_perfect_power_p: ..Passed

Checking gmp_root: ..Passed

Checking msieve plugin (QS): ..Passed

Checking GMP-ECM plugin: ..Passed

Checking database connection: ..Passed

Checking tables: ..Passed

Checking free disk space: ..Passed

Self-test passed![/code]

The PRPs from 2000-3800 dd have started to pile up again, so I have moved many of my machines back to that area. I still have some working composites between 76 and 94, but it will be a while before I have a strong presence with composites again.

I'm about frustrated out of the composites. If I'm not allowed to keep up with the input, why bother? Now, all of my machines are errorring for over half their time:

[CENTER][B]Resources used by your IP[/B] ([URL="http://www.factordb.com/help.php?page=1"]?[/URL])
Page requests 1,355
IDs created 12,004
[COLOR=#FF0000][B]You have reached your hourly limit of 12000 IDs created.[/B][/COLOR]
Database queries 392,038
CPU (Wall clock time) 689.4 seconds
Counting since October 4, 2017, 4:19 am
[/CENTER]

This is even messing up my automated Primo certificate reporting.

Sorry, but I'm unsure what I will do about this