Hello! Windows 2003, Apache 2.2.9, active state perl. There is a huge script which does a lot of data manipulations and working with mysql. Suddenly, when number of products in orders grew it stopped working. The script's perl precess was in the memory, but there were no lines in access log or error log AT ALL. After 2 days of figuring out what was going on we discovered that too many warn statements were stopping the process. We deleted warn statements and it started to work again. It worked before because there were not too many products in orders and since warn is in the loop the overall ouput to stderr was within some kind of limit. After the number of products grew the warn output grew a lot more and everything stopped. The weird thing is that is such case there is no record in the access log and not even a part of warn output. So, i think, that apache under windows writes all logs in a bufferred manner and only does it after cgi script finished. I guess too many warnstatements fill up that stderr buffer and after that script waits for the buffer to become free and apache does not free it.
This seems to be a terrible feature for debugging process. Any comments? -- Artem --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|