MicroStrategy components generate tons of logs about low-level activity such as memory use, service information, errors, and so on. One of the most valuable logs is DSSErrors.log. If MicroStrategy has any problems, it is good practice to start from this log and look at the information. You can find it using this command:

# cd /root/mstr10/microstrategy_logs

If we open the log file, we can see rows of data and search information about particular issues:

For example, let's imagine that the MicroStrategy server was shut down. In order to understand why it happened, we should open DSSErrors.log and look to see what the problem is. It will be in the last couple of rows.

How the DSSErrors file works

There are two files, as shown in the following screenshot:

The default size of DSSErrors.log is 2048 KB. When it becomes more than 2048 KB, MicroStrategy renames it DSSErrors.log.bak and creates a new DSSErrors.log file.

It is possible to change the destination of the DSSErrors.log file. Here are links that give a detailed overview of how to do it:

• https://community.microstrategy.com/t5/Server/TN13943-How-to-change-the-log-destination-for-the-DSSErrors-log/ta-p/174444
• https://community.microstrategy.com/t5/Architect/TN13940-How-to-change-the-log-destination-for-the-DSSErrors-log/ta-p/174442