Summary
There are instances when we need to enable debug logging for the Officescan Standalone Smart Scan server then replicate the issue or problem so that we capture the root cause in the logs (for analysis).
We need to make sure we enable the debugging before we collect data otherwise it will be a waste of turnaround time.
Details
The Officescan Standalone Smart Scan console has a support section where you can click a button to collect troubleshooting data. This is convenient as it collects files such as the following:
- Configuration files for Officescan Standalone Smart Scan server
- Log files for Officescan Standalone Smart Scan server
- Configuration files for CentOS Linux Operating System
- Log files for CentOS Linux Operating System
- Core dumps if any
However if you collect data (using the smart scan console) right away when an issue happens then it will be collecting diagnostic logs instead of debug logs. To enable debug logging, Do the following:
- On the standalone smart scan server, go to command line. Go to /var/tmcss/conf
- Open a file called log.ini. You can use a text editor like pico or vi. Change log level from 1 to 6. Save and exit the file.
- To confirm that it is running in debug, go to /var/tmcss/debuglogs
- Open the latest diagnostic log (e.g. diagnostic_1.log, diagnostic_2.log, etc). If you see: "[DEBUG]" then it is in debugging mode. If you see: "[ERROR]" then it is in default diagnostic logging mode.
After enabling debugging, replicate the issue, then collect the data using the support section of the Smart Scan console. Don't forget to undo the changes to the log.ini file above so that it goes back to diagnostic logging. When you submit the data collected by Smart Scan console its logging is already in debug mode.
