Instructions to Reinstall/Upgrade RPMs on the Oracle Big Data Appliance Nodes

Asset ID:	1-79-1596582.1
Update Date:	2017-10-14
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1596582.1 : Instructions to Reinstall/Upgrade RPMs on the Oracle Big Data Appliance Nodes

Applies to:

Big Data Appliance Integrated Software
Big Data Appliance Hardware
Linux x86-64

Purpose

This document provides instructions on

a) How to re-install corrupted RPM's on the Oracle Big Data Appliance(BDA) Nodes.

b) How to upgrade RPM's incase the RPM's didn't get upgraded correctly during Mammoth upgrade.

RPM corruption may occur during install/upgrade of Mammoth software or accidental removal. If RPM corruption occurs during install/upgrade then /root/BDA_REBOOT_FAILED file will be generated and also failures will be reported by bdachecksw / bdacheckcluster scripts.

Scope

Oracle Big Data Appliance(BDA)Administrators

Details

One solution would be manually copying the RPM's from node01 to the needed nodes and installing using 'rpm --replacepkgs -ihv <rpmname>' command. This option has the overhead of copying the rpm's across the BDA nodes.

Another option would be to use yum command, as there is a yum repository server named bda running on Node01 of BDA Cluster. Also all the nodes in the BDA cluster contain bda.repo file in /etc/yum.repos.d directory.

# pwd
/etc/yum.repos.d
# ls
bda.repo
# more bda.repo
[bda]
baseurl=http://<node01>-master.us.oracle.com/bda
gpgcheck=0
proxy=_none_
enabled=1

Note:- dlci can be used to check if all the nodes in BDA Cluster contain the bda.repo file

# dcli -C ls /etc/yum.repos.d

Executing 'yum upgrade' or 'yum reinstall' command from any of the BDA nodes might result in 'Connection refused' error

# yum reinstall <rpmname>
Loaded plugins: rhnplugin, security
Repository 'bda' is missing name in configuration, using id
This system is not registered with ULN.
ULN support will be disabled.
Setting up Reinstall Process
http://<node01>-master.us.oracle.com/bda/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>

The error can occur during download of the packages if NOT occured during Dependency check.

Downloading Packages:
http://<node01>-master.us.oracle.com/bda/RPMS/x86_64/******.rpm: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
Trying other mirror.

The error is caused since httpd service on node 1 is stopped after Mammoth install/upgrade is completed.

Follow below steps as root user to enable httpd service and execute the needed yum command to reinstall/upgrade RPM's on the BDA nodes

1) Check the status of the httpd service on node01

# service httpd status
httpd is stopped

2) Start httpd service on node01

# service httpd start
Starting httpd: [ OK ]
# service httpd status
httpd (pid 13543) is running...

3) For list of yum commands and description refer to yum Man Page.

# man yum

4) If there are multiple .repo files in /etc/yum.repos.d directory containing links to the rpm being installed/upgraded then use ' yum --disablerepo' option so that bda.repo will be the one used.

# yum --disablerepo=<3rd party repo files> reinstall/upgrade <packagename>

5) Command to upgrade an rpm

# yum upgrade <packagename>

6) Command to reinstall the rpm's on any node in the BDA cluster

# yum reinstall <packagename>

Sample output

# yum reinstall <rpmname>
Loaded plugins: rhnplugin, security
Repository 'bda' is missing name in configuration, using id
This system is not registered with ULN.
ULN support will be disabled.
Setting up Reinstall Process
Resolving Dependencies
--> Running transaction check
---> Package <rpmname>.i386 0:0.5.8.1-62.el5 set to be updated
---> Package <rpmname>.x86_64 0:0.5.8.1-62.el5 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package       Arch             Version                     Repository     Size
================================================================================
Reinstalling:
<rpmname>           i386             0.5.8.1-62.el5              bda           391 k
<rpmname>           x86_64           0.5.8.1-62.el5              bda           377 k

Transaction Summary
================================================================================
Remove        0 Package(s)
Reinstall     2 Package(s)
Downgrade     0 Package(s)

Total download size: 768 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): <rpmname>-0.5.8.1-62.el5.x86_64.rpm                     | 377 kB     00:00
(2/2): <rpmname>-0.5.8.1-62.el5.i386.rpm                       | 391 kB     00:00
--------------------------------------------------------------------------------
Total                                            12 MB/s | 768 kB     00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing     : <rpmname>                                                      1/2
Installing     : <rpmname>                                                      2/2

Installed:
<rpmname>.i386 0:0.5.8.1-62.el5             <rpmname>.x86_64 0:0.5.8.1-62.el5

Complete!

7) Once reinstall/upgrade of RPM's is done execute bdacheckcluster command to make sure there are NO RPM related errors.

8) Stop httpd service on node01 once the yum operations are completed.

# service httpd stop
Stopping httpd: [ OK ]
# service httpd status
httpd is stopped

Attachments

This solution has no attachment