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

VIO Deployment Start Hangs At 41% (53127)

Last Updated: 7/14/2020Categories: TroubleshootingTotal Views: 2648Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Starting deployment fails at 41% in the web client plugin.

/var/log/jarvis/ansible.log show similar to the following.

p=564 u=jarvis |  TASK: [config-db | flush privileges] ******************************************
p=564 u=jarvis |  changed: [10.0.131.202]
p=564 u=jarvis |  changed: [10.0.131.115]

Note:  The ansible task only completed on two of the three database nodes

On the database server that is missing from the above, /var/log/syslog will look similar to the following

database0x mysqld: 160901 16:58:36 [ERROR] WSREP: Address already in use
database0x mysqld: 160901 16:58:36 [ERROR] WSREP: failed to open gcomm backend connection: 98: error while trying to listen 'tcp://0.0.0.0:4567?socket.non_blocking=1', asio error 'Address already in use': 98 (Address already in use)

Cause

The MySQL service will start on boot and looks to see if the cluster is already running, like what would happen in a HA scenario. If time between the ESXi the VM boots on and the OMS is off,  this first boot MySQL process will not timeout/stop creating a race condition with the Ansible task that initiates the main node for the Maria cluster.

Resolution

Verify NTP servers are working and the following components are set for the same NTP.

vCenter

Add or Replace NTP Servers in the vCenter Server Appliance Configuration 6.5

Add or Replace NTP Servers in the vCenter Server Appliance Configuration 6.0

ESXi

Edit Time Configuration for a Host 6.5

Edit Time Configuration for a Host 6.0

Guide to configure NTP on ESX servers (1003063)

OpenStack Management Server

Connect to the vSphere web client.

Shutdown the OMS vApp

Edit settings of the vApp and add NTP servers to the NTP properties.

Power on the OMS from the vApp

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Integrated OpenStack

Related Versions:

VMware Integrated OpenStack 3.x

Take Our Survey

Support Assistant