Hi, I got to the technical reason behind this issue. Looks like the fix may be to increase the request timeout on the apache side. Can someone tell me which timeout parameter to increase:
The basic cause is thathe segmentation fault being generated by ssl3_write_pending(). This happens when a timeout occurs during ap_send_fd() or ap_send_mmap(). The Apache timeout() handler is invoked by the SIGALRM handler, which closes the connection and frees the SSL context. When the signal handler finishes and returns to the stack (where we were in the middle of a write operation somewhere inside of ssl3_write_pending()), ssl3_write_pending() segfaults when it tries to access the non-existent context. thx Sailesh On Thu, Feb 28, 2008 at 1:41 PM, Joshua Slive <[EMAIL PROTECTED]> wrote: > On Thu, Feb 28, 2008 at 11:56 AM, Sailesh Krishnamurthy > <[EMAIL PROTECTED]> wrote: > > As you said, this may be better pursued over the mod_ssl mailing list. > > The problem is similar to the one described here: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg21131.html > > > > if i can find the culprit cgi app, that may help. can enable duebug > loggin > > in apache help? > > do let me know. > > Unlikely. If you were using a recent version, mod_log_forensic would > allow you to find the problem request. But if you use ancient > versions, you've got to expect problems. > > Joshua. > > --------------------------------------------------------------------- > 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: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >