perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pas Argenio <pas.arge...@gmail.com>
Subject Re: mod_perl-2.0.4 with Apache 2.2.9 and perl 5.10.0 intermittent crashing
Date Wed, 27 Jan 2010 19:05:14 GMT
No, wish I were. East coast US, unseasonably warm (we have more hot air in
general).

I'm building everything from source.  I've rebuilt perl a half-dozen times
both static & dynamic.  I'm working on building 5.10.1 but it seems so
different in the build defaults.
Still to try: mod_perl.2.0.3 and using perl malloc

On Wed, Jan 27, 2010 at 1:50 PM, Tosh Cooey <tosh@1200group.com> wrote:

> perl -V
>
> I don't think it's an Apache issue, my purely superstitious feelings based
> on the ravens I saw flying around this morning is that blame lies with perl
> 5.10, I just don't trust even number releases, even less round numbers
> cleanly divisible by 10.
>
> But then $r scares me so...
>
> Are you in Europe?  It's really cold here, so maybe Apache needs to warm up
> first like a car, it takes a couple moments before it turns over?
>
> But in all seriousness I am also having the same problem.  How did you
> create your setup?  From packages or building everything from source?
>
> I'm using packages and suspect fault there as well...
>
> Tosh
>
>
> Pas Argenio wrote:
>
>> I just fell back to Apache-2.2.8 but same problem.  By the way, Tosh, how
>> did you dump the libperl info?
>> I'm getting more core dumps than you, but pages are displayed by the next
>> child to pick it up.  Here is the most common stack trace (via Solaris'
>> pstack command):
>>
>> Wed Jan 27 09:06:35 EST 2010
>> core '/tmp/core' of 13862:    /usr/local/apache/bin/httpd -k start
>>  fee56ec8 t_delete (528c90, 228, 0, fecb2e24, fef303a8, c20360) + 74
>>  fee56ac4 realfree (528a60, 229, d995c, fee56eb0, 0, 528a58) + 8c
>>  fee56610 _malloc_unlocked (528598, 6f8, 528590, ff, 0, 0) + 260
>>  fee56394 malloc   (4c8, 1, da058, fee563a0, fef303a8, fef3a518) + 4c
>>  fec8ae8c Perl_safesysmalloc (4c8, 0, 2000000, fffffff8, c000004, c329d9)
>> + 10
>>  fecc2294 Perl_sv_grow (d17680, 4c8, 0, 2000000, 4cb, 0) + f8
>>  fecbd094 Perl_sv_setsv_flags (84408, 4c7, 12c04540, d17680, d177e0,
>> ff800000) + ea0
>>  fecbd5ac Perl_sv_mortalcopy (d177e0, 5e65d0, fed76000, 78, fed74400,
>> d17680) + 60
>>  fecb2e24 Perl_pp_aassign (fed76294, 5b8c20, 5b8c0c, 5b8c1c, 0, fed74400)
>> + 154
>>  fecaa830 Perl_runops_standard (0, fecb2cd0, fed75c88, 91c2c0, fed75c00,
>> 91cec0) + 1c
>>  feca4ce0 Perl_call_sv (fed75c00, fed76000, fed76000, fed75c00, fed75c00,
>> 91c2c0) + 4a4
>>  fec1ca94 modperl_callback (0, 44b410, 44b450, ab4b8, 160080, fed76000) +
>> 338
>>  fec1d05c modperl_callback_run_handlers (fed75dec, 4, 44b450, 121dc8,
>> ab4b8, 0) + 31c
>>  fec1d32c modperl_callback_per_dir (6, 44b450, 1, 1, ffbff03c, 214678) +
>> 24
>>  fec19ab4 modperl_response_handler_run (44b450, 0, 1460, 0, fed761d8,
>> fed76000) + 18
>>  fec19cc4 modperl_response_handler_cgi (44b450, 4484b8, 121520, 0, 99070,
>> 9) + 134
>>  0003bfe4 ap_run_handler (44b450, 0, c, 449018, 448728, 0) + 3c
>>  0003c460 ap_invoke_handler (44b450, 77400, 44b450, 0, fe780020, 0) + b8
>>  000547f8 ap_process_request (44b450, 0, 4, 44b450, 0, 443728) + 160
>>  00051964 ap_process_http_connection (4436c8, 443430, 443430, 0, 998d0, 2)
>> + 10c
>>  00042790 ap_run_process_connection (4436c8, 443430, 443430, 0, 441438,
>> 4453f8) + 3c
>>  00067a10 child_main (0, 0, 99c00, 99800, 11177, 99800) + 42c
>>  00067c74 make_child (67400, 0, 0, fe781020, 440fc8, 0) + ec
>>  00067d44 startup_children (5, feebd280, 0, 10, 1cf4, a) + 68
>>  000686b0 ap_mpm_run (a4878, 99800, ab4b8, 99c00, 99800, 99800) + 950
>>  000291f4 main     (a4878, 96c00, 99000, 99000, a2870, 0) + 780
>>  00028594 _start   (0, 0, 0, 0, 0, 0) + 5c
>>
>> My MPM is straight pre-fork, default 5 children to start with.
>>  Unfortunately, this stuff needs to go into production soon.
>>
>>
>>
>> On Wed, Jan 27, 2010 at 11:42 AM, Tosh Cooey <tosh@1200group.com <mailto:
>> tosh@1200group.com>> wrote:
>>
>>    I'm seeing the same thing on my DEV server which is:
>>
>>    Server: Apache/2.2.11 (Ubuntu) mod_perl/2.0.4 Perl/v5.10.0
>>
>>    I see it in the mornings when it has been sitting around all night
>>    doing nothing, and the first couple hits result in core dumps/seg
>>    faults, then after pounding REFRESH like a mad monkey a couple times
>>    it then works.
>>
>>    This is on an Amazon EC2 Ubuntu 9.04 jaunty AMI built by Eric Hammond
>>    http://alestic.com  http://ec2ubuntu-group.notlong.com
>>
>>    perl -V:
>>
>>
>>    Summary of my perl5 (revision 5 version 10 subversion 0) configuration:
>>     Platform:
>>       osname=linux, osvers=2.6.24-23-server,
>>    archname=i486-linux-gnu-thread-multi
>>       uname='linux rothera 2.6.24-23-server #1 smp wed apr 1 22:22:14
>>    utc 2009 i686 gnulinux '
>>       config_args='-Dusethreads -Duselargefiles -Dccflags=-DDEBIAN
>>    -Dcccdlflags=-fPIC -Darchname=i486-linux-gnu -Dprefix=/usr
>>    -Dprivlib=/usr/share/perl/5.10 -Darchlib=/usr/lib/perl/5.10
>>    -Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5
>>    -Dvendorarch=/usr/lib/perl5 -Dsiteprefix=/usr/local
>>    -Dsitelib=/usr/local/share/perl/5.10.0
>>    -Dsitearch=/usr/local/lib/perl/5.10.0 -Dman1dir=/usr/share/man/man1
>>    -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/local/man/man1
>>    -Dsiteman3dir=/usr/local/man/man3 -Dman1ext=1 -Dman3ext=3perl
>>    -Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Ud_ualarm -Uusesfio
>>    -Uusenm -DDEBUGGING=-g -Doptimize=-O2 -Duseshrplib
>>    -Dlibperl=libperl.so.5.10.0 -Dd_dosuid -des'
>>
>>       hint=recommended, useposix=true, d_sigaction=define
>>       useithreads=define, usemultiplicity=define
>>
>>       useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
>>       use64bitint=undef, use64bitall=undef, uselongdouble=undef
>>       usemymalloc=n, bincompat5005=undef
>>     Compiler:
>>       cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN
>>    -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
>>    -D_FILE_OFFSET_BITS=64',
>>       optimize='-O2 -g',
>>       cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN
>>    -fno-strict-aliasing -pipe -I/usr/local/include'
>>       ccversion='', gccversion='4.3.3', gccosandvers=''
>>       intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
>>       d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
>>
>>       ivtype='long', ivsize=4, nvtype='double', nvsize=8,
>>    Off_t='off_t', lseeksize=8
>>       alignbytes=4, prototype=define
>>     Linker and Libraries:
>>       ld='cc', ldflags =' -L/usr/local/lib'
>>       libpth=/usr/local/lib /lib /usr/lib /usr/lib64
>>       libs=-lgdbm -lgdbm_compat -ldb -ldl -lm -lpthread -lc -lcrypt
>>       perllibs=-ldl -lm -lpthread -lc -lcrypt
>>       libc=/lib/libc-2.9.so <http://libc-2.9.so>, so=so,
>>
>>    useshrplib=true, libperl=libperl.so.5.10.0
>>       gnulibc_version='2.9'
>>     Dynamic Linking:
>>       dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
>>       cccdlflags='-fPIC', lddlflags='-shared -O2 -g -L/usr/local/lib'
>>
>>
>>
>>    Characteristics of this binary (from libperl):
>>     Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV
>>                           PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP
>>    USE_ITHREADS
>>                           USE_LARGE_FILES USE_PERLIO USE_REENTRANT_API
>>     Built under linux
>>     Compiled at Jun 26 2009 18:23:00
>>     @INC:
>>       /etc/perl
>>       /usr/local/lib/perl/5.10.0
>>       /usr/local/share/perl/5.10.0
>>       /usr/lib/perl5
>>       /usr/share/perl5
>>       /usr/lib/perl/5.10
>>       /usr/share/perl/5.10
>>       /usr/local/lib/site_perl
>>       .
>>
>>
>>    Of course this could also just be all the illegitimate bastard
>>    apache children I have been spawning being totally unprepared to
>>    answer a real web request, but I'm keeping an eye on this server...
>>
>>    Tosh
>>
>>
>>
>>    Pas Argenio wrote:
>>
>>        Sorry if this is naive, but has anyone gotten this combo to
>>        work?  Upgraded to Apache 2.2.14, now crash on almost every
>>        request, then next httpd picks up the request and actually
>>        displays the page...
>>
>>        I've got massive core dumps all ending in malloc/free, truss
>>        shows last operation was close()
>>
>>
>>    --    McIntosh Cooey - Twelve Hundred Group LLC -
>> http://www.1200group.com/
>>
>>
>>
> --
> McIntosh Cooey - Twelve Hundred Group LLC - http://www.1200group.com/
>

Mime
View raw message