OHS Fails To Start With Invalid Argument: Could Not Set Permission For Mutex Lock!
(Doc ID 2540650.1)
Last updated on NOVEMBER 17, 2023
Applies to:
Oracle Fusion Middleware - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]Information in this document applies to any platform.
Symptoms
OHS fails with Invalid argument: Could not set permission for mutex lock!
[unixd:alert] [pid <PID>:tid <TID>] AH02155: getpwuid: couldn't determine user name from uid <ID>, you probably need to modify the User directive
[ossl:debug] [pid <PID>:tid <TID>] ossl_engine_pphrase.c(97): Environment variable ORACLE_SSL_ALLOW_MD5_CERT_SIGNATURES is not set
[ossl:debug] [pid <PID>:tid <TID>] ossl_engine_init.c(421): OHS:2055 Init: (oradweb:443) Configuring permitted SSL ciphers [SSL_RSA_WITH_AES_128_CBC_SHA:SSL_RSA_WITH_AES_256_CBC_SHA]
[weblogic:notice] [pid <PID>:tid <TID>] WebLogic Server Plugin version 12.2.1.3.0 <WLSPLUGINS_12.2.1.3.0_LINUX.X64_190313.2302>
[weblogic:info] [pid <PID>:tid <TID>] mod_weblogic: init_mod: mpm is threaded.
[weblogic:crit] [pid <PID>:tid <TID>] (22)Invalid argument: Could not set permission for mutex lock!
[:emerg] [pid <PID>:tid <TID>] AH00020: Configuration Failed, exiting
Changes
httpd.conf is not configured with User and Group values.
Applied 29407043
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 |