Re: [WebDNA] WebDNA7 and mod_fcgi
This WebDNA talk-list message is from 2013
It keeps the original formatting.
numero = 110574
interpreted = N
texte = yes, it *feels* like that (what Chris says) to me too - some (legacy?) = code somewhere eats too much RAM (near the limit) .. which Webdna does = not recover from well ... and so Webdna stays in that limited-RAM state = (*even though* RAM should have meanwhile been freed up again; the = offending script has long since stopped parsing). I bet there is some = bad code in the Webdna engine itself ... that does not do "garbage = collection" properly... does not re-free up RAM that was used, under = certain conditions ... and when our scripts get near the hardware RAM = limit, then this weakness, in the heart of Webdna, gets uncovered. I = have been watching this behavior, off an on, since the late 1990's. Rebooting fixes it, until the situation it repeated. It does not have to occur when Webdna has been up a long time.. the = situation can be repeated within a minute of rebooting.. if a = too-RAM-intensive script it parsed again. Assuming my intuition is accurate, I think that without ability to fix = the real issue inside Webdna, our best bet is to prevent our scripts = pushing the envelope too much, in RAM. I don't know anything for sure.. but what I type here is my BEST = intuition on the topic ... repeatedly, over the years. -Govinda On 2013-08-17, at 2:55 AM, christophe.billiottet@webdna.us wrote: > According to these two errors pointing at mod_fcgid, i would suggest = to restart apache or reboot the whole server: the memory footprint of = the server has probably increased because of a long uptime period. A = simple reboot should fix it. WebDNA.fcgi itself is not involved in this = error. >=20 > - chris >=20 >=20 >=20 >=20 > On Aug 16, 2013, at 11:07 PM, Dan Strong
wrote: >=20 >> Apache error logs littered with these two errors (15000+/day): >>=20 >> 1) [warn] (103)Software caused connection abort: mod_fcgid: = ap_pass_brigade failed in handle_request function >> 2) [notice] mod_fcgid: too much /var/www/html/domain.com/page.html = process(current:1, max:1), skip the spawn request >=20
Associated Messages, from the most recent to the oldest:
yes, it *feels* like that (what Chris says) to me too - some (legacy?) = code somewhere eats too much RAM (near the limit) .. which Webdna does = not recover from well ... and so Webdna stays in that limited-RAM state = (*even though* RAM should have meanwhile been freed up again; the = offending script has long since stopped parsing). I bet there is some = bad code in the Webdna engine itself ... that does not do "garbage = collection" properly... does not re-free up RAM that was used, under = certain conditions ... and when our scripts get near the hardware RAM = limit, then this weakness, in the heart of Webdna, gets uncovered. I = have been watching this behavior, off an on, since the late 1990's. Rebooting fixes it, until the situation it repeated. It does not have to occur when Webdna has been up a long time.. the = situation can be repeated within a minute of rebooting.. if a = too-RAM-intensive script it parsed again. Assuming my intuition is accurate, I think that without ability to fix = the real issue inside Webdna, our best bet is to prevent our scripts = pushing the envelope too much, in RAM. I don't know anything for sure.. but what I type here is my BEST = intuition on the topic ... repeatedly, over the years. -Govinda On 2013-08-17, at 2:55 AM, christophe.billiottet@webdna.us wrote: > According to these two errors pointing at mod_fcgid, i would suggest = to restart apache or reboot the whole server: the memory footprint of = the server has probably increased because of a long uptime period. A = simple reboot should fix it. WebDNA.fcgi itself is not involved in this = error. >=20 > - chris >=20 >=20 >=20 >=20 > On Aug 16, 2013, at 11:07 PM, Dan Strong wrote: >=20 >> Apache error logs littered with these two errors (15000+/day): >>=20 >> 1) [warn] (103)Software caused connection abort: mod_fcgid: = ap_pass_brigade failed in handle_request function >> 2) [notice] mod_fcgid: too much /var/www/html/domain.com/page.html = process(current:1, max:1), skip the spawn request >=20
John Butler
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:
[WebDNA] WebDNA 7 multiple fcgid processes (2012)
serial number generation (1997)
Credit card arrangement (2005)
setheader and retrieve it immediatly (2001)
Include (2000)
Bug or syntax error on my part? (1997)
Problem with version 4 browsers (1998)
Document Contains No Data! (1997)
[PHP3] php vs WebCatalog (2000)
separate by mont (search) (2002)
off topic (1999)
File Upload, Browser Timeout (2003)
Re1000001: Setting up shop (1997)
BadSuffix with 2.1b3 cgi (1997)
Shopping Cart Problems (2000)
WebCat2 beta 11 - new prefs ... (1997)
(thx) automating a POST (2002)
WebCat2b12plugin - [search] is broken ... not! (1997)
Range compare... (2000)
SMSI FTP - calander system (2002)