After Applying OracleAS Patchset 4 (10.1.3.4), HTTP Server Core Dumps When Using Server-Status (Doc ID 784397.1)

Last updated on MAY 30, 2024

Applies to:

Symptoms

Oracle HTTP Server core dumps when attempting to use the server-status functionality

In the error_log this error is seen

[notice] child pid 422260 exit signal Segmentation fault (11)

and a core file is created in the Oracle Home. The stack trace from the core file shows:
(Example given below is from an AIX machine)

Segmentation fault in sig_coredump at 0x100037d4
0x100037d4 (sig_coredump+0x44) 80410014 lwz r2,0x14(r1)
(dbx) corefile
Process Name: <ORACLE_HOME>/Apache/Apache/bin/httpd
Version: 430
Flags: CORE_VERSION_1 | MSTS_VALID | UBLOCK_VALID | USTACK_VALID | LE_VALID
Signal: SEGV
Process Mode: 32 bit
(dbx) where
sig_coredump(??) at 0x100037d4
status_handler(??) at 0xd3de65e8
ap_invoke_handler(??) at 0x1002063c
process_request_internal(??) at 0x100470a4
ap_process_request(??) at 0x10048174
child_main(??) at 0x10001cf4
make_child(??, ??, ??) at 0x100016a0
startup_children(??) at 0x100014a0
standalone_main(??, ??) at 0x10000bf0
http_main.main(??, ??) at 0x10000794
(dbx) proc

The server-status output itself shows garbage characters

Server Version: Oracle-Application-Server-10g/ 10.1.3.4.0 Oracle-HTTP-Server
..
8 requests currently being processed, 0 idle servers
.?2??d??d....................
...............
.............

Changes

OracleAS 10g Rel 3 patchset 4 (10.1.3.4) has been applied

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.