It's amazing what you can find when you read the documentation and notes...
I found that I must now specifically define HTML::Mason::ApacheHandler in my
handler.pl script. I wasn't doing this and it appears that was causing my
seg faults.. It looks like this changed after v0.89. Now I have other
problems but they appear to be programming script issues not seg faults.
PS: I had already built Apache with Mod_Perl compiled in... same result.
----- Original Message -----
From: "Jared Rhine" <jared@...>
To: "Main Line Health" <mlhgods@...>
Sent: Saturday, April 07, 2001 6:05 AM
Subject: [Mason] Apache 1.3.19 + Mod_Perl 1.25 + Mason 1.015 = Segmentation
> [Citation date: Fri, 6 Apr 2001 21:53:48 -0400]
> >>>>> Mike == Main Line Health <mlhgods@...>
> Mike> Has anyone got any experience with the components mentioned
> Mike> above? I'm running a Redhat 7.1 Beta machine with Apache
> Mike> 1.3.19 + Mod_Perl v1.25 and Mason 1.015 and I'm getting
> Mike> segmentation fault in HTTPD when I try to start Apache. If
> Mike> I use Apache 1.3.12 with Mod_Perl v1.24 and Mason 0.87
> Mike> everything works perfectly with no problems.
> Very interesting. I'm running 1.3.19 + mod_perl 1.25 + Mason and also
> have seg fault issues. If you search around a bit, you'll find lots
> and lots of reports regarding segfaults, but there's very different
> causes. For instance, since you indicate a segfault upon startup, the
> stock answer is "you're probably linking with the expat library,
> possibly through inclusion by mod_dav".
> I stopped using mod_dav (and specifically excluded the expat library),
> but I still have seg faults. However, mine are sporadic and occur
> not during boot, but just to random apache children. So I'm probably
> having a different problem.
> Current best practices for segfault-free mod_perl include:
> - Static linking of apache binary
> - Removing all expat references, specifically by excluding mod_dav
> - Sometimes splitting apache into a 'frontend server' and a 'backend
> server' can help reduce.
> It seems unlikely that Mason is the cause of the actual segfaults;
> mod_perl seems to be the main culprit. An upgraded Mason running on
> the old apache and mod_perl would probably not segfault, if it works
> I'm very interested in the idea I might be able to revert versions and
> fix the problems.
> -- jared@...
> "Society in every state is a blessing, but Government, even in its
> best state, is but a necessary evil; in its worst state, an intolerable
> one." -- Thomas Paine
> Mason-users mailing list