Hi,

I've had a few problems getting AxKit to work on a specific server...

A few months ago, folks on the AxKit IRC channel helped me
try to fix this, but in the end, the problem was not solved. Unfortunately,
I haven't have time to continue to work on this until just recently.

The initial issue was: constant segfaults. Using: apache 1.3.24, perl 5.6.1
and AxKit 1.5.2.

Here's the error log:

[Sat Aug 10 12:39:04 2002] [notice] Apache/1.3.24 (Unix) AxKit/1.52
mod_perl/1.26 configured -- resuming normal operations
[Sat Aug 10 12:39:04 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sat Aug 10 12:39:19 2002] [notice] child pid 21351 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:20 2002] [notice] child pid 21352 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:21 2002] [notice] child pid 21354 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:21 2002] [notice] child pid 21353 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:22 2002] [notice] child pid 21355 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:23 2002] [notice] child pid 21357 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:23 2002] [notice] child pid 21356 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:24 2002] [notice] child pid 21358 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:25 2002] [notice] child pid 21360 exit signal Segmentation
fault (11)
[Sat Aug 10 12:39:25 2002] [notice] child pid 21359 exit signal Segmentation
fault (11)
[Sat Aug 10 12:40:24 2002] [notice] caught SIGTERM, shutting down


At first, it seemed the problem was one of the server's libraries. In any case,
the segfaults persisted even after the library was updated. (The above log, and
the following backtrace, were generated _after_ the library was updated.)

Here is the backtrace:

Program received signal SIGSEGV, Segmentation fault.
XS_AxKit_Debug (cv=0x8328530) at AxKit.xs:197
197
        if (level > cfg->debug_level) {

(gdb) bt
#0  XS_AxKit_Debug (cv=0x8328530) at AxKit.xs:197
#1  0x8109efc in Perl_pp_entersub () at eval.c:88
#2  0x8104870 in Perl_runops_standard () at eval.c:88
#3  0x80c789a in perl_call_sv () at eval.c:88
#4  0x80c7666 in perl_call_sv () at eval.c:88
#5  0x807da90 in perl_call_handler () at eval.c:88
#6  0x402760df in axkit_handler (r=0x8379664) at axconfig.c:1043
#7  0x8099b89 in ap_invoke_handler () at eval.c:88
#8  0x80af14f in ap_some_auth_required () at eval.c:88
#9  0x80af1b6 in ap_process_request () at eval.c:88
#10 0x80a5e56 in ap_child_terminate () at eval.c:88
#11 0x80a6011 in ap_child_terminate () at eval.c:88
#12 0x80a618c in ap_child_terminate () at eval.c:88
#13 0x80a681d in ap_child_terminate () at eval.c:88
#14 0x80a707c in main () at eval.c:88
#15 0x400a72eb in __libc_start_main (main=0x80a6ce8 <main>, argc=2,
ubp_av=0xbffff5f4, 
   init=0x8062818 <_init>, fini=0x8146cac <_fini>, rtld_fini=0x4000c130
<_dl_fini>, stack_end=0xbffff5ec)
    at ../sysdeps/generic/libc-start.c:129


It seems to me that other times I ran backtraces, I got slightly
different results.

Anyway, since a new AxKit was recently released, I installed it, to see
if the problems persisted. With 1.6, I get no segfaults, but AxKit
won't process any documents. With the following in the httpd.conf

<Perl>
        use Carp ();
        $SIG{__WARN__} = \&Carp::cluck;
        use lib qw(/home1/d/d2ia1/lib/perl5);

</Perl>

PerlModule AxKit
SetHandler perl-script
PerlHandler AxKit
AxAddStyleMap application/x-xpathscript Apache::AxKit::Language::XPathScript
AxLogDeclines On

AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT
AxDebugLevel 10


the server serves documents fine, but AxKit never does any
transforming--not even XPathScript works. I also don't get any log
messages explaining why AxKit declines to process the requests.

The only oddity about this configuration is that Apache, AxKit and
a few other Perl modules were not installed in default locations, but
in directories under ~, and were not installed with root privileges.

I should add that Sablotron is installed and running fine; I tested it outside
the AxKit context. But AxKit still doesn't process documents when I tell it to
use Sablotron instead of LibXSLT.

Thanks in advance,

Andrew

P.S. Hope nobody minds if I put in a plug for the hosting company that
runs the server--kattare.com. Excellent service, support, willing to
bend over backwards to help out...

-------------------------------------------------
Obtén tu correo en www.correo.unam.mx
UNAMonos Comunicándonos



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to