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 MariaDB cluster will not start (78716)

Last Updated: 8/28/2020Categories: TroubleshootingTotal Views: 3868Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Using VMware Integrated Openstack 6.x

MariaDB pods keep restarting.

Rest of deployment will not start as a result

MariaDB logs similar to

2020-04-17 02:18:08,248 - OpenStack-Helm Mariadb - INFO - The data we have from the cluster is too old to make a decision for node mariadb-server-2 2020-04-17 02:18:08,248 - OpenStack-Helm Mariadb - INFO - The data we have from the cluster is ok for node mariadb-server-1 2020-04-17 02:18:08,248 - OpenStack-Helm Mariadb - INFO - The data we have from the cluster is too old to make a decision for node mariadb-server-0

Time is off by more than 20 seconds on controller nodes

osctl get cm mariadb1-mariadb-state -oyaml

apiVersion: v1
data:
...
sample_time.mariadb-server-0: "2020-04-17T21:06:20.799403Z"
sample_time.mariadb-server-1: "2020-04-17T21:06:42.447370Z"
sample_time.mariadb-server-2: "2020-04-17T21:06:42.574760Z"
...

Cause

Time sync issues causing database cluster to not start up.

systemctl-timesyncd default settings do not sync if time is off by 5 seconds

Resolution

To fix timesync issues on control plane.

ssh into the manager node

Edit the conf file and add RootDistanceMaxSec

Note: Maximum acceptable root distance. Takes a time value (in seconds). Defaults to 5 seconds.

/etc/systemd/timesyncd.conf

[Time]

NTP=xxx.xxx.xxx.xxx
RootDistanceMaxSec=3600

Restart timesyncd and verify change and time synchronization:

systemctl restart systemd-timesyncd.service

systemctl status systemd-timesyncd.service

timedatectl show-timesync

timedatectl timesync-status
timedatectl

Login to a controller node(s):

root@oms [ /var/log ]# kubectl get node

NAME                    STATUS   ROLES                     AGE   VERSION

controller-2rx87xxnsb   Ready    openstack-control-plane   55d   v1.14.1

controller-6qjfjbnnq7   Ready    openstack-control-plane   55d   v1.14.1

controller-tmgjfmnvr5   Ready    openstack-control-plane   55d   v1.14.1

oms.vio.local           Ready    master                    55d   v1.14.1

root@oms [ /var/log ]# viossh controller-2rx87xxnsb

Last login: Wed Apr 15 13:26:29 UTC 2020 from 172.20.0.45 on pts/0

Last login: Wed Apr 15 21:25:31 2020 from 172.20.0.45

vioadmin@controller-2rx87xxnsb [ ~ ]$

Edit the conf file and add RootDistanceMaxSec

/etc/systemd/timesyncd.conf.d/cloud-init.conf

[Time]

NTP=xxx.xxx.xxx.xxx
RootDistanceMaxSec=3600

Restart timesyncd and verify time synchronization:

sudo systemctl restart systemd-timesyncd.service

sudo systemctl status systemd-timesyncd.service

timedatectl show-timesync

timedatectl timesync-status
timedatectl 

Wait for the pods to recreate and for OpenStack Deployment State to say RUNNING:

watch -n2 'viocli get deployment'

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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 6.x

Take Our Survey

Support Assistant