Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 Manager 6.7 upgrade fails if IPv6 is disabled (54744)

Last Updated: 7/14/2020Categories: TroubleshootingTotal Views: 6157Language:
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

An Internal server error when attempting to access the software update page in the Admin UI.

When running service vmware-vcops status the following output appears on the problematic node:

Slice Online-false

Offline Reason-online_state.change_reason.bring_cluster_offline_for_adding_pak

admin Role Enabled-true

pg_ctl: could not open PID file "/storage/db/vcops/vpostgres/repl/postmaster.pid": Permission denied

vRealize Operations vPostgres Replication Database is not running.

vRealize Operations Gemfire Locator is not running.

data Role Enabled-true

pg_ctl: could not open PID file "/storage/db/vcops/vpostgres/data/postmaster.pid": Permission denied

vRealize Operations vPostgres Database is not running.

vRealize Operations Cassandra Distributed Database is not running.

vRealize Operations Analytics is not running.

vRealize Operations Collector is not running.

vRealize Operations API is not running.

ui Role Enabled-true

remote collector Role Enabled-false

On the problematic node the/storage/log/var/log/firstboot/firstbootInfrastructure.log has similar entries to:

2018-04-23 09:09:49,199 [25290] - root - INFO - run-firstboot-scripts - <module> - 235 - Run scripts:
2018-04-23 09:09:49,199 [25290] - root - INFO - run-firstboot-scripts - <module> - 237 - [Failed] /usr/lib/vmware-vcopssuite/firstboot/vsutilitiesFirstBoot.py

2018-04-23 09:09:49,200 [25290] - root - INFO - run-firstboot-scripts - <module> - 237 - [Finished] /usr/lib/vmware-casa/firstboot/casa-firstboot.py

2018-04-23 09:09:49,200 [25290] - root - INFO - run-firstboot-scripts - <module> - 237 - [Finished] /usr/lib/vmware-casa/firstboot/admin-app-firstboot.py

2018-04-23 09:09:49,200 [25290] - root - ERROR - run-firstboot-scripts - <module> - 243 - First boot is a failure

On the problematic node the /storage/log/var/log/firstboot/vsutilitiesFirstBoot.py_id_stdout.log has similar entries to:

ERROR: Script command: "/sbin/service apache2 start" failed with exit code: "1"

stdout: Apache VCOPS_APACHE_SERVER_NAME: x.x.x.x

Starting httpd2 (prefork) [Mon Apr 23 09:09:24 2018] [warn] module deflate_module is already loaded, skipping

[Mon Apr 23 09:09:24 2018] [crit] (EAI 9)Address family for hostname not supported: alloc_listener: failed to set up sockaddr for ::1

Syntax error on line 7 of /etc/apache2/listen.conf:

Listen setup failed

Cause

This issue is present when IPv6 has been disabled on any of the vRealize Operations Manager nodes in your cluster.

Resolution

This is a known issue affecting vRealize Operations Manager 6.7 upgrades.
This is currently no resolution.

Workaround

To workaround this issue, choose one of the following options:

Option 1

Revert back to your snapshots prior to upgrading.

Note: The cluster should be offline at this point.  If not, take the cluster offline in the Admin UI.

Log into the Primary node as root via SSH or Console

Open /etc/modprobe.conf.local in a text editor.

Verify the lines alias net-pf-10 off and alias ipv6 off do not exist.  If they do, delete the lines, then save and close the file.

Run the following commands to enabled IPv6 in /etc/sysctl.conf:

sysctl -w net.ipv6.conf.lo.disable_ipv6=0
sysctl -w net.ipv6.conf.all.disable_ipv6=0
sysctl -w net.ipv6.conf.default.disable_ipv6=0

Repeat steps 1-5 on all other nodes in the cluster.

Option 2

Revert back to your snapshots prior to upgrading.

Note: The cluster should be offline at this point.  If not, take the cluster offline in the Admin UI.

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

Identify which nodes have IPv6 disabled.

Note: Running ifconfig will not return an IPv6 address if IPv6 is disabled

Enable IPv6 by logging into the node as root via SSH or console.

Enter the folowing command, and wait for the graphical interface to load:

yast

Navigate to Network Devices > Network Settings.

Using Tab and arrow keys to navigate, in the Global Options section, check Enable IPv6.

Tap the F10 key to exit the Network Settings interface.

Tap the F9 key to quit YaST.

Repeat steps 1-8 on all other nodes in the cluster.

Related Information

Click Subscribe to Document in the Actions box to be notified when this article is updated.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vSAN における「APD タイムアウト通知をファイルシステムを登録できません。: デバイスに対する 不適切な ioctl 」メッセージ (2145444)

KB
•
Download and Install VMware Fusion (2014097)

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 Operations Manager

VMware vRealize Operations

Related Versions:

VMware vRealize Operations Manager 6.7.x

Take Our Survey

Support Assistant