Oracle HTTP Server Failing to Start with httpd: symbol lookup error and httpd: undefined symbol
(Doc ID 2524705.1)
Last updated on JUNE 05, 2023
Applies to:
Oracle HTTP Server - Version 12.1.3.0.0 and laterInformation in this document applies to any platform.
OHS cannot be started through Node Manager, or directly with apachectl.
Symptoms
On Oracle HTTP Server (OHS) 12c, unable to start the httpd process through Node Manager, or directly with the apachectl command.
This can be tested by means of running lastinvocation.log as a script when troubleshooting the start up issue.
NOTE: For OHS 12c, in the logs folder for OHS, there is a lastinvocation.log which logs the commands used to start OHS, as well as environment variables needed to start OHS. Changing permissions to 755 will allow it to be ran as a script.
This is the most direct way to start OHS without any external entanglements and is a good way to test if the problem is at OHS or in the underpinning Apache Server. This would be ran as follows: $ ./lastinvocation.log, or one could make a copy of the file and call it lastinvocation.sh.
This is the most direct way to start OHS without any external entanglements and is a good way to test if the problem is at OHS or in the underpinning Apache Server. This would be ran as follows: $ ./lastinvocation.log, or one could make a copy of the file and call it lastinvocation.sh.
The following can be observed in the Node Manager log output:
Changes
OHS may have been patched recently, or patches rolled back, or other changes in the installation file system have resulted in the present state.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |