Using log files to debug the BMC PATROL Agent and Integration Service connections

The following topic describes how to enable or disable debug to check for issues in the BMC PATROL Agent and Integration Service connections.

Checking BMC PATROL Agents that are connected to the Integration Service without enabling debug

To check BMC PATROL Agents that are actively connected to the Integration Service without enabling debug, see the installationDirectory\TSIMAgent\pw\pronto\logs\debug\PatrolAgentCache.dump file. The following is a sample of the PatrolAgentCache.dump file. 

Current Time : Tue
Dec 17 03:44:49 CST 2013
************ Dump start : IS Patrol Agent Cache ************
Patrol Agent :  
consoleIndex=0, guid=10005, host=pun-lpar-pat04.bmc.com, port=9876,
version=V9.5.00i, status=CONNECTED agsRequestTime=1387309761000
Patrol Agent :  
consoleIndex=1, guid=10001, host=vm-w23-rds545, port=3181,
version=V9.5.00i, status=CONNECTED agsRequestTime=1386954196000
************ Dump end : IS Patrol Agent Cache ************ 

Manually enabling debug on the Integration Service

To manually enable debug on the Integration Service, in the installationDirectory\TSIMAgent\pw\custom\conf\pronet.conf file, change the following configurations from:

#Global logging level. 0 means turning off debug.  1 means turning on debug.
pronet.apps.logging.debug=0
#pronet.apps.logging.debug.jserver=1
#pronet.apps.logging.debug.agentcontroller=1
#pronet.apps.logging.debug.agent=1
#pronet.apps.logging.debug.nttcpmon=1
.
.
.
#To enable the dll debug
pronet.apps.is.dll.debug.enable=false
#To enable the debug diag
pronet.apps.is.dll.diag.enable=false

to:

#Global logging level. 0 means turning off debug.  1 means turning on debug.
pronet.apps.logging.debug=1
#pronet.apps.logging.debug.jserver=1
#pronet.apps.logging.debug.agentcontroller=1
#pronet.apps.logging.debug.agent=1
#pronet.apps.logging.debug.nttcpmon=1
.
.
.
#To enable the dll debug
pronet.apps.is.dll.debug.enable=true
#To enable the debug diag
pronet.apps.is.dll.diag.enable=true

After you enable debug, check the following logs for details:

• installationDirectory\TSIMAgent\pw\pronto\logs\debug\IntegrationService.log
  
  The following message is displayed in the IntegrationService.log file, if the BMC PATROL Agent is disconnected from the Integration Service:

  DEBUG 12/17 05:07:07 IntegrationService   [ISExecutor-97] @ ISExecutor- @
  PatrolMessageListenerImpl:  [AGENT_DEL]
  ts=1387278427, consoleIndex=1, name=vm-w23-rds545.bmc.com, port=3181,
  version=V9.5.00i

• installationDirectory\TSIMAgent\pw\pronto\logs\debug\MessageServiceIS.log

DLL log files

The .dll files collect data from the BMC PATROL Agent and if there are issues during data collection, they are displayed in the following .dll log files:

• installationDirectory\TSIMAgent\pw\patrol\pis\logs\bppmpis-SA_DEFAULT-clm-pun-002154.errs
• installationDirectory\TSIMAgent\pw\patrol\pis\logs\bppmpis-clm-pun-002154_diag.out
• installationDirectory\TSIMAgent\pw\patrol\pis\logs\bppmpis-SA_DEFAULT-1387275673_debug.txt

Enabling Integration Service log files from the BMC TrueSight Infrastructure Management Server

Run the following command to debug issues between the TrueSight Infrastructure Management Server and the Integration Service:

pw debug on -a <IntegrationServiceHost>