ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to enable CSAPI debug logging in Protection Engine 7.8 and later on Linux

book

Article ID: 164895

calendar_today

Updated On:

Products

Protection Engine for Cloud Services Protection for SharePoint Servers Protection Engine for NAS

Issue/Introduction

CSAPI logging is intended for debugging, therefore it should be utilized only in case of necessity by request of a Symantec Support Engineer.

The Symantec Protection Engine (SPE) process model has changed in SPE 7.8 and later, therefore configuration requires modification in symcmicrodefsmgr.sh script as well.

Resolution

Enabling CSAPI debug logging

  1. Stop the SPE service.
    /etc/init.d/symcscan stop
     
  2. Take a backup of the current symcscan.sh script and symcmicrodefsmgr.sh script.
    cd /opt/SYMCScan/bin
    cp -p symcscan.sh symcscan.sh.org
    cp -p symcmicrodefsmgr.sh symcmicrodefsmgr.sh.org
     
  3. Insert the following lines right after comment in symcscan.sh and symcmicrodefsmgr.sh.
    CSAPI_DEBUG_LOG=/var/log/csapi.log
    CSAPI_DEBUG_LEVEL=5
    CSAPI_DEBUG_FILE_SIZE_LIMIT=104857600
    CSAPI_DEBUG_MAX_LOG_FILES=1 export CSAPI_DEBUG_LOG export CSAPI_DEBUG_LEVEL export CSAPI_DEBUG_FILE_SIZE_LIMIT
    export CSAPI_DEBUG_MAX_LOG_FILES
     
  4. Restart symcscan.
     /etc/init.d/symcscan start
     
  5. Verify CSAPI logs are being created and log messages are yielded.


Disabling CSAPI debug logging 

  1. Stop the SPE Service
     /etc/init.d/symcscan stop
     
  2. Comment out the lines inserted in step 3 above or replace with the original script.
  3. Restart symcscan
     /etc/init.d/symcscan start