[Catalyst] Catalyst modperl - child process segmentation fault

Toby Corkindale toby.corkindale at strategicdata.com.au
Tue Dec 9 06:46:57 GMT 2008

Terence Monteiro wrote:
> Toby Corkindale wrote:
>> Terence Monteiro wrote:
>>> Toby Corkindale wrote:
>>>> Terence Monteiro wrote:
>>>>> I'm running my Catalyst application on apache2 using modperl with mysql
>>>>> database accessed by DBIx::SearchBuilder. I'm getting the message in
>>>>> the
>>>>> apache2 error logs:
>>>>> child pid 1140 exit signal Segmentation fault (11), possible core dump
>>>>> in /tmp
>> ]snip]
>>>> Ugh.. Dumping core? That's rather drastic!
>>>> What versions of DBI and DBD::mysql are you running?
>>>> And is DBD::mysql linked against the same mysql client libraries as
>>>> mod_php?
>>> Thanks, Toby
>>> DBD::mysql version: 4.008
>>> DBI version:        1.607
>>> libapache2-mod-php5 version: 5.2.0-8+etch10
>>> How can I find out the mysql client libraries DBD::mysql and mod_php are
>>> linked with? What you say is possible because I upgraded DBD::mysql from
>>> the latest debian sources in unstable, but not (yet) mod_php. But I don't
>>> understand why mod_php should matter.
>> Could you humour me, and try disabling PHP in Apache, and then seeing if> 
>> that stops the Catalyst app crashing?
>> I think you can do it by 'rm /etc/apache/mods-enabled/*php*.load' or
>> something very similar?
> Thanks for the reply. I have switched to fastcgi deployment and so far have
> not had any segfaults. I will try what you're saying tonight, since being a
> production environment, I get downtime only after 7:30pm IST (0100 UTC).
>> To check the actual versions of libraries used, you can do:
>> ldd /usr/lib/apache2/modules/mod_php*.so
>> ldd /usr/lib/perl5/auto/DBD/mysql/mysql.so
>> (At least I'm pretty sure that's where the files should be on debian etch)
>> But if you've recompiled dbd::mysql from source, and not mod_php, then
>> I'll bet this IS the problem. Sorry.
> I installed both DBD::mysql and mod_php from debian packages
> (libdbd-mysql-perl and libapache2-mod-php5). I did not compile DBD::mysql
> (never have before).

Ah, sorry, I mistook something.

But I do think you said you installed the DBD::Mysql from a debian 
backports, whereas the mod_php was from etch stable?
So, the Debian crew have done the compiling for you, but still, the 
DBD::mysql is linked against mysqlclient from backports, while mod_php 
is linked against the stable mysql client libraries.

Another test would be to update all of perl, apache, mod_php, 
dbd::mysql, mod_perl etc from backports, so at least everything is from 
the same source.


More information about the Catalyst mailing list