On 11.5.10.2 in Production:
When attempting to stop Apache using adapcctl.sh, the following error occurs.
ERROR
Service can not be stopped using this script
STEPS
The issue can be reproduced at will with the following steps:
1. Run adapcctl.sh stop
BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, unable to stop Apache successfully.
.
When attempting to stop Apache using adapcctl.sh, the following error occurs.
ERROR
Service can not be stopped using this script
STEPS
The issue can be reproduced at will with the following steps:
1. Run adapcctl.sh stop
BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, unable to stop Apache successfully.
.
Cause
The issue is caused by the following setup:
$IAS_ORACLE_HOME/Apache/Apache/logs/ directory contained both httpd.pid and
apache_runmode.properties
Files httpd.pid and httpd_pls.pid gets created when Apache is started in NORMAL mode.
File apache_runmode.properties gets created when Apache is started in RESTRICTED mode.
As both kind of files are present in Logs directory, adapcctl.sh script thinks Apache cannot be
started in both modes and fails to stop.
.
$IAS_ORACLE_HOME/Apache/Apache/logs/ directory contained both httpd.pid and
apache_runmode.properties
Files httpd.pid and httpd_pls.pid gets created when Apache is started in NORMAL mode.
File apache_runmode.properties gets created when Apache is started in RESTRICTED mode.
As both kind of files are present in Logs directory, adapcctl.sh script thinks Apache cannot be
started in both modes and fails to stop.
.
Solution
To implement the solution, please execute the following
steps:
1. Stop Apache / Kill all httpd processes if exists any.
2. Backup $IAS_ORACLE_HOME/Apache/Apache/logs
3. Delete all files under $IAS_ORACLE_HOME/Apache/Apache/logs/ directory.
4. Re-start Apache.
5. Retest the issue.
1. Stop Apache / Kill all httpd processes if exists any.
2. Backup $IAS_ORACLE_HOME/Apache/Apache/logs
3. Delete all files under $IAS_ORACLE_HOME/Apache/Apache/logs/ directory.
4. Re-start Apache.
5. Retest the issue.
No comments:
Post a Comment