Related Event Data missing under executed task in vCenter
Article ID: 338852
Updated On:
Products
Issue/Introduction
To fix vCenter Events ID overflow which is causing event data to be missing.
Customer will notice related event data missing
You may see logs like below:
journalctl | grep " Event " | tail
Jan 24 18:02:11 vc01.example.com vpxd[6050]: Event [-2105376566] [1-1] [2022-01-24T16:01:32.09891Z] [vim.event.UserLogoutSessionEvent] [info] [root] [VC-Datacenter] [-2105376566] [User root@127.0.0.1 logged out (login time: Monday, 24 January, 2022 04:01:32 PM, number of API invocations: 7, user agent: pyvmomi Python/3.5.9 (VMkernel; 7.0.1; x86_64))]
Jan 24 18:02:11 vc01.example.com vpxd[6050]: Event [-2105376565] [1-1] [2022-01-24T16:02:03.011487Z] [vim.event.UserLoginSessionEvent] [info] [root] [VC-Datacenter] [-2105376565] [User root@127.0.0.1 logged in as pyvmomi Python/3.5.9 (VMkernel; 7.0.1; x86_64)]
Environment
VMware vCenter Server 6.7.x
VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.x
Cause
Issue with event overflows in task and events in vCenter.
Resolution
To work around the issue see below:
Note: Please take a snapshot of the vCenter before proceeding ahead.
1. Take an SSH session to vCenter node
2. stop vpxd service
# service-control --stop vmware-vpxd
3. Run the below command:
# /opt/vmware/vpostgres/current/bin/psql -U postgres VCDB -c "ALTER SEQUENCE VPX_EVENT_SEQ RESTART WITH 1"
4. start vpxd service
# service-control --start vmware-vpxd
Additional Information
Feedback
