Factoring database

[kar_bon]

Originally Posted by EdH

Is it possible that only "I" am having this issue? It's showing up across platforms. It would have to be a pretty selective occurrence to only hit me, but still hit all my machines - ISP specific, I suppose.

I'm getting the same '5a7a7' at beginning and '0' at the end!

There's an error in the FactorDB because I know it worked fine, when I used this to download current data and make a table from those.

[EdH]

Originally Posted by kar_bon

I'm getting the same '5a7a7' at beginning and '0' at the end!

There's an error in the FactorDB because I know it worked fine, when I used this to download current data and make a table from those.

Thanks for checking, kar_bon. It used to work for AliWin, too. But, now, aliqueit crashes when it does the initial file read.

I thought Maybe it was just that the search criteria had changed. I guess that's not the reason and I'm not singled out.

[EdH]

Originally Posted by kar_bon

...There's an error in the FactorDB because I know it worked fine, when I used this to download current data and make a table from those.

I suppose the follow-on question would be whether anyone who is capable, considers this important enough to fix...

[Syd]

sorry for being late with all these bugfixes.
Just got the "5a7a7"-one. I forced the webserver to use HTTP/1.1 in the reply, but forgot that some clients like wget do not support features like chunked encoding. Now its back to 1.0-Request -> 1.0 Reply, looks like its working.

@mdettweiler
I use my self-written routines at the moment, but they are really slow, especially the N+1-one. Going to switch this over to pfgw some time.

Some bugs, as you wrote me / wrote here (thanks for your help!)
-The % in terms is handled with the wrong priority
-No limit in parallel "scan-button-clicks" could overload the server
-Some large terms exceed the memory limit
-Still no merge detection within sequences (sorry)

@gremlins:
they appear if the disk is full and pfgw cannot write its logfile

@all:
thank you for contributing so many certificates. Its more than 4GB already and growing!

[EdH]

Thank you for all the work, Syd! I appreciate it. I did add a step into my AliWin program to filter out extraneous lines. Now, I can take that back out.

A question - I had been having AliWin (GUI for Aliqueit) hit the db for the last line when getting ready to send data, but now I seem to only be able to retrieve the entire file. Additionally, if I retrieve the file to decide where to start sending, the subsequent send operation frequently times out. Consequently, I have changed the process to only hitting the db once, but sending the entire file each time. Any thoughts? Is there a "spam" delay that I'm hitting by retrieving the file and then turning around and sending too soon?

Thanks again for all your work.

Take Care,
Ed

[Greebley]

Syd,
I think I might have broken something. I made the mistake with typing a wget that had 'eff=1' instead of 'eff=2' :

wget "http://factorization.ath.cx/sequences.php?se=1&eff=1&aq=276&action=last" -O last_276.http

It never came back (I ^c'd after a bit) and the database went away (not reachable by browser). I really hope I didn't damage anything.
Jay



Sorry about that chief! - Maxwell Smart

[gd_barnes]

Syd is now reporting a power outage and that the DB will be back soon.

[Syd]

Hi everyone,

there was a power outage today, allowing the server to cool down for about 3 hours. I bought an UPS for it some time ago, but it wasnt able to keep it up long enough for a clean shutdown - instead it blew up one battery after just one minute and left a toxic smell.
Now I'm repairing the tables again. I also have a recent backup, but that wont be necessary. When done I'll tune it a little bit and add some minor updates.

@EdH
There was a high load on the server sometimes, mainly cause there is no limit on scan-queries. I think this caused the timeouts. I'll reprogram the sequence-section anyway - put this on my list. There is a spam delay, but thats set really high, about 4 pages/second. Just to catch some spambots and googlebot crawling too fast.

@Greebley
No, you didnt

[EdH]

Originally Posted by Syd

...
@EdH
There was a high load on the server sometimes, mainly cause there is no limit on scan-queries. I think this caused the timeouts. I'll reprogram the sequence-section anyway - put this on my list. There is a spam delay, but thats set really high, about 4 pages/second. Just to catch some spambots and googlebot crawling too fast.
...

Right now I've stopped hitting the db twice and just have the program submitting the full elf. Once I do get the last line only "wget" working correctly, I'll build in a slight delay between db check and Aliqueit send. Of course, I can't guarantee what version of AliWin others are using, but I'll try to keep the available one current. Actually, I really need to set it up to keep track of what has been sent within the current program invocation, and leave the db alone. Otherwise, the only reason for a db check is to catch merges, and neither my program nor the db are currently looking for merges.

Sorry to hear (and see) about the battery. Thanks much for all the work.

[schickel]

Some problems still in the DB (maybe from the power outage?). These two sequences, that I know of, show up blank (status is from the last time I polled):

282810 375. sz 113 2^3 * 3 * 5
515028 320. sz 103 2^3 * 3^3 * 5 * 73

[bchaffin]

Originally Posted by schickel

Some problems still in the DB (maybe from the power outage?). These two sequences, that I know of, show up blank (status is from the last time I polled):

282810 375. sz 113 2^3 * 3 * 5
515028 320. sz 103 2^3 * 3^3 * 5 * 73

434700, 468360, 740736, and 947880 also show up blank.