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

NSX startup or lookup service registration fails in NSX-v (59251)

Last Updated: 11/2/2018Categories: TroubleshootingTotal Views: 5260Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX lookup service registration fails.

You see the error in the User Interface (UI) similar to:

500 Internal Server Error.

NSX start up fails.

In the vsm.log file, you see entries similar to:

2018-09-13 00:10:08.282 GMT ERROR localhost-startStop-1 ContextLoader:350 - Context initialization failed
org.springframework.context.ApplicationContextException: Failed to start bean 'vsmSSOInitializer'; nested exception is java.lang.IllegalArgumentException: Non-positive period.
Caused by: java.lang.IllegalArgumentException: Non-positive period.

2018-09-18 08:37:12.822 GMT ERROR http-nio-127.0.0.1-7441-exec-1 BaseRestController:452 - REST API failed : 'Non-positive period.'
java.lang.IllegalArgumentException: Non-positive period.

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

Cause

This issue occurs when the value of "Maximum holder-of-key token lifetime" vCenter SSO Token policy is improperly configured. (For example, less than 5000 seconds). NSX refers to this value to define token renewal interval (For example, 0.20 * "Maximum holder-of-key token lifetime"/1000) and when it derives to 0, error "Non-positive period" is seen in the logs.

Resolution

To resolve this issue:

Configure "Maximum holder-of-key token lifetime" value under vCenter Administration SSO “Token policy” to minimum of 5000 seconds).Please note the default value for this filed is 2592000 seconds.

If NSX Manager service fails to come up, restart the NSX Management Service either from NSX Manager Appliance Management User Interface (UI) or through the console with the root access by running this command:

/etc/rc.d/init.d/bluelane-manager restart

If the issue is seen with the lookup service registration from the User Interface, re-configure the lookup service. For more information on the values, see the Edit the vCenter Single Sign-On Token Policy
section of the vSphere Security Guide.

Notes:

This issue is observed when upgrading from VMware NSX for vSphere 6.2.9 to 6.3.6. However, the same issue could also be seen in other NSX releases if the Maximum holder-of-key token lifetime value in Token Policy is misconfigured.

It is not recommended to modify the Maximum holder-of-key token lifetime value as a general practice.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VIBをインストールするとき"保留中のトランザクションには空き容量が xxx MB 必要です"のエラーが発生する (2144200)

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

Results 1-2 of 2

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:

Take Our Survey

Support Assistant