Data Collector logs filling with ERROR messages
Article ID: 233614
Updated On:
Products
Issue/Introduction
These messages are filling up the DX NetOps Performance Management (PM) Data Collector (DC) karaf.log file.
Is there a way to prevent them from filling the logs?
2022-02-01T13:13:23,896 | ERROR | 300000-thread-1 | StandardSnmpScheduledPollRequest | StandardSnmpScheduledPollRequest 58 | 54 - com.ca.im.data-collection-manager.snmp - 21.2.6.RELEASE-287 | | IP <IP_Address> Poll Group 4016 doesn't have the correct oids [null] attribute group position=1
2022-02-01T13:13:23,896 | ERROR | 300000-thread-1 | CiscoIPSLAScheduledPollRequest | a.CiscoIPSLAScheduledPollRequest 347 | 54 - com.ca.im.data-collection-manager.snmp - 21.2.6.RELEASE-287 | | Skipping attribute group position: 1, Caught exception 'For input string: "null"' constructing baseOIDWithTestIndex for IP=<IP_Address>, deviceItemID=886556, ipslaComponentID=[5549142], discoveryOID=1.3.6.1.4.1.9.9.42.1.3.2.1.7, testID=null, dynamicDiscoveryState=null
Environment
DX NetOps Performance Management releases r21.2.7 and earlier
Cause
Incorrect message classification as ERROR results in their appearance in the logs.
Resolution
In the r21.2.8 release of DX NetOps Performance Management the messages are changed to a level that prevents their writing to the karaf.log.
To alleviate the issue we can edit the org.ops4j.pax.logging.cfg file to change the logging behavior.
Workaround for r21.2.2+ releases:
In r21.2.2+ releases add the following lines to the (default path shown) /opt/IMDataCollector/apache-karaf-<version>/etc/org.ops4j.pax.logging.cfg file.
Open the file for editing. Add the lines to the end of the file and save the changes. No service restarts are needed as the changes to the logging are read in on the fly.
#
# Log only FATAL messages for NonStandardSnmpScheduledPollRequest
# to new log file outside of karaf.log
# can remove post r21.2.8
#
log4j2.logger.NonStandardSnmpScheduledPollRequest.name = com.ca.im.dm.snmp.collector.pollrequest.NonStandardSnmpScheduledPollRequest
log4j2.logger.NonStandardSnmpScheduledPollRequest.level = FATAL
log4j2.logger.NonStandardSnmpScheduledPollRequest.additivity = false
log4j2.logger.NonStandardSnmpScheduledPollRequest.appenderRef.sift.ref = sift
#
# Log only FATAL messages for CiscoIPSLAScheduledPollRequest
# to new log file outside of karaf.log
# can remove post r21.2.8
#
log4j2.logger.CiscoIPSLAScheduledPollRequest.name = com.ca.im.dm.snmp.collector.ipsla.CiscoIPSLAScheduledPollRequest
log4j2.logger.CiscoIPSLAScheduledPollRequest.level = FATAL
log4j2.logger.CiscoIPSLAScheduledPollRequest.additivity = false
log4j2.logger.CiscoIPSLAScheduledPollRequest.appenderRef.sift.ref = sift
Workaround for r21.2.1 and earlier releases:
In r21.2.1 and earlier releases add the following lines to the (default path shown) /opt/IMDataCollector/apache-karaf-<version>/etc/org.ops4j.pax.logging.cfg file.
Open the file for editing. Add the lines to the end of the file and save the changes. No service restarts are needed as the changes to the logging are read in on the fly.
#
# Log only FATAL messages for NonStandardSnmpScheduledPollRequest
# to new log file outside of karaf.log
# can remove post r21.2.8
#
log4j.logger.com.ca.im.dm.snmp.collector.pollrequest.NonStandardSnmpScheduledPollRequest = FATAL, sift
log4j.additivity.com.ca.im.dm.snmp.collector.pollrequest.NonStandardSnmpScheduledPollRequest = false
#
# Log only FATAL messages for CiscoIPSLAScheduledPollRequest
# to new log file outside of karaf.log
# can remove post r21.2.8
#
log4j.logger.com.ca.im.dm.snmp.collector.ipsla.CiscoIPSLAScheduledPollRequest = FATAL, sift
log4j.additivity.com.ca.im.dm.snmp.collector.ipsla.CiscoIPSLAScheduledPollRequest = false
Additional Information
These lines should not be needed in r21.2.8 and newer releases.
Feedback
