This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
PRODUCT:
BMC Release Process Management
COMPONENT:
Release Process Management
APPLIES TO:
BRPM 4.4 onwards.
QUESTION:
How to enable debug logging in BRPM?
ANSWER:
BRPM from version 4.4 onwards, runs in a JBoss application server.
For BRPM 5.0 onwards, you can enable debug by just editing the <BRPM_INSTALL_HOME>/bin/start.sh by setting the variable:
From:
export LOG_LEVEL="INFO"
To
export LOG_LEVEL="DEBUG"
export LOG_LEVEL="INFO"
To
export LOG_LEVEL="DEBUG"
For BRPM version 4.4.x to 4.8.x, debug can be enabled the below 2 ways:
Method1: By editing the standalone.xml or standalone-ha.xml (for cluster configuration).
The standalone-xml or standalone-ha.xml can be found in BRPM_INSTALL_HOME/server/jboss/standalone-configuration folder.
Edit the standalone.xml and change as below:
Edit the standalone.xml and change as below:
From:
<root-logger>
<level name="${jboss.logging.level:INFO}"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
To:
<root-logger>
<level name="${jboss.logging.level:DEBUG}"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
Restart BRPM process.
If the BRPM instance is a part of a cluster setup then you need to make the same changes in standalone-ha.xml on all the nodes of the cluster and restart all of them.
Method2: By editing the BRPM startup script. <level name="${jboss.logging.level:INFO}"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
To:
<root-logger>
<level name="${jboss.logging.level:DEBUG}"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
Restart BRPM process.
If the BRPM instance is a part of a cluster setup then you need to make the same changes in standalone-ha.xml on all the nodes of the cluster and restart all of them.
The startup script is located in <BRPM_INSTALL_HOME>/bin
For windows its start.bat and for linux its start.sh.
Add the additional argument to the executable as below:
"$EXECUTABLE" -c standalone-ha.xml -b $NODE_IP -Djboss.node.name=$NODE_NAME -Djboss.logging.level=DEBUG > /dev/null 2>&1 &
For windows its start.bat and for linux its start.sh.
Add the additional argument to the executable as below:
"$EXECUTABLE" -c standalone-ha.xml -b $NODE_IP -Djboss.node.name=$NODE_NAME -Djboss.logging.level=DEBUG > /dev/null 2>&1 &
https://youtu.be/xo3qKE_i9RI
Article Number:
000148875
Article Type:
Comments