Exapatch Fails During Upgrade Of Compute Node To Jan 2017 PSU

Asset ID:	1-72-2237941.1
Update Date:	2017-03-10
Keywords:

Solution Type Problem Resolution Sure

Solution 2237941.1 : Exapatch Fails During Upgrade Of Compute Node To Jan 2017 PSU

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.170117 to 2.0.6.2.170117
Exalogic Elastic Cloud X4-2 Hardware - Version X4 to X4 [Release X4]
Exalogic Elastic Cloud X3-2 Eighth Rack - Version X3 to X3 [Release X3]
Information in this document applies to any platform.

Symptoms

While patching Compute nodes on Exalogic rack to Jan PSU 2017 (2.0.6.2.170117), bellow Error is seen in exapatch logs (/var/log/exapatch).

INFO: Sun Feb 26 07:23:39 PST 2017: Completed copying /usr/lib/init-exalogic-node/supported_config_M5 to /var/tmp/ebi_conf.pre2062170117.bak/supported_config_M5
INFO: Sun Feb 26 07:23:39 PST 2017: Backup /usr/lib/init-exalogic-node/supported_config
INFO: Sun Feb 26 07:23:39 PST 2017: Completed copying /usr/lib/init-exalogic-node/supported_config to /var/tmp/ebi_conf.pre2062170117.bak/supported_config
INFO: Sun Feb 26 07:23:39 PST 2017: Backup /usr/lib/init-exalogic-node/supported_platform_data
INFO: Sun Feb 26 07:23:39 PST 2017: Completed copying /usr/lib/init-exalogic-node/supported_platform_data to /var/tmp/ebi_conf.pre2062170117.bak/supported_platform_dataINFO: Sun Feb 26 07:23:39 PST 2017: Completed Replacing oswbb script
ERROR: Sun Feb 26 07:23:39 PST 2017: Restarting oswbb service failed
INFO: Sun Feb 26 07:23:39 PST 2017: remove services that launch post patching procedures

Changes

Patching Compute Nodes on Exalogic fails with Error : Restarting oswbb service failed

Deleting or removing OSWBB directory causes this issue while patching.

This happens when OSWBB directory is moved or deleted manually. This is not a Patching issue. It is manual mistake at customer end.

Cause

This clearly shows that the oswatcher serivce is not configured/running correctly. Re-starting the oswbb service fails with the below error:-

#>service oswbb start
Starting OSWatcher: //usr///libexec/oswbb-service/oswbb-helper: line 34: cd: /opt/oswbb: No such file or directory
[FAILED]

Solution

This happens when oswatcher is misconfigured in the compute node. It is a very important and mandatory process to be up and running to capture memory related data.

This happened when we remove the "/opt/oswbb". Please validate the home directory of oswbb in /etc/oswbb.conf

# grep OSW_HOME /etc/oswbb.conf
# Set OSW_HOME to the directory where you unpacked OSW or OSWbba
OSW_HOME='/opt/oswbb'

Ensure that the files are there inside /opt/oswbb

NOTE: Although the issue was for Jan PSU 2017 but it may occur during any patching if OSWBB directory is missing under /opt/

Attachments

This solution has no attachment