Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Smarts NCM :Excessive logging of WARN messages for AuthorizationSucceededEvent event thrown by integration adapters (521993)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 4264Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Under some NCM instance production specific usage profiles, use of the integration modules may cause the server.log or powerup.log files to become filled with very rapidly occurring, high volume writes of the following or similar WARN messages tied to the AuthorizationSucceededEvent (the integration module named may vary by NCM instance):

2018-05-22 10:49:48,341 WARN [com.voyence.configmgr.integration.modules.flatfile.jmx.FlatFileIntegrationModule] (ActiveMQ Session Task-2779) Ignoring received event AuthorizationSucceededEvent. This module not setup to handle this event.
2018-05-22 10:49:48,341 WARN [com.voyence.configmgr.integration.modules.mail.jmx.MailIntegrationModule] (ActiveMQ Session Task-2731) Ignoring received event AuthorizationSucceededEvent. This module not setup to handle this event.
2018-05-22 10:49:48,342 WARN [com.voyence.configmgr.integration.modules.snmp.jmx.SNMPIntegrationModule] (ActiveMQ Session Task-2727) Ignoring received event AuthorizationSucceededEvent. This module not setup to handle this event.

This has been tied to large log file size, and rapid rolling of the affect log files at a pace that makes them largely useless for other troubleshooting. In some cases, we have seen the entire rolled log set cycle completely out of scope in under thirty (30) minutes.

Cause

Many of the integration modules were not written with message handlers to gracefully receive and discard the AuthorizationSucceededEvent message because it is considered to be normal function. Under most usage profiles, these messages can be safely ignored, as they do not impact NCM functionality in any way except in the narrow use case where the sheer volume of these messages in the logs becomes problematic.

Resolution

1.  During an appropriate maintenance window, log into a Linux shell on the NCM Application Server (AS) host as 'root'.
2.  Set NCM related shell session variables by running the following command:

source /etc/voyence.conf

3.  Make a backup copy of the current logging configuration responsible for the excessive error logging for NCM integration modules by running the following command:

cp -p $VOYENCE_HOME/ncmcore/webapps/ncm-webapp/WEB-INF/classes/log4j.xml $VOYENCE_HOME/ncmcore/webapps/ncm-webapp/WEB-INF/classes/_backup_log4j.xml

4.  Open the original file cited in Step 3. above for editing in a text editor of your choice (ex.: POSIX Linux 'vi' text editor):
5.  Locate the comment section immediately prior to the '<root>' tag near the end of the file (on our about line 297).
6.  Insert the following new configuration stanza prior to the comment section cited in Step 4 above:

<category name="com.voyence.configmgr.integration">

<priority value="OFF" />

<appender-ref ref="FILE"/>

</category>

7.  Save and exit the file
8.  Restart NCM services on the AS host by running the following command:

service vcmaster restart

This should suppress the excessive integration module logging of these normal function messages so they no longer adversely impact NCM logging.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant