Re: Apache exiting with 152

Posted by ErmanArslansOracleBlog on May 29, 2023; 7:39am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Apache-exiting-with-152-tp11857p11924.html

Hi Satish,

I couldn't find time to analyze the strace output, but it seems you fixed the issue.

**Is it a cloud instance? Because This is already documented  for OCI and that directive should have been there already. But! I think it should be applicable to ON-PREM as well! So, cool solution ..
So, under the hood, you made semaphores to be used rather than the lock files. Lock files are not required. (according to the FMW 11.1.1.9 Admin Guide)

*
Here -> Sharing the Application Tier File System in Oracle E-Business Suite Release 12.2 or 12.1.3 Using the Oracle Cloud Infrastructure File Storage Service (Doc ID 2794300.1) .. And there reference of that MOS note comes from the FMW documented itself (from Oracle HTTP Server 11.1.1.9
Fusion Middleware Administrator's Guide for Oracle HTTP Server)

Beginning with the primary application tier node, update the httpd.conf as follows:
Launch the Fusion Middle Control. For example, use the following URL: http://<hostname.domain:admin_port>/em
Select and edit the httpd.conf file.
Update AcceptMutex fcntl to the following AcceptMutex sysvsem (found in two places in the httpd.conf file).
Comment out the LockFile directive (found in three places in the httpd.conf file).
Save the file and exit the Fusion Middleware Control.
Restart the HTTP server for the configuration changes to take effect.
Repeat steps 1 through 6 for all secondary nodes in the environment.

Note that: We had fnctl in the strace, just before the timeout output is given :

fcntl(5, F_SETFD, FD_CLOEXEC)           = 0
connect(5, {sa_family=AF_INET6, sin6_port=htons(6110), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=htonl(0), sin6_scope_id=0}, 28) = 0
open("/u01/PRODAPPS/fs2/FMW_Home/webtier/instances/EBS_web_OHS2/config/OPMN/opmn/.formfactor", O_RDONLY) = 6
fstat(6, {st_mode=S_IFREG|0400, st_size=27, ...}) = 0


Some additional info:

The AcceptMutex directives sets the method that Apache uses to serialize multiple children accepting requests on network sockets.

sysvsem : Uses SySV-style semaphores to implement the mutex..

fcntl:Uses the fnctl system call to lock the file defined by the LockFile directive

Maybe ( I didn't test it), Linux semaphores will need to be manually cleaned up if HTTP Server crashes abnormally.  If such a crash happens, you can use ipcs -a to see that, and  ipcrm -s to clean them. (but only maybe, I didn't test it... just saying)