Process To Enable And Disable Full Debugging For Troubleshooting
search cancel

Process To Enable And Disable Full Debugging For Troubleshooting

book

Article ID: 303590

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Steps for enabling more verbose logging to further troubleshoot an issue in NCM, and steps for disabling. 

Environment

NCM 10.X

Resolution


The following steps explain how to enable and disable full debugging in NCM. Note: You will need root/administrative access to the device server(s) to edit the necessary files mentioned in the following instructions.

Enabling full debugging
To enable full debugging in VoyenceControl, do the following:

  1. Open the logs.cfg file in the following directory on the device server:

    $VOYENCE_HOME/conf/logs.cfg
    

     
  2. Uncomment the following line in the logs.cfg file:

    #*:log(0-9):file(10x1000000)
    

     
  3. Save and quit the logs.cfg file.
  4. Restart the voyence service on your device server as follows, depending on your environment: 

    • Linux/Solaris: Run the following command:

      /etc/init.d/voyence restart 
      

       
    • Windows: Restart the NCM_commmgr service found in the Services console of the Computer Management administrative tool on your device server.

Disabling full debugging
To disable full debugging in VoyenceControl, do the following:

  1. Open the logs.cfg file in the following directory on the device server:
    $VOYENCE_HOME/conf/logs.cfg 
    

     
  2. Comment out (#) the following line:
    *:log(0-9):file(10x1000000)
    
     
  3. Save and quit the logs.cfg file.
  4. Restart the voyence service on your device server as follows, depending on your environment: 

    • Linux/Solaris: Run the following command:
      /etc/init.d/voyence restart 
      

       
    • Windows: Restart the NCM_commmgr service found in the Services console of the Computer Management administrative tool on your device server.



Additional Information

The variable $VOYENCE_HOME refers to the installed location of VoyenceControl, typically:

/opt/voyence

or

/home/powerup.