Upgrading to BDA V2.5 on OL5 Fails at Step 2 Patching the Factory Image with Connection Timeouts and Does not Reboot
(Doc ID 1910339.1)
Last updated on JULY 25, 2014
Applies to:Big Data Appliance Integrated Software - Version 2.5.0 and later
The symptoms are listed below:
1. During an upgrade from Oracle Big Data Appliance(BDA) V2.2.1 to V2.5 using the Mammoth Software Upgrade Bundle on OL5, Step 2, Patching the Factory Image fails with:
INFO: Error is : ssh: connect to host bdanode05 port 22: Connection timed out
More detailed output looks like:
In summary, we can conclude that the upgrade to BDA 2.5 is fully successful if a) the uname output shows the kernel is correctly upgraded b) the two grub files are consistent and look correct c) the post-upgrade validation checks are successful.
Note: To diagnose the root cause for why the patch factory image step did not detect that a new kernel was installed and reboot and determine why imageinfo did not report the correct kernel collect:
1. The top level upgrade log found in a directory like:
There might be a few files in this path i.e. ones from other './mammoth -p' runs but the one wanted will be the one containing: "INFO: Patching factory image. This will take some time ..."
2. The post_upgrade_script_*.out files from each node in the cluster found in the directories:
/opt/oracle/bda/deployment-summary and under /bda/install/log/upgrade*
They will look like:
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