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

vpxd crashes when changing vSphere Distributed Switch (vDS) settings when using postgres database (55702)

Last Updated: 9/6/2018Categories: TroubleshootingTotal Views: 5245Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vCenter Server Appliance (vpxd) crashes when changing vDS settings.

The vpxd.log file shows errors similar to:

2018-05-21T17:50:43.745Z error vpxd[7FC8EEA3E700] [Originator@6876 sub=Default opID=DvPortSettingsDialog-apply-1549-ngc:70000253-b2] [Vdb::IsRecoverableErrorCode] Unable to recover from 23505:7
2018-05-21T17:50:43.745Z error vpxd[7FC8EEA3E700] [Originator@6876 sub=Default opID=DvPortSettingsDialog-apply-1549-ngc:70000253-b2] [Vdb::IsRecoverableErrorCode] Unable to recover from HY000:110
2018-05-21T17:50:43.746Z error vpxd[7FC8EEA3E700] [Originator@6876 sub=vpxCommon opID=DvPortSettingsDialog-apply-1549-ngc:70000253-b2] [Vpxd_HandleVmRootError] Received unrecoverable VmRootError. Generating minidump ...
2018-05-21T17:50:43.746Z error vpxd[7FC8EEA3E700] [Originator@6876 sub=Default opID=DvPortSettingsDialog-apply-1549-ngc:70000253-b2] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbError] (-17) "Error for Update" is returned when executing SQL statement "UPDATE VPX_DVPORT_SETTING SET BLOCKED_FLG = ? , NRP_KEY = ? , IN_SHAPING_OBJECT_FLG = ? , IN_SHAPING_AVG_BANDWIDTH = ? , IN_SHAPING_BURST_SIZE = ? , IN_SHAPING_ENABLED = ? , IN_SHAPING_PEAK_BANDWIDTH = ? , OUT_SHAPING_OBJECT_FLG = ? , OUT_SHAPING_AVG_BANDWIDTH = ? , OUT_SHAPING_BURST_SIZE = ? , OUT_SHAPING_ENABLED = ? , OUT_SHAPING_PEAK_BANDWIDTH = ? , VLAN_OBJECT_FLG = ? , VLAN_ID = ? , QOS_TAG = ? , TX_UPLINK = ? , IPFIX_OBJECT_FLG = ? , IPFIX_ENABLED = ? , SEC_POLICY_OBJECT_FLG = ? , ALLOW_PROMISCUOUS = ? , FORGED_TRANSMITS = ? , MAC_CHANGES = ? , TEAMING_OBJECT_FLG = ? , TEAMING_POLICY = ? , TEAMING_REVERSE = ? , TEAMING_NOTIFY = ? , TEAMING_ROLLING = ? , CRITERIA_OBJECT_FLG = ? , TEAMING_FAIL_CHK_BEACON = ? , TEAMING_FAIL_CHK_DUPLEX = ? , TEAMING_FAIL_CHK_PERCENT = ? , TEAMING_FAIL_CHK_SPEED = ? , TEAMING_FAIL_DUPLEX = ? , TEAMING_FAIL_PERCENT = ? , TEAMING_FAIL_SPEED = ? , UPLINK_ORDER_OBJECT_FLG = ? , VENDOR_BLOB_OBJECT_FLG = ? , NPT_ALLOWED_FLG = ? , LACP_ENABLE = ? , LACP_MODE = ? , PVLAN_ID = ? , OVERLAY_OBJECT_FLG = ? , TRAFFIC_FILTER_OBJ_FLG = ? WHERE DVS_ID = ? AND DVPORTGROUP_ID = ? AND DVPORT_KEY = ?"
2018-05-21T17:50:43.751Z panic vpxd[7FC8EEA3E700] [Originator@6876 sub=Default opID=DvPortSettingsDialog-apply-1549-ngc:70000253-b2]
-->
--> Panic: Unrecoverable VmRootError. Panic!
--> Backtrace:
--> [backtrace begin] product: VMware VirtualCenter, version: 6.5.0, build: build-8307201, tag: vpxd, cpu: x86_64, os: linux, buildType: release
--> backtrace[00] libvmacore.so[0x002B673C]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace[01] libvmacore.so[0x001B1FE8]: Vmacore::System::SystemFactoryImpl::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] libvmacore.so[0x002B46EB]
--> backtrace[03] libvmacore.so[0x002B47C6]: Vmacore::PanicExit(char const*)
--> backtrace[04] vpxd[0x00726D5A]
--> backtrace[05] vpxd[0x0073C70B]
--> backtrace[06] vpxd[0x0073EA41]
--> backtrace[07] vpxd[0x00743D82]
--> backtrace[08] libvmacore.so[0x0023B4A3]
--> backtrace[09] libvmacore.so[0x0023B78A]
--> backtrace[10] libvmacore.so[0x002BBFDB]
--> backtrace[11] libpthread.so.0[0x00007444]
--> backtrace[12] libc.so.6[0x000E8C2D]
--> [backtrace end]

The vpxd.log also shows errors as similar to:

2018-05-23 18:51:01.850 UTC 5b05b6ad.294b 0   LOG:  Updated instance status successfully.
2018-05-23 18:51:36.472 UTC 5b05b6ed.32b5 669655 VCDB vc ERROR:  duplicate key value violates unique constraint "pk_vpx_dvport_setting"
2018-05-23 18:51:36.472 UTC 5b05b6ed.32b5 669655 VCDB vc DETAIL:  Key (dvs_id, surr_key)=(21443, 14) already exists.
2018-05-23 18:51:36.472 UTC 5b05b6ed.32b5 669655 VCDB vc STATEMENT:  INSERT INTO VPX_DVPORT_SETTING (DVS_ID, DVPORTGROUP_ID, DVPORT_KEY, BLOCKED_FLG, NRP_KEY, IN_SHAPING_OBJECT_FLG, IN_SHAPING_AVG_BANDWIDTH, IN_SHAPING_BURST_SIZE, IN_SHAPING_ENABLED, IN_SHAPING_PEAK_BANDWIDTH, OUT_SHAPING_OBJECT_FLG, OUT_SHAPING_AVG_BANDWIDTH, OUT_SHAPING_BURST_SIZE, OUT_SHAPING_ENABLED, OUT_SHAPING_PEAK_BANDWIDTH, VLAN_OBJECT_FLG, VLAN_ID, QOS_TAG, TX_UPLINK, IPFIX_OBJECT_FLG, IPFIX_ENABLED, SEC_POLICY_OBJECT_FLG, ALLOW_PROMISCUOUS, FORGED_TRANSMITS, MAC_CHANGES, TEAMING_OBJECT_FLG, TEAMING_POLICY, TEAMING_REVERSE, TEAMING_NOTIFY, TEAMING_ROLLING, CRITERIA_OBJECT_FLG, TEAMING_FAIL_CHK_BEACON, TEAMING_FAIL_CHK_DUPLEX, TEAMING_FAIL_CHK_PERCENT, TEAMING_FAIL_CHK_SPEED, TEAMING_FAIL_DUPLEX, TEAMING_FAIL_PERCENT, TEAMING_FAIL_SPEED, UPLINK_ORDER_OBJECT_FLG, VENDOR_BLOB_OBJECT_FLG, NPT_ALLOWED_FLG, LACP_ENABLE, LACP_MODE, PVLAN_ID, OVERLAY_OBJECT_FLG, TRAFFIC_FILTER_OBJ_FLG) VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, $19, $20, $21, $22, $23, $24, $25, $26, $27, $28, $29, $30, $31, $32, $33, $34, $35, $36, $37, $38, $39, $40, $41, $42, $43, $44, $45, $46)
2018-05-23 18:52:01.857 UTC 5b05b6ad.294b 0   LOG:  Updating instance status...

Cause

Database sequence is out of sync during an attempt to either insert/update the primary key column on the VPX_DVPORT_SETTING table, causing the vCenter Server Appliance to crash.

Impact / Risks

Modifying the database can be dangerous.
Ensure you backup the database and take snapshots of the vCenter Server.

Resolution

Update the last_value in the sequence to reflect the latest sequence +1.

Log into the vCenter Server Appliance as root via SSH or Console.

Run the following command to enter the shell.

shell

Connect to the vPostgres database for SQL execution by running this command:

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

To get the current sequence last_value, run this command:

select * from vpx_dvport_setting_surr_key_seq;

Example: This will give 11 as the last  value as in example below.

sequence_name                            | last_value | start_value | increment_by |      max_value      | min_value | cache_value | log_cnt | is_cycled | is_called
---------------------------------+------------+-------------+--------------+---------------------+-----------+-------------+---------+-----------+-----------
vpx_dvport_setting_surr_key_seq |         11 |           1 |            1 | 9223372036854775807 |         1 |           1 |       0 | f         | t
(1 row)

To fix and reset the sequence value, run the statement below:

select setval('vpx_dvport_setting_surr_key_seq', (select coalesce(max(surr_key)+1) from vpx_dvport_setting), false);

To re check the sequence value, run the statement below:

select * from vpx_dvport_setting_surr_key_seq;

To re confirm the value of surr_key (seq value)  run the statement:

select coalesce(max(surr_key)+1) from vpx_dvport_setting;

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant