Accessing the vSphere Lifecycle Manager Database using vumuser fails with FATAL: Peer authentication failed for user "vumuser"
search cancel

Accessing the vSphere Lifecycle Manager Database using vumuser fails with FATAL: Peer authentication failed for user "vumuser"

book

Article ID: 344944

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • Accessing the Update Manager/vSphere Lifecycle Manager (vLCM) Database fails with FATAL:  Peer authentication failed for user "vumuser"
  • /var/log/vmware/vpostgres/postgresql-xx.log
2023-05-22 20:44:03.228 UTC 646bd413.5511 0 [unknown] [unknown] [local] 21777 1 LOG:  connection received: host=[local]
2023-05-22 20:44:03.229 UTC 646bd413.5511 0 VCDB vumuser [local] 21777 2 LOG:  no match in usermap "updatemgr" for user "vumuser" authenticated as "root"
2023-05-22 20:44:03.229 UTC 646bd413.5511 0 VCDB vumuser [local] 21777 3 FATAL:  Peer authentication failed for user "vumuser"
2023-05-22 20:44:03.229 UTC 646bd413.5511 0 VCDB vumuser [local] 21777 4 DETAIL:  Connection matched pg_hba.conf line 54: "local  VCDB  vumuser  peer map=updatemgr"

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vCenter Server 8.0.x

Resolution

In order to access vLCM database, refer to the below steps
  • Log in to the vCenter Server via ssh
  • Switch the user to updatemgr from root
su updatemgr -s /bin/bash

Note: The session would change to updatemgr@<vcenter name> from root@<vcenter name>
  • Log in to the database instance
psql -U vumuser -d VCDB
  • exit the database prompt by typing \q and hit enter
  • To switch back to root, type exit and hit enter
Screenshot for reference:

image.png