Banner Agent 4.1.x - Job Capture debug - capture log is created but nothing is written to it
search cancel

Banner Agent 4.1.x - Job Capture debug - capture log is created but nothing is written to it

book

Article ID: 267208

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

In 4.x versions of the Banner Agent, Job Capture debug is not working.  When working properly, enabling Job Capture debug is as follows:

  • Job capture debug is turned on by creating a 0 byte file in Banner Agents capture directory (ie. $AW_HOME/Banner/TEST/capture)
    • cd $AW_HOME/Banner/TEST/capture
    • touch Debug
  • The Banner Agent must be stopped and restarted, either in the Application or from the server command line. At the command line, use
    • stopso TEST  <-- the Banner agent name
    • startso TEST
  • Capture debug details will be written to the capture/log/capture.log file (ie. $AW_HOME/Banner/TEST/capture/log/capture.log)

With the current bug, you see the creation of the capture.log but nothing is written to it.  

Environment

Release : RA Banner 4.x.x

Resolution

This is being investigated by Broadcom Development and will be fixed in a future release of the Agent Agent under bug number RA_BANNER-215

There is no workaround at this time.