× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Folks:

Had a weird situation the other day ... someone notified me that a
single page on my website wasn't displaying.  No specific error, but no
page either.

I went to the page and saw the same thing.  I couldn't figure it out.
So I checked the main error log for apache ... and I saw the
following... "child pid 14075 exit signal Segmentation fault (11)"

Unfortunately, I couldn't figure out what was causing the segfault.

Upon some investigation, I noticed that the file was exactly 8192 bytes
long.  On a lark, I manually edited the file to change it's size to 8193
(added a blank).

The page displayed fine.

When I removed the extra blank, so the file was 8192 bytes again ... it
segfaulted when displayed.

The system is a Redhat 7.3 with Apache 1.3.27 (yeah, I know it's old ...
but it works {mostly}).

The pages that are being served are static and are on a nfs mount (if
that makes any difference).

The only module I'm using is mod_layout so I can add some content to
every page.

Any suggestions on how to figure out what is causing the segfault on an
8k file?

Thanks!

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.