Page tree
Skip to end of metadata
Go to start of metadata

If you experience any troubles with BMC Release Process Management (RPM) or the BMC Release Lifecycle Management Requester UI (now called Release Process Management - Requester UI, 5.0.03.001 onward), you can view the appropriate logs and define the cause of the problem.

The following video (4:00) demonstrates how to enable debug for RPM.

 https://www.youtube.com/watch?v=xo3qKE_i9RI

Viewing logs in RPM

  • To view RPM server logs, go to RLMhome/server/jboss/standalone/log/server.log.
  • To view RPM automation logs, go to RLMhome/automation_results.


NEW IN 5.0.03The following system info about JVM memory details is available in the RPM server logs:

  • Available processors
  • Heap Memory (total, used, free)
  • Total JVM (B)
  • Used JVM (B)
  • Free JVM (B)
  • Threads (http & Net I/O)
  • Thread info
  • Number of DB connections
  • Queue Info

VERSION 5.0.03.004 OR LATER The following figure shows a sample log file with the system information displayed in the logs.

13:55:14,444 INFO  [SystemInfo] (EE-ManagedScheduledExecutorService-default-Thread-6)
Available processors: 8, Total JVM (B): 477626368, Free JVM (B): 53917552, Used
JVM (B): 423708816, Thread info: {:total=>136, :http=>0,
:io_worker=>0}, DB pool info: {:size=>20, :connections=>7, :busy=>1,
:idle=>6, :checkout_timeout=>10} 

VERSION 5.0.03.003 OR EARLIER The following figure shows a sample log file with the system information displayed in the logs.

05:40:00,005 INFO [System Info]
(jboss.deployment.unit."RPM-knob.yml".job_scheduler_Worker-2)
Available processors: 4, Total JVM (B): 4242014208, Free JVM (B): 1678910912,
Used JVM (B): 2563103296, Thread info: {:total=>109, :http=>7,
:io_worker=>8}, Queue Info: 


{"/queues/audit"=>0,
"/queues/torquebox/RPM/tasks/torquebox_backgroundable"=>0,
"/queues/backgroundable/automation"=>0, "/queues/activity_log"=>0,
"brpm_event_queue"=>0}

To configure the server logging in RPM

To define the advanced logging parameters for servers in RPM, modify the JBOSS logging configuration:

  1. Go to RLMhome/server/jboss/standalone/configuration and open one of the following files:
    • For non-high-availability deployment, open standalone-full.xml VERSION 5.0.03.004 OR LATER or standalone.xml VERSION 5.0.03.003 OR EARLIER.
    • For high-availability deployment, open standalone-full-ha.xml VERSION 5.0.03.004 OR LATER or standalone-ha.xml VERSION 5.0.03.003 OR EARLIER.
  2. In the file, edit the console-handler section as appropriate, and then save the file. 

Starting with 5.0.01.00, you can specify the logging level for servers in RPM.

  1. Stop the RPM server.
  2. Go to RLMhome/bin, and then open the start.bat (Windows) or start.sh (Linux) file in a text editor.
  3. In the file, modify the value of the LOG_LEVEL variable as appropriate.
  4. Save the file.

To configure time interval for system info job for versions 5.0.03.004 or later

By default, the system info job runs at a 10 minute interval. To modify the time interval, perform the following steps:

  1. Go to RLMhome/releases/vv.rr.nn/RPM/portal.war/WEB-INF/config and open the wildfly.yml file. 
  2. In the file, locate the system.info job.
    The following figure shows the system info job in the sample wildfly.yml file. 

    jobs:
      system.info:
        job: SystemInfo
        every: 600 # (seconds), every 10 minutes
        description: Display system level info like JVM Heap memory, threads, db connections
      audit.storage:
        job: AuditHandler::MessagesProcessor
        every: 60 #every 1 minute
        description: Stores queued audit messages
      scheduled_jobs.expired:
        job: ScheduledStepExpiredJob
        every: 3600 #every hour
        description: Notify users when scheduled step is expired
  3. Under the system.info job section, make changes to the job attribute that match your requirement. 
    By default, the value is set to 10 minutes. To change the time interval, enter the updated value in seconds.

NEW IN 5.0.03To configure time interval for system info job for versions 5.0.03.003 or earlier

By default, the system info job runs at a 10 minute interval. To modify the time interval, perform the following steps:

  1. Go to RLMhome/releases/vv.rr.nn/RPM/config and open the torquebox.yml file. 
  2. In the file, locate the system.info job section.
    The following figure shows the system info job in the sample torquebox.yml file. 
  3. Under the system.info job, make changes to the cron attribute that match your requirement. 
    By default, the value is set to 10 minutes. To change the time interval, follow the standard Cron time string format. For example, if you want to change the time interval to 15 minutes, change the string to '0 */15 * * * ?'
    For more information on cron string format and the allowed values and characters, see  CRON expression .

Logging in the RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward)

To view the RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward) server logs, go to RLMUIhome/apache/logs.

To define the server logging level in the RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward)

You can specify the server logging level in the RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward) using the Apache logging configuration.

  1. Go to RLMUIhome/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 in the Apache documentation.

    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.