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

"Failed to create VUM database" VCSA 6.7 upgrade fails during Update Manager Firstboot (67910)

Last Updated: 11/2/2023Categories: TroubleshootingTotal Views: 8694Language:
English

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

vCenter Server Appliance 6.7 upgrade fails during Update Manager firstboot while creating VUM Database with error:"Failed to create VUM database"

You will see similar entries in /var/log/firstboot/updatemgr-firstboot.py_####_stdout.log

2019-04-17T22:08:04.346Z  Exception caught in checkException: Failed to create Database schema
2019-04-17 22:08:04,347  UpdateMgr received BaseInstallException '{
"detail": [
{
"localized": "Failed to create VUM database",
"translatable": "Failed to create VUM database",
"id": "install.updatemgr.error.db_create"
},
{
"localized": "Failed to setup VUM database",
"translatable": "Failed to setup VUM database",
"id": "install.updatemgr.error.db_setup"
}
],
"resolution": {
"localized": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a  support request.",
"translatable": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a  support request.",
"id": "install.updatemgr.resolution.common"
},
"problemId": "install.updatemgr.firstboot",
"componentKey": "Update Manager"
}' during action 'firstboot'.
Traceback (most recent call last):
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 106, in proxy
return func(self, *args, **kwargs)
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 577, in _createDataBaseSchema
raise LoggedException("Failed to create Database schema")
LoggedException: Failed to create Database schema

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 710, in Main
updateMgrFB.firstbootAction()
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 668, in firstbootAction
self._setupDataBase(msg)
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 106, in proxy
return func(self, *args, **kwargs)
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 530, in _setupDataBase
self._createDataBaseSchema(msg)
File "/usr/lib/vmware-updatemgr/firstboot/updatemgr-firstboot.py", line 117, in proxy
problemId="install.updatemgr.firstboot")
cis.baseCISException.BaseInstallException: {
"detail": [
{
"localized": "Failed to create VUM database",
"translatable": "Failed to create VUM database",
"id": "install.updatemgr.error.db_create"
},
{
"localized": "Failed to setup VUM database",
"translatable": "Failed to setup VUM database",
"id": "install.updatemgr.error.db_setup"
}
],
"resolution": {
"localized": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a  support request.",
"translatable": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a  support request.",
"id": "install.updatemgr.resolution.common"
},
"problemId": "install.updatemgr.firstboot",
"componentKey": "Update Manager"
}

Updatemgr-Firstboot.py:

2019-04-18 21:25:58.647 UTC 5cb8eb66.56dc 0 VCDB postgres ERROR:  role "vumuser" already exists
2019-04-18 21:25:58.647 UTC 5cb8eb66.56dc 0 VCDB postgres STATEMENT:  CREATE USER vumuser WITH PASSWORD 'yIqMtKL7=3r01$gG';
2019-04-18 21:25:59.107 UTC 5cb8eb67.5700 0 VCDB vumuser FATAL:  password authentication failed for user "vumuser"
2019-04-18 21:25:59.107 UTC 5cb8eb67.5700 0 VCDB vumuser DETAIL:  Password does not match for user "vumuser"

Cause

This issue occurs when the  role "vumuser" already exists and its trying to create the user vumuser .

Resolution

Take a backup of the VUM database.

Take a snapshot of the VCSA appliance.

Run the below commands to connect to DB and drop the users,

/opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB

Drop owned by vumuser;

Drop user vumuser;

Re-run the VCSA upgrade process again.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VMware Academic Program について (1033638)

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

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Update Manager

Related Versions:

VMware vCenter Update Manager 6.7.x

Take Our Survey

Support Assistant