Quote:
Originally Posted by EdH
Thanks! I'll definitely try to set that up on my RPi machines.
But, my "farm" machines have almost all crashed! They were working 70dd+10 and they're all coming up with gibberish:
Code:
href="res.php">limits</a>) already factored
Error, no result found
Factoring 3 digits: (<a
compCheck 100% 127KB 9.8MB/s 00:00
(<a already factored
(<a already factored
Error, no result found
Factoring 28 digits: href="imp.html">Imprint</a>)
compCheck 100% 127KB 9.7MB/s 00:00
href="imp.html">Imprint</a>) already factored
Error, no result found
Factoring 3 digits: (<a
compCheck 100% 127KB 9.5MB/s 00:00
(<a already factored
(<a already factored
Error, no result found
Factoring 31 digits: href="datenschutz.html">Privacy
compCheck 100% 127KB 9.3MB/s 00:00
href="datenschutz.html">Privacy already factored
Error, no result found
Factoring 11 digits: Policy</a>)
compCheck 100% 127KB 9.6MB/s 00:00
Policy</a>) already factored
Error, no result found
Factoring 0 digits:
compCheck 100% 127KB 9.6MB/s 00:00
already factored
Error, no result found
(The compCheck is a file that contains a list of all the composites that any of the machines has factored, to minimize duplicates. I have to trim it often.)
I had to take the entire set down for now.

To judge by the bits of html factordb is sending a web page instead of a number to factor. Which might well be saying you have reached a limit on how much you can do in an hour. The limits are by IP address connecting to factordb so are shared by everything at that IP address.
I've had to update my scripts to wait for a few minutes before trying again when they see something like that. And dump whatever they received to a log where I can see it.
I've also seen messages like:
Code:
1040: SQLSTATE[HY000] [1040] Too many connections
Which is an internal problem in factordb.
Chris