Re: [WebDNA] Error 500 with SUMM=T
This WebDNA talk-list message is from 2017
It keeps the original formatting.
numero = 113847
interpreted = N
texte = 1442 > This morning I wrote a dirty script to summ the result by making a > new DB and searching this db before adding a new line... Good approach, because it forces WebDNA to run on a db that's not being used for anything else. > And I still add a crash, so memery problem... Maby not, we all > have been thinking of Webdna, Ram etc, but a 500 answer isn't it a > Apache error? I'm not sure without looking it up. What is the exact text of the error message? > I realised that this new db was still getting written after this > 500 error and I did get the right data in my db after all... Well then, WebDNA is not having a problem after all. Instead the browser is probably just timing out. > So isn't it in apache that I should setup a Timeout or KeepAlive Well, it certainly sounds like this might be a way to eliminate the apache timeout error if in fact what you've been getting is an apache timeout error. What are your current Apache settings? Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=55 Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
1442 > This morning I wrote a dirty script to summ the result by making a > new DB and searching this db before adding a new line... Good approach, because it forces WebDNA to run on a db that's not being used for anything else. > And I still add a crash, so memery problem... Maby not, we all > have been thinking of Webdna, Ram etc, but a 500 answer isn't it a > Apache error? I'm not sure without looking it up. What is the exact text of the error message? > I realised that this new db was still getting written after this > 500 error and I did get the right data in my db after all... Well then, WebDNA is not having a problem after all. Instead the browser is probably just timing out. > So isn't it in apache that I should setup a Timeout or KeepAlive Well, it certainly sounds like this might be a way to eliminate the apache timeout error if in fact what you've been getting is an apache timeout error. What are your current Apache settings? Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=55 Bug Reporting: support@webdna.us .
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
PCS Frames (1997)
WebCat2b12--[searchstring] bug (1997)
WebCat2b12--[searchstring] bug (1997)
Thread (1999)
WebCat2b12plugin - [search] is broken ... not! (1997)
sending two mails from one template (2004)
Emailer and encryption (1997)
Emailer (1997)
Running 2 two WebCatalog.acgi's (1996)
Press Release hit the NewsWire!!! (1997)
Variable Prices (1998)
really wierd browser truncating (1997)
test (2004)
Help formatting search results w/ table (1997)
Searching multiple fields from one form field (1997)
Storebuilder Seems to have just died (2003)
Spawn not working (1999)
Navigator 4.01 (1997)
Date field search needs ... (1998)
Web requests in que... (2007)