<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Apache coredump on Stop in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962949#M101288</link>
    <description>I just installed the latest version of Apache on an L-Class running HPUX 11.  Apache starts up OK but when I stop the web server it produces a core dump.  The stop seems to be successful but I'm left with an ugly core file on disk.  Any ideas???&lt;BR /&gt;&lt;BR /&gt;hpuxwsAPACHE          A.2.0.55.02    HP-UX Apache-based Web Server&lt;BR /&gt;&lt;BR /&gt;# ./apachectl stop&lt;BR /&gt;./apachectl[188]: 13683 Memory fault(coredump)</description>
    <pubDate>Mon, 27 Feb 2006 14:04:05 GMT</pubDate>
    <dc:creator>Chris J. Solarczyk</dc:creator>
    <dc:date>2006-02-27T14:04:05Z</dc:date>
    <item>
      <title>Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962949#M101288</link>
      <description>I just installed the latest version of Apache on an L-Class running HPUX 11.  Apache starts up OK but when I stop the web server it produces a core dump.  The stop seems to be successful but I'm left with an ugly core file on disk.  Any ideas???&lt;BR /&gt;&lt;BR /&gt;hpuxwsAPACHE          A.2.0.55.02    HP-UX Apache-based Web Server&lt;BR /&gt;&lt;BR /&gt;# ./apachectl stop&lt;BR /&gt;./apachectl[188]: 13683 Memory fault(coredump)</description>
      <pubDate>Mon, 27 Feb 2006 14:04:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962949#M101288</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-27T14:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962950#M101289</link>
      <description>post the output of the command "file core" would give us the name of what process caused the core.&lt;BR /&gt;&lt;BR /&gt;patch levels upto date as per apache recommendations ? 11.00 or 11.11 ? &lt;BR /&gt;&lt;BR /&gt;if reproduceable anything eating resources ? maybe use glance to check ?</description>
      <pubDate>Mon, 27 Feb 2006 14:14:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962950#M101289</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2006-02-27T14:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962951#M101290</link>
      <description># file core&lt;BR /&gt;core:           core file from 'httpd' - received SIGSEGV&lt;BR /&gt;&lt;BR /&gt;# what core&lt;BR /&gt;core:&lt;BR /&gt;        HP-UX libisamstub.sl 19991217 (135120)  B3907DB/B3909DB B.11.01.11&lt;BR /&gt;        fs_amod.s $Revision: 1.9.1.1 $&lt;BR /&gt;        libcl.sl version B.11.01.04 - Jul 10, 2000&lt;BR /&gt;        HP-UX libm shared PA1.1 C math library 980423 (163456)   UX 11.0&lt;BR /&gt;        STREAMS:        Revision: B.11.00  $Date: 99/07/07 14:00:00 $&lt;BR /&gt;        Pthread Interfaces&lt;BR /&gt;        libpthread HP-UX (Release B.11.00): Tue Aug 31 15:35:32 PDT 1999&lt;BR /&gt;         $ PATCH/11.00:PHCO_22076  Aug 16 2000 16:53:50 $&lt;BR /&gt;         SMART_BIND&lt;BR /&gt;        92453-07 dld dld dld.sl B.11.13 990903</description>
      <pubDate>Mon, 27 Feb 2006 14:18:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962951#M101290</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-27T14:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962952#M101291</link>
      <description>Chris best I can offer is check kernel tuneables &lt;A href="http://www.hp.com/products1/unix/webservers/apache/techtips/hpapache_20_perf.html" target="_blank"&gt;http://www.hp.com/products1/unix/webservers/apache/techtips/hpapache_20_perf.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;that said it maybe we are seeing a known feature that may well be patcheable ... depends on how recent patch levels are ? &lt;BR /&gt;&lt;BR /&gt;If I remember I'll check when I'm back in the office tomorrow.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Feb 2006 14:42:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962952#M101291</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2006-02-27T14:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962953#M101292</link>
      <description>Does it do the same thing when you specify the fully qualifed path instead of doing the dot-slash reference?&lt;BR /&gt;&lt;BR /&gt;mark</description>
      <pubDate>Mon, 27 Feb 2006 16:11:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962953#M101292</guid>
      <dc:creator>Mark Greene_1</dc:creator>
      <dc:date>2006-02-27T16:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962954#M101293</link>
      <description>Yes, same thing happens without the ./&lt;BR /&gt;&lt;BR /&gt;I installed the following patch but it didn't seem to fix the problem.  Didn't see any other patch requirements.&lt;BR /&gt;&lt;BR /&gt;PHSS_33032            1.0            ld(1) and linker tools cumulative patch</description>
      <pubDate>Mon, 27 Feb 2006 16:16:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962954#M101293</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-27T16:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962955#M101294</link>
      <description>Chris,&lt;BR /&gt;&lt;BR /&gt;  yes I looked at the known issues that fixed and none matched , the libisam.sl might be worth a look at as may if gdb is installed producing a back trace .... (bt) advise use the gui.&lt;BR /&gt;&lt;BR /&gt;I'll see what I can find tomorrow ... glance show anything wrt memory etc  ?</description>
      <pubDate>Mon, 27 Feb 2006 16:25:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962955#M101294</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2006-02-27T16:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962956#M101295</link>
      <description>glance looks OK.  The server has 4GB of RAM with about 2.5GB free so not much memory pressure.</description>
      <pubDate>Mon, 27 Feb 2006 16:39:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962956#M101295</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-27T16:39:29Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962957#M101296</link>
      <description>It is barely possible that the memory violation is occurring because maxssiz is set too small especially if maxssiz is still at the default of 8MB. If so, increase it to 32MB but no more than 64MB. The stack would only need to be larger than about 32MB on very poorly written code.&lt;BR /&gt;&lt;BR /&gt;Plan B. Download and install Apache 2.2.0 from &lt;A href="http://www.apache.org." target="_blank"&gt;www.apache.org.&lt;/A&gt; It's a very easy build.</description>
      <pubDate>Mon, 27 Feb 2006 16:45:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962957#M101296</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-02-27T16:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962958#M101297</link>
      <description>maxssiz is set to 100MB.  This server also runs Oracle which may explain why it's set so high.  &lt;BR /&gt;&lt;BR /&gt;I'm just surprised that HP's Apache would have these problems right out of the box.  I installed the latest version on another server and the same thing happens with the 'stop' command.  It coud be a patch problem since these servers are behind in patches.  I may try to download the source and build it myself.</description>
      <pubDate>Mon, 27 Feb 2006 17:17:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962958#M101297</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-27T17:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962959#M101298</link>
      <description>I downloaded the source from apache.org for version 2.0.55 and compiled using gcc.  Everything is working OK.  I am able to start/stop the web server without a core dump.  Not sure what's wrong with the packaged install from HP...</description>
      <pubDate>Mon, 27 Feb 2006 23:16:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962959#M101298</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-27T23:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962960#M101299</link>
      <description>Well, if you are interested in finding the problem, you should be able to run the HP supplied version and allow it to crash and then use gdb to run a stack trace. You will at least know the function that triggered the crash and can look at that function very carefully for bugs in the source code for the "good" 2.0.55 version,</description>
      <pubDate>Tue, 28 Feb 2006 00:55:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962960#M101299</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-02-28T00:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962961#M101300</link>
      <description>Hi Chris I maybe off the mark here but PHSS_30969&lt;BR /&gt;&lt;BR /&gt;s700_800 11.00 ld(1) and linker tools cumulative patch PHSS_32574 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;s700_800 11.X HP aC++ -AA runtime libraries (aCC A.03.61)&lt;BR /&gt;&lt;BR /&gt;might have been worth installing along with installing the  2.14 Web server suite I think this may have been seen b4</description>
      <pubDate>Tue, 28 Feb 2006 03:29:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962961#M101300</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2006-02-28T03:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962962#M101301</link>
      <description>The problem was resolved by installing the following patches:&lt;BR /&gt;&lt;BR /&gt;  PHSS_33032            1.0            ld(1) and linker tools cumulative patch&lt;BR /&gt;  PHSS_33262            1.0            HP aC++ -AA runtime libraries&lt;BR /&gt;&lt;BR /&gt;Thanks to all that replied and offered their advice...</description>
      <pubDate>Tue, 28 Feb 2006 11:09:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962962#M101301</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-28T11:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Apache coredump on Stop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962963#M101302</link>
      <description>Closing the thread...</description>
      <pubDate>Tue, 28 Feb 2006 11:12:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/apache-coredump-on-stop/m-p/4962963#M101302</guid>
      <dc:creator>Chris J. Solarczyk</dc:creator>
      <dc:date>2006-02-28T11:12:33Z</dc:date>
    </item>
  </channel>
</rss>

