DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34264>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34264 ------- Additional Comments From [EMAIL PROTECTED] 2005-04-01 21:41 ------- FWIW, I am able to hit the mod_cgid mess on the last Solaris 10 beta as well as Solaris 10 GA. Prior beta builds of Solaris 10 did not have the problem. I haven't tested mod_ssl any. This is 32-bit Solaris 10/x86 on Pentium 4. The failure is intermittent. Under CGI load, I have caused my box to reboot before, as mod_cgid daemon gets bogus data over the socket about how many bytes to allocate and tries to malloc too much. I can't recreate the failure with detailed tracing of one side of the socket (mod_cgid daemon or mod_cgid handler). The root cause of the problem is some corruption of information about CGI environment variables which is sent from the cgid handler over to the cgid daemon prior to creation of the CGI process. I have tweaked the mod_cgid code on both sides of the Unix socket to try to see what is required to trigger the problem, but without success. Meanwhile, we don't have reports of this type of problem occur on any other platform and it didn't occur on most of the publically-released beta versions of Solaris 10. That doesn't mean it can't possibly be an Apache bug, but it seems fairly likely that it is NOT an Apache bug. I've tried multiple levels of gcc (the two levels available from blastwave) with no change in behavior seen. So: I'm suggesting that an Apache change to fix this may not be forthcoming, and that you may see cgid problems without mod_ssl. I'd recommend that you stick with your prefork configuration (which uses mod_cgi and does not use a Unix socket) for now. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
