RE: [users@httpd] Fw: signal Bus error with apache Apache/2.0.54 with SSL pages

[charles_e_borton@xxxxxxxxxxx]

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:  6144774334@xxxxxxxxxxxxxx



Charles E Borton

charles_e_borton@xxxxxxxxxxx 06/11/2005 12:00 AM Please respond to users

To:        users@xxxxxxxxxxxxxxxx         cc:                 Subject:        RE: [users@httpd] Fw: signal Bus error with apache Apache/2.0.54 with SSL pages

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 (around 60% of all SSL pages but not normal
pages) is occurring on straight html pages with gif images.   For
example, if I load a page with 10 gif images, I may get success on 4 images
and failure and bus errors on 6.  Usually by the 3rd refresh, I get
all of the images.   It's not restricted to just images.  Sometimes,
a straight html page or _javascript_ file will fail with the same bus error.

Any other suggestions? 

One question I have - what is the minimum version of openssl that is required
with apache 2.0?  I have - openssl-0.9.6l. 

Thank you. 


Chuck Borton
JPMorgan Chase & Co. 
Global Network Engineering
Office:  614-213-8757
Cell:  614-477-4334
Pager:  6144774334@xxxxxxxxxxxxxx



Charles E Borton

"Boyle Owen" <Owen.Boyle@xxxxxxx> 06/09/2005 05:08 AM Please respond to users

To:        <users@xxxxxxxxxxxxxxxx>        cc:                Subject:        RE: [users@httpd] Fw: signal Bus error with apache Apache/2.0.54 with SSL pages

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 request, cross reference, using the timestamp, the error log
with the access log. That will tell you what module is being accessed.
Then recompile it for apache 2.

Rgds,
Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored. 


-----Original Message-----
From: charles_e_borton@xxxxxxxxxxx [mailto:charles_e_borton@xxxxxxxxxxx]
Sent: Mittwoch, 8. Juni 2005 18:50
To: users@xxxxxxxxxxxxxxxx
Subject: [users@httpd] Fw: signal Bus error with apache Apache/2.0.54 with
SSL pages



All, 

My apologies.  I forgot to include the error message: 

[Wed Jun 08 11:11:37 2005] [notice] child pid 14430 exit signal Bus error
(10) 

Thank you. 


Chuck Borton
JPMorgan Chase & Co. 
Global Network Engineering
Office:  614-213-8757
Cell:  614-477-4334
Pager:  6144774334@xxxxxxxxxxxxxx

----- Forwarded by Charles E Borton/OH/ONE on 06/08/2005 12:45 PM -----
Charles E Borton Charles E Borton 
06/08/2005 11:33 AM         
       To:        users@xxxxxxxxxxxxxxxx
       cc:         
       Subject:        signal Bus error
with apache Apache/2.0.54 with SSL pages


Hi, 

I have recently upgraded to 2.0.54 from 1.3.29. 

In my new install, when users try to access the HTTPs portion of my site,
they get some (around 605) broken links (often on images but sometime on
whole pages). 

The broken links map to errors in the error log that look like this: 

Has anyone seen this before? 

Thank you. 


Chuck Borton
JPMorgan Chase & Co. 
Global Network Engineering
Office:  614-213-8757
Cell:  614-477-4334
Pager:  6144774334@xxxxxxxxxxxxxx


This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this transmission
in error, please immediately contact the sender and destroy the material
in its entirety, whether in electronic or hard copy format. Thank you.
Diese E-mail ist eine private und persönliche Kommunikation. Sie hat keinen
Bezug zur Börsen- bzw. Geschäftstätigkeit der SWX Gruppe. This e-mail is
of a private and personal nature. It is not related to the exchange or
business activities of the SWX Group. Le présent e-mail est un message
privé et personnel, sans rapport avec l'activité boursière du Groupe SWX.


This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in
error, please notify the sender urgently and then immediately delete the
message and any copies of it from your system. Please also immediately
destroy any hardcopies of the message. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you
are not the intended recipient. The sender's company reserves the right
to monitor all e-mail communications through their networks. Any views
expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorised to state them
to be the views of the sender's company.

---------------------------------------------------------------------
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: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx