Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How do I collect the Tivoli Provisioning Manager server and target computer logs at debug level?

0
Posted

How do I collect the Tivoli Provisioning Manager server and target computer logs at debug level?

0

Provisioning server • Edit the $TIO_HOME/config/log4j.prop file. • Change the log level of the Tivoli Provisioning Manager console and error logs: • log4j.appender.errorfile.threshold=DEBUG • log4j.appender.consolefile.threshold=DEBUG • Change the log level of the deployment engine: • log4j.category.com.ibm.tivoli.orchestrator.de=DEBUG • log4j.category.com.thinkdynamics.kanaha.de=DEBUG • To turn debug logging on for the Tivoli Provisioning Manager packages only, uncomment the following categories: • log4j.category.com.ibm.tivoli=DEBUG • log4j.category.com.thinkdynamics=DEBUG • Note: Restarting the Tivoli Provisioning Manager software is not required. Log configurations will be reloaded every 60 seconds. Target computers • Stop the Tivoli Common Agent service on the target computer. • Edit the ep\runtime\base\rcp\plugin_customization.ini file. • Change the following lines to turn on Tivoli Common Agent logging to the highest level: • com.ibm.rcp.core.logger.boot.RCPFileHandler.level=ALL

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123