Date: Sat, 12 Jun 2004 15:45:09 +0200 From: Mathieu Arnold <mat@FreeBSD.org> To: jamie+gmane@silverdream.org, freebsd-stable@freebsd.org Subject: Re: OTRS, apache2 & mod_perl2 Message-ID: <7854D3959D0FF88B959F3CF3@nescarba.in.t-online.fr> In-Reply-To: <pan.2004.06.11.22.08.44.792101@silverdream.org> References: <pan.2004.06.11.22.08.44.792101@silverdream.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--==========6623FDAB3F2A53DEB0CE========== Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline +-le 11/06/2004 23:08 +0100, Jamie L. Penman-Smithson =E9crivait : | -----BEGIN PGP SIGNED MESSAGE----- | Hash: SHA1 |=20 | I'm running FreeBSD 4.9 and I've been trying to get OTRS to work with | apache2 and mod_perl2, both from ports. However, whether I use apache2 | with mod_perl2 or apache13 with mod_perl the apache process dies with a | segfault: |=20 | [Fri Jun 11 23:00:20 2004] [notice] child pid 92298 exit signal | Segmentation fault (11) |=20 | Which is all apache displays even on the highest LogLevel. In | /var/log/messages all I see is: |=20 | Jun 11 23:01:18 solaris pid 92299 (httpd), uid 80: exited on signal 11 | Jun 11 23:01:18 solaris pid 92301 (httpd), uid 80: exited on signal 11 |=20 | Does anyone have any [successful] experience of setting up OTRS with | apache2/mod_perl ...? </plea> |=20 | I've fiddled here and there and not been able to glean anything more, OTRS | seems to be working fine - I've discussed this on the OTRS mailing list | and it appears to be a problem with apache and mod_perl. As an aside - I | tried rt3 from ports and it segfaulted too, suggesting/confirming that the | problem is something to do with apache. The fact that the problem occurs | with apache2 *and* apache13 and both versions of mod_perl is strange, | though... |=20 | I'd be grateful for an ideas |=20 | Thanks in advance, I don't know what ORTS is but I know that there could be some conflicts with apache13/expat if using perl modules as XML::Parser, so you could have -DWITHOUT_APACHE_EXPAT. If using apache2, you could set CoreDumpDirectory[1] so that you get an apache core dump and you could know where the prolem lies. [1] <http://httpd.apache.org/docs-2.0/mod/mpm_common.html#coredumpdirectory>; --=20 Mathieu Arnold --==========6623FDAB3F2A53DEB0CE========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iQEVAwUBQMsI6lvROjYJ63c1AQLS1QgAjATPVVXamXLH4zp4+rqTenAcQU6pBTti OxsjgkcER4DDK+chSVJGQ23a++H9mrETap8Il8PjJi05+TRkSThC3wAfzO/g2Ahf QlLiDITWhXKdsBX6O6+cBQtlZEuw0h4dJZ3DBpu65//vd6v6+E2KFvun5ONd4BIA /3icRimmG64gAlH887GNW1sWe7/PUm7FZGhIilI7O2natfps/J6CRBE185Vnztdi V5Z3H/rfO1ZMBH1WsGOUnGw4TEAHF++mUfNhnKkWiQ3dVFWJhklLMsK1jXvWrNAk 9uXiMbamyNhDuhGLqW2FdPiMJTnK3ALXGPUhX9JuzruEIBitvoun/g== =c4KF -----END PGP SIGNATURE----- --==========6623FDAB3F2A53DEB0CE==========--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7854D3959D0FF88B959F3CF3>