Re: troubleshooting seg fault/child exit
This is going to be long. It's also incomplete because I want to run one more test that came to me this AM. -- Output of perl -v: This is perl, version 5.005_02 built for PA-RISC2.0 Copyright 1987-1998, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5.0 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page. -- Ouptut of perl -V: Summary of my perl5 (5.0 patchlevel 5 subversion 2) configuration: Platform: osname=hpux, osvers=11.00, archname=PA-RISC2.0 uname='hp-ux hpprobe b.11.00 a 9000800 869669421 two-user license ' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize=' ', gccversion= cppflags='-D_HPUX_SOURCE -Aa -I/usr/local/include' ccflags ='-D_HPUX_SOURCE -Aa -I/usr/local/include' stdchar='unsigned char', d_stdstdio=define, usevfork=false intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=undef, longlongsize=, d_longdbl=define, longdblsize=16 alignbytes=8, usemymalloc=y, prototype=define Linker and Libraries: ld='ld', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib/pa1.1 /lib /usr/lib /usr/ccs/lib libs=-lnsl -lnm -lndbm -ldld -lm -lc -lndir -lcrypt -lcl libc=/lib/libc.sl, so=sl, useshrplib=false, libperl=libperl.a Dynamic Linking: dlsrc=dl_hpux.xs, dlext=sl, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-B,deferred ' cccdlflags='+z', lddlflags='-b -L/usr/local/lib' Characteristics of this binary (from libperl): Built under hpux Compiled at Nov 30 1999 15:00:56 %ENV: PERL_AIOC="/sp1/perl_aioc" @INC: /usr/local/lib/perl5/5.00502/PA-RISC2.0 /usr/local/lib/perl5/5.00502 /usr/local/lib/perl5/site_perl/5.005/PA-RISC2.0 /usr/local/lib/perl5/site_perl/5.005 . -- mod_perl version: 1.21 configure is run as follows (building out of /usr/local/src): perl Makefile.PL \ APACHE_SRC=../apache_1.3.9 \ DO_HTTPD=1 \ USE_APACI=1 \ PREP_HTTPD=1 \ EVERYTHING=1 -- apache version: 1.3.9 configure for mod_perl-enabled apache as follows: CC=cc EXTRA_CFLAGS=+e ./configure \ --activate-module=src/modules/perl/libperl.a \ --disable-module=auth \ --disable-module=autoindex \ --disable-module=imap -- make test: passes 100% as follows: (numerous skippings of unchanged .pm and .h files deleted for brevity) cp t/conf/mod_perl_srm.conf t/conf/srm.conf ../apache_1.3.9/src/httpd -f `pwd`/t/conf/httpd.conf -X -d `pwd`/t httpd listening on port 8529 will write error_log to: t/logs/error_log letting apache warm up...done /usr/bin/perl t/TEST 0 still waiting for server to warm up...ok ok ok modules/actions.ok modules/cgi.ok modules/constants...ok modules/cookie..skipping test on this platform modules/fileok modules/httpdconf...ok modules/include.ok modules/log.ok modules/module..skipping test on this platform modules/perlrun.ok modules/perlrunxs...skipping test on this platform modules/psections...skipping test on this platform modules/request.skipping test on this platform modules/sandwichskipping test on this platform modules/src.ok modules/ssi.ok modules/stage...skipping test on this platform modules/status..ok modules/symbol..skipping test on this platform modules/uri.ok modules/utilok internal/apiok internal/auth...ok internal/croak..ok internal/dirmagic...ok internal/error..ok internal/headersok internal/hooks..ok internal/http-get...ok internal/http-post..ok internal/proxy..ok internal/redirect...ok internal/rwrite.ok internal/stackedok internal/table..ok internal/taint..ok All tests successful, 8 tests skipped. Files=36, Tests=370, 26 wallclock secs (18.47 cusr + 1.30 csys = 19.77 CPU) kill `cat t/logs/httpd.pid` rm -f t/logs/httpd.pid rm -f t/logs/error_log -- mod_perl-enabled apache started up as follows: /isg/WWW/bin/httpd_perl -X -d/isg/WWW -f conf/modperl.conf no errors on startup. Only notation in its error log is that it is starting up server configuration as follows: --cut here-- ServerType standalone Port90 Useraisgadm Group staff ServerAdmin [EMAIL PROTECTED] # -- do NOT perform a reverse DNS lookup on the incoming conx # HostNameLookups off # -- ServerRoot: where the server's config, error, and log files are kept # ServerRoot /isg/WWW AccessConfig/dev/null ResourceConfig /dev/null # -- Log file locations/settings # ErrorLoglogs/error.modperl TransferLog logs/access_modperl PidFile logs/modperl.pid ScoreBoardFile
Re: troubleshooting seg fault/child exit
I am having a problem similar to yours... Whenever I try an connect to Oracle (using DBD and DBI), I am getting a segmentation fault / child pid exit error. But this only happens under mod_perl, and only on one box in particular. If I move the exact same script to another box, everything works great. Also, if I write a command line perl script that talks to Oracle (e.g., does not use mod_perl), everything is fine. I ran into this problem once before, and I forget what I did to fix it. I don't recall that it was anything in the script itself - perhaps a setting in one of Apache's .conf files? Throughout my testing today, I am led to believe it has something to do with either Apache or mod_perl, and not with any particular script... Any help would be appreciated. Jason Simms __ Get Your Private, Free Email at http://www.hotmail.com
Re: troubleshooting seg fault/child exit
Jason Simms wrote: I am having a problem similar to yours... Whenever I try an connect to Oracle (using DBD and DBI), I am getting a segmentation fault / child pid exit error. But this only happens under mod_perl, and only on one box in particular. If I move the exact same script to another box, everything works great. Also, if I write a command line perl script that talks to Oracle (e.g., does not use mod_perl), everything is fine. What Hardware/software have you observed this on? I have been seeing the _exact same symptoms_ for the better part of a month while attempting to rehost my team's website. My HW/SW: HP-UX 11.0 (with HP's ANSI-C compiler) Oracle 7.3.4 perl 5.005_02 mod_perl 1.21 apache 1.3.9 DBI 1.13 DBD::Oracle 1.03 I've tried gcc 2.95 instead of HP's ANSI-C compiler, with the exact same results. I even tried compiling everything static, again with no success. This is a configuration which (under slightly earlier versions of everything) is currently up on a production machine running HP-UX 10.20, so I've been more than a little frustrated. Throughout my testing today, I am led to believe it has something to do with either Apache or mod_perl, and not with any particular script... Any help would be appreciated. I had traced the problem to an interaction between mod_perl and the Oracle libraries linked into DBD. If the fix is as simple as correcting some settings in the .conf files, that means I won't have to spend the better part of tomorrow reinstalling Oracle. I *had* decided the problem had lain in how it had been installed instead of with the apache end of things until about five minutes ago. Ges
Re: troubleshooting seg fault/child exit
The reason I don't think it has anything to do with DBD is that, as I said, I have been able to use a script which calls DBD::Oracle not running under mod_perl and everything works great. This is on the same box that dies when calling DBD through mod_perl. And again, the same script, when run on a different box with the same verison of DBI and DBD, runs fine. Therefore, if the problem does lie in the communication with DBD as per your hypothesis), it must be a mod_perl communication problem, as "regular" Perl is able to use the same module and talk to Oracle without a hitch... For reference, my hw/sw is: Solaris 2.7 (gcc) Oracle 8.0.6 Perl 5.005_03 mod_perl 1.21 Apache 1.3.9 DBI 1.13 DBD::Oracle 1.03 What I find odd is that all of the sudden people seem to be coming out of the woodwork about this stuff. Whe I searched through mailing list archives, some of them going back years, I found something odd... Many people were talking about this same problem between December of last year and January of this year. No one found a satisfactory solution (at least, I didn't see one). Some blamed it on pre-loading CGI.pm in startup.perl, while others blamed it on having a PerlFreshRestart On in the Apache confguration scripts. This seems to be a pretty big deal, if so many people are complaining under so many configurations, and apparently it has gone on for over a year. Jason Simms __ Get Your Private, Free Email at http://www.hotmail.com
Re: troubleshooting seg fault/child exit
[Tue Dec 14 15:44:22 1999] [notice] child pid 13243 exit signal Segmentation fault (11) -- ... If someone could please point me in the right direction or FAQ, I, and my sanity, would be most happy. there are quite a few tips on debugging core dumps posted between last night and today, along with the SUPPORT doc. trying building a libperld.a, build mod_perl with PERL_DEBUG=1, and post a stacktrace.
Re: troubleshooting seg fault/child exit
What I find odd is that all of the sudden people seem to be coming out of the woodwork about this stuff. Whe I searched through mailing list archives, some of them going back years, I found something odd... Many people were talking about this same problem between December of last year and January of this year. No one found a satisfactory solution (at least, I didn't see one). Some blamed it on pre-loading CGI.pm in startup.perl, while others blamed it on having a PerlFreshRestart On in the Apache confguration scripts. This seems to be a pretty big deal, if so many people are complaining under so many configurations, and apparently it has gone on for over a year. core dumps can happen for many different reasons. why there are so many these past couple of days, I don't know, but doubt they are all triggered by the same thing. if you could follow suit and post a stacktrace from gdb, that would help.
