Eric S. Johansson wrote: >> > I'm getting a 500 error message from a reasonably long running CGI >> > program after about 15-20 seconds runtime. There is no output >> > apparently coming from my CGI program and everything seems to run >> > okay when it runs with a smaller data set. I'm seeing nothing in >> > the error log or the access log so I'm more than a little puzzled. >> > It's more than likely that it is my own CGI but I need some way of >> > getting in the middle to figure out what's going wrong. any >> > suggestions what may be happening or for the diagnostic approach? >> >> Ummmm.. try to increase CGI_TIMEOUT in macros.h, and recompile. >> >> Please, let me know if that fixes the problem for you :-) > > not yet. need to build up a bigger test case. but i found another case > that triggers a 500 quickly. had a script with wrong permissions and I > got the dreaded 500. running cherokee on the command line I saw a bunch > of non-fatal warnings from the cgi and: > > /usr/local/camram/cgi-bin/logout.cgi: could not execute the script
Actually, there were a few releases in which we checked for this, but then I realized that it doesn't worth to access() the file before executing it just to check if it has the right permissions. I mean, do we really want a slower server (at the end of the day, it is an additional system call) just to be able to show a fancy error message if a CGI has the wrong permissions? :-) > which should show up in th error log. fix perms problem, one set of > 500's went away. now working on second set. We could to this, but we would need to stat() or access() the CGI for almost nothing. > another error that needs logging is: > > 192.168.0.30 - - [15/Mar/2006:15:17:08 --500] "GET /favicon.ico > HTTP/1.1" 404 0 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; > rv:1.8) Gecko/20051111 Firefox/1.5" > 1 > > I have a favicon.ico 0 len file in doc root but is it not seen. the log > entry should help with debugging the problem. Could you please log a bug for this? If this is not a misconfiguration problem, we should forget about it. Actually, it is odd.. does it only happen to you with empty files? > and last, just wondering, do you send stderror to the error log on > cgi calls? No, it doesn't. Do you think we should do it? I don't think it is a good idea. For example, for my case, I would get huge log files filled with a nasty warning message that the PHP prints when it is launched.. -- Greetings, alo. _______________________________________________ Cherokee mailing list [email protected] http://www.0x50.org/cgi-bin/mailman/listinfo/cherokee
