CGI's output to stderr is logged in the server's default error_log instead of the error_log for the virtual server with the corresponding SuexecUserGroup directive. Perhaps there is an architectural limitation that lead to the current implementation. If its not feasible to log the suexec'd CGI's stderr to the corresponding error_log of the virtual server, then PLEASE record the full path of the CGI in the system's default error_log. At least then it becomes possible to later parse the log and report errors back to the owners of the virtual servers. Thanks for your time reading and responding to this. P.S. Fantastic work guys. I love Apache 2!
is this with mod_cgi or mod_cgid?
I'm using mod_cgid and the worker MPM on a single processor x86 2.4.18 kernel. When using the worker MPM, what is the latest recommendation for the latest x86 Linux kernels? mod_cgi or mod_cgid?
This is a more general problem than just with suexec. Henry, I'm sorry I didn't see your update before. Regarding your question on what to use: mod_cgid is always the recomendation when using a threaded MPM. With prefork MPM, mod_cgi is almost always the better choice. However, folks with CGIs that generate a lot of output to stderr encounter problems with mod_cgi that don't occur with mod_cgid. Clear as mud? *** This bug has been marked as a duplicate of 14090 ***
Yup, I'm clear .. I did some more homework. I'm using the correct one (mod_cgid) with MPM worker. However, I only experienced problems after switching to using suexec. Prior to that, stderr seemed to go to the right places. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14090 is definitely a duplicate of the bug I opened. Sorry I missed that entry when looking for existing reports of this problem.