As a Cloud Manager administrator, you might occasionally encounter capacity collection issues in the Cloud Manager system. You can enable the debugging for capacity collection logging on your production level Cloud Manager Application Server to help you or NetIQ Support troubleshoot these issues.
The Cloud Manager Application Server uses a custom properties file, /etc/cmplanner.logging.properties, to enable logging. Its contents, including the DEBUG setting, look like this:
# Set root logger level to DEBUG and its only appender to A1. log4j.rootLogger=WARN, CMFILE, CMOUT # Planner is set to be a ConsoleAppender. log4j.appender.CMOUT=org.apache.log4j.ConsoleAppender log4j.appender.CMOUT.layout=org.apache.log4j.PatternLayout log4j.appender.CMOUT.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n # File appender log4j.appender.CMFILE=org.apache.log4j.RollingFileAppender log4j.appender.CMFILE.layout=org.apache.log4j.PatternLayout log4j.appender.CMFILEt.layout.ConversionPattern=[%d{dd MMM yyyy HH:MM:ss}] %-5.5p | %-16.16t | %-32.32c{1} | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n log4j.appender.CMFILE.file=${karaf.base}/logs/cloudmanager_server.log log4j.appender.CMFILE.append=true log4j.appender.CMFILE.maxFileSize=10MB log4j.appender.CMFILE.maxBackupIndex=10 # Logging category modifications for novell-esb log4j.logger.org.quartz=DEBUG log4j.logger.com.netiq.rest.planner.CmPlanner=DEBUG log4j.logger.com.netiq.service.planner.capacitybot.CapacityBot=DEBUG
To enable debug logging,
Edit the properties file, changing any WARN value to a DEBUG value (see example, above).
In the Karaf console, run an update on the AppServices bundle.
The update process requires that you enter a module ID. You can find this ID using a list command and then browsing the list of modules and their accompanying IDs.