Vault Upgrade failing with Database Error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Vault Upgrade failing with Database Error

L3 Networker

Hi All,

 

Am upgrading Vault from 12.6 to 14.2 and facing issues with Database.

When I run setup.exe file am getting below error,

 

=====================================

ITADB495I FIPS Mode is disabled

ITADB399I Using encryption algorithms: Advanced Encryption Standard (AES), 256 bit, RSA (2048 bit), SHA2-512 (Protocol Integrity), SHA2-512 (Files Integrity).

ITADM114I Successfully connected to Database, Database id 0.

ITALD013I LDAP configuration refreshed successfully.

ITALD017I Connection to the LDAP server completed successfully.

ITAQS031I Object cache is loaded.

CAVLT103I Upgrading Vault database to version V1205.

CAVLT197I Performing step 1 of 4...

CAVLT197I Performing step 2 of 4...

CAVLT197I Performing step 3 of 4...

CAVLT197I Performing step 4 of 4...

CAVLT103I Upgrading Vault database to version V1206.

CAVLT197I Performing step 1 of 6...

CAVLT197I Performing step 2 of 6...

CAVLT197I Performing step 3 of 6...

CAVLT197I Performing step 4 of 6...

CAVLT197I Performing step 5 of 6...

CAVLT197I Performing step 6 of 6...

CAVLT197I Performing step 7 of 6...

CAVLT197I Performing step 8 of 6...

CAVLT223I Performing post DB upgrade steps...

CAVLT197I Performing step 1 of 1...

CAVLT105I Vault database upgrade ended successfully.

ITADB399I Using encryption algorithms: Advanced Encryption Standard (AES), 256 bit, RSA (2048 bit), SHA2-512 (Protocol Integrity), SHA2-512 (Files Integrity).

ITADB431S Error connecting to database (Code: -1, Reason: Can't connect to MySQL server on 'localhost:3306' (10061)).

ITADB369I utility terminated.

==================================

 

 

Anyone Faced this issue ? Can you please help me on this,

 

-Subash

8 REPLIES 8

L3 Networker

Hello Subash,

 

Your best bet is to open a case with CyberArk Technical Support. Is this being done on your primary vault? Have you run the same upgrade on a DR vault?

 

Thank you,

Tim Sawyer

 

L4 Transporter

Hello @Subash Jesuraj​ 

 

Please check if vault server is unhardened properly.

 

There is a community thread which might help you!

 

ITADB431S Error connecting to database Access denied for 'VaultUser'@'localhost'

 

L4 Transporter

Hello @Subash Jesuraj​ 

 

Please check if vault server is unhardened properly.

 

There is a community thread which might help you!

 

ITADB431S Error connecting to database Access denied for 'VaultUser'@'localhost'

 

L4 Transporter

@Subash Jesuraj​  My best bet

check all vault.ini on vault server - if custom port used then upgrade may cause update it to default

There are several vault.ini on vault servers so look for all and update accordingly

L4 Transporter

@Subash Jesuraj​  My best bet

check all vault.ini on vault server - if custom port used then upgrade may cause update it to default

There are several vault.ini on vault servers so look for all and update accordingly

L3 Networker

I tried to replicate this, upgrading a 12.6.10 environment to 14.2 and didn't encounter any errors.

 

The vault(s) do not need to be unhardened to perform the upgrade

Hi @Tim Sawyer​ 

 

The issue has been fixed by myself. Actually ours in Cluster mode. So I did upgrade in one node first, and the second node was failing with Database upgrade. So I copied the .pass files from first node to next node and it worked.

But thank you so much for your replication 🙂

L0 Member

Sounds like the Vault DB upgrade went through, but MySQL didn’t come back up afterward. The key part is that “Can’t connect to MySQL server on localhost:3306 (10061)” — that’s usually just MySQL not running or refusing connections.

First thing, check if the MySQL service is actually running after the upgrade. Sometimes it stops because the data directory or port got messed up. You can also test manually with

mysql -u root -p -h localhost -P 3306

 

to see if it responds.

If it won’t start, look at the MySQL error log — it’ll tell you if the data folder is corrupted or if there’s a port/bind issue. If there’s corruption (InnoDB errors, missing ibdata files, etc.), you can repair it with something like Stellar Repair for MySQL before trying the upgrade again.

Once the DB starts and accepts connections normally, rerun the Vault setup — it should complete fine after that.

  • 453 Views
  • 8 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!