Message-ID: <384725EB.C1775E82@ix.netcom.com>
Date: Thu, 02 Dec 1999 18:07:39 -0800
From: Sam Talebbeik <saeedt@ix.netcom.com>
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: Solaris 2.7 and getting a clean coredump
References: 
 <Pine.BSF.4.10.9912022152270.3735-100000@brunte.ispra.webweaving.org>
 <3846E267.5A257B0A@elmar.co.il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org
Status: O

You will fine some very good debugging tips at Apache's
own developer web site. Try the following link:

http://dev.apache.org/debugging.html

    ST.

Eli Marmor wrote:

> Solaris processes can't core dump after calling setuid().
> Try to run it as non-root (with port number > 1023) and a dir
> which is writable by the uid. You can also run it with "User"
> root (httpd.conf), or copy /usr/bin/gcore to a temporary and
> secret place, change its mode to 4755, and call it explitcitly
> from Apache before crashing.
>
> In addition, don't forget to ensure that limit coredumpsize is
> unlimited, and the directory where core is going to be dumped
> is writable by the user.
>
> DON'T FORGET TO RESTORE EVERYTHING LATER!  (httpd.conf, or the
> secret copy of gcore, etc.).
>
> Dirk-Willem van Gulik wrote:
> >
> > Anyone have any hints as how to proceed... apache bombs out with a
> > bus/segv's quite often.. and I'd like a core.
> >
> > As we have 200+ active processes and 50 req/second attaching a debuger to
> > PID's is not an option.. kind of difficult to guess which one :-)
> >
> > Now I've set/tried
> >
> >         ulimit -c unlimited
> >
> >         cd to the core-directory before startup
> >
> >         CoreDumpDirectory ...
> >
> >
> >         the coredump directory is rw for the world. There is
> >         enough disk space.
> >
> > A 'kill -SEGV' does not yield core's either, but a CGI like
> >
> >         #/usr/local/bin/perl
> >         $|++;
> >         print "Content-type: text/plain\n\n"
> >         exec "ulimit -a; kill -SIGV $$";
> >
> > produces one (of sh) just fine. Kind of suggesting that the inherited
> > child environment is fine.
> >
> > Of course the log nicely log's the child SIGV-ing in both cases. Even
> > though the SEGV of apache causes no core.
> >
> > Any hints. Same setup dumps fine on BSD.
> >
> > Any and all suggestions appreciated !
> >
> > Dw
>
> --
> Eli Marmor