Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Manual rollback for a failed vRealize Log Insight 4.8 to 8.0 upgrade (75150)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 9821Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The upgrade of vRealize Log Insight 4.8 to 8.0 fails and automated rollback does not occur

Purpose

If you are in the middle of the upgrade and the upgrade fails, manual rollback can always be applied to revert to SLES based vRealize Log Insight.

Resolution

To preform the manual rollback, chose one of the following options.

Option 1

Log into the vRealize Log Insight Primary node as root via SSH or Console.

Open /boot/grub/default in a text editor.

Change the contents from 4 to 1.

Reboot the VM.

Repeat steps 1-4 on all other nodes in the vRealize Log Insight cluster that have already been upgraded.

Option 2

Note: this option will not select the OS permanently, but only for this reboot.

Log into the vCenter UI.

Right-Click on a vRealize Log Insight node and choose Edit Settings.

Navigate to the VM Options tab.

Under Boot Options, check the box for Force BIOS setup and click OK.

Reset or Restart the vRealize Log Insight VM from vCenter.

Exit the BIOS setup.

On the GRUB menu Photon OS will be your default. Use arrow up key to select SUSE Linux Enterprise Server 11 SP4 - 3.0.101-108.21 which should be listed as the second option.

Press Enter to boot into the SLES based vRealize Log Insight.

Repeat steps 2-8 on all other nodes in the vRealize Log Insight cluster.

If you have a cluster where some of the nodes have already been upgraded and are running on Photon while others are still running on SLES, it is highly recommended to apply the above steps not only for the failing node, but for all the nodes that have already been upgraded.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vRealize Operations Manager 中的环境视图限于 1000 个虚拟机 (75148)

KB
•
VMware vSphere InitiateFileTransferToGuest API の動作 (75075)

KB
•
利用持有者令牌 - 检索用户信息：包含用户数据的已解码 base64 持有者令牌中存在不一致问题 (75137)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Log Insight

Related Versions:

VMware vRealize Log Insight 8.x

Take Our Survey

Support Assistant