Failed to register VRMS - Failed to initialize the DBManager
search cancel

Failed to register VRMS - Failed to initialize the DBManager

book

Article ID: 312699

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

1. vSphere Replication appliance upgrade is successful but reconfiguration fails with the error - 
 
Error:

Operation Failed A general system error occurred: Failed to register VRMS.
Operation ID: 3840393f-ac36-4aca-bb65-3d2135ca9ee6

2. And, when you revert the Replication appliance snapshot to the previous version before upgrade, all the VM replications show errors & you have to reconfigure them to get them to sync. 

This problem was encountered when VR was being upgraded from 8.5 to 8.7 and its intermediate versions
 
These log snippets were taken after the appliance was upgraded to 8.7. 

/opt/vmware/var/log/vami/updatecli.log: 
 
27/03/2024 12:18:00 [INFO] Update status: Done VMware tools reconfiguration
27/03/2024 12:18:00 [INFO] Update status: Running finalizing installation
27/03/2024 12:18:00 [INFO] Running /opt/vmware/var/lib/vami/update/data/job/5/manifest_update
27/03/2024 12:18:00 [INFO] Update status: Done finalizing installation
27/03/2024 12:18:00 [INFO] Update status: Update completed successfully
27/03/2024 12:18:00 [INFO] Install Finished
 
/var/log/vmware/dr/drconfig.log:

2024-03-27T12:18:16.575Z error drconfig[00511] [SRM@6876 sub=SchemaUtils] Failed to initialize the DBManager.
--> 14DBManagerError Credentials for 'db:srmdb' do not exist in CredentialsStore.  Use 'installcreds' to install the corresponding credentials.
-->    reason = "Failed to initialize the DBManager."
 
Timeout while waiting for the vSphere Replication Management Server 'vRepl.vmware.com' to become connected.
2024-03-27T12:49:57.882Z error drconfig[00513] [SRM@6876 sub=SchemaUtils] Failed to initialize the DBManager.
--> 14DBManagerError Credentials for 'db:srmdb' do not exist in CredentialsStore.  Use 'installcreds' to install the corresponding credentials.
2024-03-27T12:49:57.882Z error drconfig[00513] [SRM@6876 sub=DrConfigDatabaseManager] _DoActivate: DB error: (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    reason = "Failed to initialize the DBManager."
-->    msg = ""
--> }
--> [context]zKq7AVECAAQAAAFuSQENZHJjb25maWcAAO2hHGxpYnZtYWNvcmUuc28AAXZgCmRyLWNvbmZpZ3VyYXRvcgAB7jYEAX5UEQKVxgZsaWJkci12bW9taS5zbwABdPsRApXGBgG0UggBqacJA90fDGxpYmRyLXZtYWNvcmUuc28AAWYTBwSHKwJsaWJjLnNvLjYAAYVPBw==[/context]
--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.7.0, build: build-21589505, tag: drconfig, cpu: x86_64, os: linux, buildType: release
--> backtrace[03] libvmacore.so[0x001CA1ED]
--> backtrace[04] dr-configurator[0x000A6076]
--> backtrace[05] dr-configurator[0x000436EE]
--> backtrace[06] dr-configurator[0x0011547E]
--> backtrace[07] libdr-vmomi.so[0x0006C695]
--> backtrace[08] dr-configurator[0x0011FB74]
--> backtrace[09] libdr-vmomi.so[0x0006C695]
--> backtrace[10] dr-configurator[0x000852B4]
--> backtrace[11] dr-configurator[0x0009A7A9]
--> backtrace[12] libdr-vmacore.so[0x000C1FDD]
--> backtrace[13] dr-configurator[0x00071366]
--> backtrace[14] libc.so.6[0x00022B87]
--> backtrace[15] dr-configurator[0x00074F85]
--> [backtrace end]

You can also check these logs to find out more about this problem - 

/var/log/vmware/vrmsdb/postgresql.log
/var/lib/vrmsdb/serverlog

Environment

VMware vSphere Replication 8.x

Cause


1. This problem is observed if the upgrade procedure of the embedded DB schema fails because the vPostgreSQL service was not fully started.

2. DBManager error: Product version mismatch, when the current and runtime schema version don't match.

Resolution


NOTE: A normal snapshot must be taken before performing these steps. 

Run these commands before upgrading the appliance.  As per my most recent troubleshooting scenario, this has also worked post upgrade. 

1. Check the owner of postgresql.log

chown vrmsdb:vrmsdb /var/log/vmware/vrmsdb/postgresql.log

2. Restart hms-vpostgres: systemctl restart hms-vpostgres.service

To verify, please make sure hms-vpostgres is running.

admin@vRepl [ ~ ]$ systemctl status hms-vpostgres.service
* hms-vpostgres.service - VMware Postgres database server
   Loaded: loaded (/lib/systemd/system/hms-vpostgres.service; enabled; ven>
   Active: active (running) since Mon 2023-12-11 05:35:29 UTC; 4 days ago
 Main PID: 1168 (postgres)
    Tasks: 13 (limit: 4915)
   Memory: 92.0M
   CGroup: /system.slice/hms-vpostgres.service
           |- 1168 /opt/vmware/vpostgres/11/bin/postgres -D /var/lib/vrmsd>
           |- 1204 postgres: logger
     
3. Run the command:  echo "hms-8.5.0.11296-19237281.noarch" > /tmp/hmsrpminfo

You can get this information from this location below. This information must be collected after the upgrade is complete. The hms version will change depending on the version you are upgrading to. 

Example:
root@vsphere-replication-hq [ /opt/vmware/var/log/vami ]# less updatecli.log | grep -i noarch
Removing: hms-8.6.0.14070-20545422.noarch

 
root@vRepl [ ]# /opt/vmware/hms/bin/hms-configtool -cmd upgrade -configfile /opt/vmware/hms/conf/hms-configuration.xml
2024-06-08 15:36:36.394 INFO  com.vmware.hms.configtool.App [main] (..hms.configtool.App) [] | HMS Configuration Tool 8.8
2024-06-08 15:36:36.422 INFO  com.vmware.hms.configtool.App [main] (..hms.configtool.App) [] | FIPS mode: false
2024-06-08 15:36:36.431 INFO  com.vmware.hms.configtool.App [main] (..hms.configtool.App) [] | COMMAND: upgrade, CONFIG FILE: /opt/vmware/hms/conf/hms-configuration.xml
2024-06-08 15:36:36.443 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | Previous HMS version: 8.6.0.14070
2024-06-08 15:36:36.444 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | New HMS version: 8.8.0.17026 build number: 23166649
2024-06-08 15:36:36.449 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | Upgrading from 8.6.0.14070 to 8.8.0.17026.
2024-06-08 15:36:36.449 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | No need to merge hms-configuration.xml with the old file.
2024-06-08 15:36:36.555 WARN  com.vmware.hms.configtool.App [main] (..hms.configtool.DatabaseProcessor) [] | Error while executing SQL statement: ERROR: relation "configentryentity" does not exist Position: 25
2024-06-08 15:36:36.586 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | Previous DB version: 8.8.0.0
2024-06-08 15:36:36.586 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | Database schema upgrade started.
2024-06-08 15:36:36.587 DEBUG com.vmware.hms.configtool.App [main] (..hms.configtool.UpgradeProcessor) [] | Database schema upgrade completed.

The DB schema upgrade starts. Wait for the upgrade procedure to complete.

4. Go to VRMS VAMI, reconfigure and check if you are able to register now. 

 

Powered by Wolken Software