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

vRealize Operations 8.1 Upgrade hangs on step 4 of 9 - Wait for Cassandra to start (78571)

Last Updated: 4/14/2020Categories: TroubleshootingTotal Views: 7070Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The vRealize Operations cluster uses IPv6.

The in-place upgrade to vRealize Operations 8.1 hangs on step 4 of 9 on one or more analytic nodes.

The executing status of the Master node shows Wait for Cassandra to start.

The /storage/log/vcops/log/dbupgrade_timestamp.log on the Master node shows entries similar to:

2020-04-02 17:02:11,884 - INFO - main:601 - Cassandra version has changed, upgrading sstables.
2020-04-02 17:02:11,886 - INFO - cluster_sstable_upgrade:165 - Calling CaSA to upgrade the Cassandra cluster
2020-04-02 17:02:11,887 - DEBUG - getSuiteProperty:140 - STORAGE: '/storage'
2020-04-02 17:02:12,001 - DEBUG - runHttpRequest:203 - Code: 200 - Body: b''
2020-04-02 17:02:12,001 - DEBUG - runHttpRequest:220 - Open URL: 'https://localhost/casa/cassandra/cluster/sstable/upgrade' response code: 200
2020-04-02 17:02:12,002 - INFO - main:603 - Wait for ss table upgrade clusterwide.
2020-04-02 17:02:12,003 - INFO - wait_for_ssupgrade_ready:502 - Calling CaSA to get for ss table status
2020-04-02 17:02:12,003 - DEBUG - getSuiteProperty:140 - STORAGE: '/storage'
2020-04-02 17:02:12,043 - DEBUG - runHttpRequest:203 - Code: 200 - Body: b'false'
2020-04-02 17:02:12,044 - DEBUG - runHttpRequest:220 - Open URL: 'https://localhost/casa/cassandra/cluster/sstable/status' response code: 200
2020-04-02 17:02:12,044 - INFO - wait_for_ssupgrade_ready:515 - retrying in 10 seconds
2020-04-02 17:02:12,055 - INFO - wait_for_ssupgrade_ready:502 - Calling CaSA to get for ss table status
2020-04-02 17:02:12,055 - DEBUG - getSuiteProperty:140 - STORAGE: '/storage'
2020-04-02 17:02:12,104 - DEBUG - runHttpRequest:203 - Code: 200 - Body: b'false'
2020-04-02 17:02:12,104 - DEBUG - runHttpRequest:220 - Open URL: 'https://localhost/casa/cassandra/cluster/sstable/status' response code: 200
2020-04-02 17:02:12,104 - INFO - wait_for_ssupgrade_ready:515 - retrying in 10 seconds

Cause

This is caused by a known issue with IPv6 nodes.

Resolution

To resolve the issue, remove the self-generated IPv6 (Scope:Global) entries from all affected Analytic (Data and Replica) nodes, except the Master node.

Log into an affected node as root via SSH or Console.

Note: Type ALT+F1 in a Console to log in.

Run the following command to output the configuration of the eth0 interface:

ifconfig eth0

In the output, note any entries ending in Scope:Global, except the entry containing the assigned IPv6 address.

Example: Note the bold entries below.
eth0      Link encap:Ethernet  HWaddr 00:50:56:88:82:b3
inet6 addr: fc00:10:145:155:250:56ff:fe88:82b3/64 Scope:Global
inet6 addr: fc00:10:145:154:250:56ff:fe88:82b3/64 Scope:Global
inet6 addr: fc00:10:145:153:250:56ff:fe88:82b3/64 Scope:Global
inet6 addr: fc00:10:145:152:aaaa:bbbb:cccc:fcc3/64 Scope:Global
inet6 addr: fc00:10:145:152:250:56ff:fe88:82b3/64 Scope:Global
inet6 addr: fe80::250:56ff:fe88:82b3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:34217193 errors:0 dropped:22891 overruns:0 frame:0
TX packets:2386776 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2368254775 (2.3 GB)  TX bytes:528352773 (528.3 MB)

Run the following command to delete each invalid entry noted in step 3:

ip addr del address dev eth0

Note: Replace address with the address portion of the entries noted in step 3.

Examples:
ip addr del fc00:10:145:155:250:56ff:fe88:82b3/64 dev eth0
ip addr del fc00:10:145:154:250:56ff:fe88:82b3/64 dev eth0
ip addr del fc00:10:145:153:250:56ff:fe88:82b3/64 dev eth0
ip addr del fc00:10:145:152:250:56ff:fe88:82b3/64 dev eth0

Run the following command to re-triage the sstable upgrade action:

curl -X POST -ik -u "admin:password" https://master_address/casa/cassandra/cluster/sstable/upgrade

Note: Replace password with the admin user's password and replace master_address with the IP address or FQDN of the Master node.

Example: curl -X POST -ik -u "admin:VMware1!" https://vrops-ipv6-master.vcloud.local/casa/cassandra/cluster/sstable/upgrade

Repeat steps 1-5 on all affected nodes.

Once completed, the upgrade process will continue as normal.

The upgrade progress can be monitored in the Admin UI, where the Master node's status should move past the Wait for Cassandra to start status.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Workspace ONE SDK 20.3 (Swift) for iOS リリースのお知らせ (78609)

KB
•
Workspace ONE Tunnel 4.2 for macOS リリースのお知らせ (78627)

KB
•
Workspace ONE Intelligence for Consumer Apps 2020/04/16 リリースのお知らせ (78628)

KB
•
VMware Workspace ONE Intelligence 2020/04/16 リリースのお知らせ (78629)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Operations Manager

VMware vCenter Operations

Related Versions:

VMware vRealize Operations 8.1.x

Take Our Survey

Support Assistant