> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Montag, 13. Juni 2005 19:31
> To: users@httpd.apache.org
> Subject: RE: [EMAIL PROTECTED] Fw: signal Bus error with apache
> Apache/2.0.54 with SSL pages
>
>
> OK - I tired a new setting in my mail client
OK - I tired a new setting in my mail client - let me know if this comes as
plain text.
Responses are in-line.
And here is new chain of thought:
After studying Ethereal traces taken during the problem, this problem
appears to occur anytime my browser attempts to re-use the SSL session ID.
I hav
You must've missed my earlier plea for plain text... I can't inline quote HTML
mail.
Did you cross reference the errors to the access log and find they were caused
by requests for GIFs?
How are the GIFs obtained - from a file on a local disk or by some magic (DB
access, generation by a script
All,
I upgraded to openssl-0.9.7g. I
still have the bus errors.
Thank you.
Chuck Borton
JPMorgan Chase & Co.
Global Network Engineering
Office: 614-213-8757
Cell: 614-477-4334
Pager: [EMAIL PROTECTED]
Charles E Borton
[EMAIL PROTECTED]
06/11/2005 12:00 AM
Please respond to users
Boyle,
Thanks for the info.
When I upgraded to 2.0, I did clean
compile and installed into a new directory. Based upon your comments,
I checked by startup script to verify that I'm not referring to any old
libraries. All references are to apache 2 directories.
The problem I'm experiencing (a
Plain text please...
To recap, you upgraded from 1.3 to 2 and now you get occassional bus errors.
My guess is that certain requests are triggering a call to a function in an
extension module or library and that the module was compiled for 1.3 and is not
compatible with apache 2.
To find the re
