Data Collector not connected

book

Article ID: 220915

calendar_today

Updated On:

Products

DX NetOps CA Performance Management - Usage and Administration

Issue/Introduction

We saw a ‘No space on device’ message in the systemctl service logs

 

I did a search for the top most used directories by volume.

The following came up:

/app/IMDataCollector/apache-karaf-2.4.3/MediationCenter/Queue.Pol/queue-CACiscoCallManager

 

This directory was full of the following types of directories

ENGINE_CACiscoCallManager_207.57-1624119300679-processed  ENGINE_CACiscoCallManager_207.57-1624806900173-processed  ENGINE_CACiscoCallManager_207.57-1625450400394-processed  ENGINE_CACiscoCallManager_207.57-1626093900567-processed

Cause

It sounds like EMS debug was enabled while troubleshooting a different issue on this host, which doesn't remove the CAMM provided poll/inv files on processing complete.

Environment

Release : 20.2

Component : IM Polling

Resolution

make sure EMS is back to INFO in

/opt/IMDataCollector/apache-karaf-2.4.3/etc/org.ops4j.pax.logging.cfg

file, then you can clean up the processed directories.

…………………..

#

# EMS Integration logging

#

log4j.logger.com.ca.im.dm.mediation=INFO, ems

log4j.logger.com.ca.im.dm.ems=INFO, ems

log4j.logger.com.ca.im.data-mgmt.common.ems=INFO, ems

log4j.logger.com.ca.im.data-collection-manager=INFO, ems

log4j.logger.com.torokina=INFO, ems

….