Managing logs

If you experience any troubles with BMC Release Package and Deployment (RPD), you can view the appropriate logs and define the cause of the problem.

• To view RPD server logs, go to RLMhome/apache/logs.
• To view RPD engine logs, go to RLMhome/releases/productVersion/RPD/app/tmp/logs/brpd_file.log.

See this video (4:45) about debugging using various logging types.

 https://youtu.be/AcP2kr7FOMo

To define the server logging level

You can specify the server logging level in RPD using the Apache logging configuration.

1. Go to RLMhome/apache/conf and open the httpd.conf file in a text editor.

2. Edit the following lines as appropriate:
   Windows

   • For error logs:
     ErrorLog "|bin/rotatelogs.exe logs/errorlog-%Y-%m-%d.txt 86400"
   • For other logs:
     CustomLog "|bin/rotatelogs.exe logs/accesslog-%Y-%m-%d.txt 86400" common

   Linux

   • For error logs:
     ErrorLog "|<RLMUIhome>/bin/rotatelogs logs/errorlog-%Y-%m-%d.txt 86400"
   • For other logs:
     CustomLog "|<RLMUIhome>bin/rotatelogs logs/accesslog-%Y-%m-%d.txt 86400" common

   For more information, see Apache rotatelogs.

   Best practice

   Do not use spaces in the errorlog-%Y-%m-%d.txt and accesslog-%Y-%m-%d.txt log file names because rotatelogs may not work.

To define the engine logging level

You can specify the level of log details for engines in RPD. For more information, see the log_level system setting.

Related topics

Managing-system-settings