Apache 2.2 Webgate 126.96.36.199.0 Fail, Child Pid NNNNN Exit Signal Segmentation Fault (11)
(Doc ID 2122439.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 188.8.131.52.5 and later
Information in this document applies to any platform.
Apache 2.2 Webgate crash with Constant Segmentation Fault.
Apache error.log show :
[Wed Mar 30 11:25:05 2016] [notice] WebLogic Server Plugin version 1.1 <WLSPLUGINS_184.108.40.206.0_LINUX.X64_130212.0859>
[Wed Mar 30 11:25:05 2016] [notice] Apache/2.2.15 (Unix) DAV/2 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Wed Mar 30 11:25:13 2016] [notice] child pid 30037 exit signal Segmentation fault (11)
[Wed Mar 30 11:25:16 2016] [notice] child pid 30038 exit signal Segmentation fault (11)
[Wed Mar 30 11:25:16 2016] [notice] child pid 30039 exit signal Segmentation fault (11)
[Wed Mar 30 11:25:17 2016] [notice] child pid 30040 exit signal Segmentation fault (11)
- Because oblog.log was not created during start attempt this indicate that the webgate crashed when attempt to do initialization itself.
- https://en.wikipedia.org/wiki/Segmentation_fault mention about segmentation fault:
A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access,or attempts to access a memory location in a way that is not allowed
New Apache 2.2 Webgate 220.127.116.11.0.0 install.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|