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

High NSX Manager CPU during AD Delta Sync (66828)

Last Updated: 2/13/2022Categories: TroubleshootingTotal Views: 4274Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

High NSX Manager CPU is seen frequently during Active Directory (AD) Delta Sync.  This is observed in NSX-v 6.4.2.

You will see the similar log entries in NSX Manager vsm.log:

2018-09-25 04:09:10.816 MSK INFO taskExecutor-12 LDAPSyncContext:431 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Start to process request: Delta sync
2018-09-25 04:43:27.927 MSK INFO taskExecutor-12 LDAPSyncContext:528 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Synchronize (Delta sync) with server: 10.50.24.45, for domain: Domain[id=1, name=gazprom-neft.local], done in 2057057 ms.
2018-09-25 07:09:10.816 MSK INFO taskExecutor-9 LDAPSyncContext:431 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Start to process request: Delta sync
2018-09-25 07:43:30.287 MSK INFO taskExecutor-9 LDAPSyncContext:528 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Synchronize (Delta sync) with server: 10.50.24.45, for domain: Domain[id=1, name=gazprom-neft.local], done in 2059416 ms.
2018-09-25 10:09:10.816 MSK INFO taskExecutor-17 LDAPSyncContext:431 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Start to process request: Delta sync
2018-09-25 10:43:17.910 MSK INFO taskExecutor-17 LDAPSyncContext:528 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Synchronize (Delta sync) with server: 10.50.24.45, for domain: Domain[id=1, name=gazprom-neft.local], done in 2047037 ms.
2018-09-25 13:09:10.816 MSK INFO taskExecutor-13 LDAPSyncContext:431 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Start to process request: Delta sync
2018-09-25 13:43:30.708 MSK INFO taskExecutor-13 LDAPSyncContext:528 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Synchronize (Delta sync) with server: 10.50.24.45, for domain: Domain[id=1, name=gazprom-neft.local], done in 2059822 ms.
2018-09-25 16:09:10.816 MSK INFO taskExecutor-9 LDAPSyncContext:431 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Start to process request: Delta sync
2018-09-25 16:43:14.023 MSK INFO taskExecutor-9 LDAPSyncContext:528 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Synchronize (Delta sync) with server: 10.50.24.45, for domain: Domain[id=1, name=gazprom-neft.local], done in 2043160 ms.
2018-09-25 19:09:10.816 MSK INFO taskExecutor-16 LDAPSyncContext:431 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Start to process request: Delta sync

2018-11-19 10:18:00.577 MSK  INFO taskScheduler-21 CPUUsagesMonitor:237 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Starting CPU monitoring as CPU usage was above threshold limit (80%) for consecutive 5 interval
2018-11-19 10:30:09.753 MSK  INFO taskScheduler-19 CPUUsagesMonitor:237 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Starting CPU monitoring as CPU usage was above threshold limit (80%) for consecutive 5 interval
2018-11-19 13:17:37.387 MSK  INFO taskScheduler-17 CPUUsagesMonitor:237 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Starting CPU monitoring as CPU usage was above threshold limit (80%) for consecutive 5 interval
2018-11-19 13:29:46.502 MSK  INFO taskScheduler-17 CPUUsagesMonitor:237 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Starting CPU monitoring as CPU usage was above threshold limit (80%) for consecutive 5 interval
2018-11-19 14:13:11.830 MSK  INFO taskScheduler-30 CPUUsagesMonitor:237 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Starting CPU monitoring as CPU usage was above threshold limit (80%) for consecutive 5 interval

2018-11-19 10:31:54.832 MSK ERROR taskExecutor-20 SqlExceptionHelper:131 - ERROR: duplicate key value violates unique constraint "ix_host_loginname_domain_id_key"
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "ix_host_loginname_domain_id_key"
2018-11-19 13:31:41.397 MSK ERROR taskExecutor-4 SqlExceptionHelper:131 - ERROR: duplicate key value violates unique constraint "ix_host_loginname_domain_id_key"
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "ix_host_loginname_domain_id_key"

postgres log /common/db/vshield/serverlog:
2019-01-02 10:16:42.544 GMT [5865]: [1-1] ERROR: duplicate key value violates unique constraint "ix_host_loginname_domain_id_key"
2019-01-02 10:16:42.544 GMT [5865]: [2-1] DETAIL: Key (lower(loginname::text), domain_id)=(hq-win2012-02a$, 4) already exists.
2019-01-02 10:16:42.544 GMT [5865]: [3-1] STATEMENT: update ai_host set deletedate=$1, displayname=$2, distinguishedname=$3, domain_id=$4, domain_sync_rootdn_id=$5, lastchangedtime=$6, orgunit_id=$7, primary_id=$8, security_id=$9, discoverymethod=$10, loginname=$11, description=$12, fqhostname=$13, singlemultiflag=$14, osstr=$15 where id=$16

Cause

In this customer scenario, the following changes are made in AD –
SID1: A
SID2: B
change to:
SID1: B
SID2: A

The problem here is due to the new name conflicting with the existing name in other objects in Active Directory (AD) even current NSX-v does support renaming AD objects while SID stays the same.
Note the conflict is transient - meaning there is no conflict in final system state but the conflicts result when processing one of the update.
For example, if changes are applied in stages, we will not see this issue.

SID1: A
SID2: B
change to:
SID1: X
SID2: B
sync AD, then change to:
SID1: X
SID2: A
sync AD, then change to:
SID1: B
SID2: A
sync AD

Resolution

This is a known issue affecting VMware NSX for vSphere 6.4.2 to 6.4.4.
Currently, there is no resolution.

Workaround

To work around this issue, file a support request with VMware Support and quote this Knowledge Base article ID (66828)  in the problem description.
For more information, see How to Submit a Support Request.

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)

KB
•
如何针对 VCHA 手动为 vCenter Server Appliance 6.5/6.7 添加第二个网卡 (2147155)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

Take Our Survey

Support Assistant