OHS Fails to Start With Syntax Errors Loading Modules After Applying and Rolling Back the Patch 29407043
(Doc ID 2550736.1)
Last updated on JUNE 16, 2021
Applies to:Oracle HTTP Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After applying the patch 29407043, OHS fails to start with error.
Even after rollback of the patch, it still fails with same error.
The DOMAIN_HOME/servers/ohs1/logs/ohs1.log shows
[OHS] [INCIDENT_ERROR:32] [OH99999] [weblogic] [host_id:<HOSTNAME>l] [host_addr: <IPADDRESS>] [pid: <PID>] [tid: <TID> ] [user: root] [VirtualHost: main] (22)Invalid argument: Could not set permission for mutex lock!
The DOMAIN_HOME/system_components/OHS/ohs_nm.log shows the following errors:
OHS started on privileged ports and all the steps mentioned in the document are followed.
Reference Starting Oracle HTTP Server Instances on a Privileged Port (UNIX Only) at URL:
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