Exporting System Debug Logs

This operation exports system debug logs, hardware configuration data, and system running parameters.

Context

The log severity indicates the importance of logs. Debug logs are classified into four severities: error, warning, info, and debug.

Procedure

When the eReplication Server service is started
1. On the menu bar, select Settings.
2. In the navigation tree, choose Log Management > System Debug Log.
3. Export system debug logs.
  In the Export System Debug Logs area, click Export.
  
  If you need to use detailed system debug logs to locate faults, you can adjust the log level. For details, see Changing the eReplication Server Log Level.
For details about how to export system debug logs when the eReplication Server service is not started.
1. Use PuTTY to log in to the eReplication Server as user DRManager.
2. Run su - OMUser, and input the password of the OMUser account to switch to the OMUser account.
3. Run the TMOUT=0 command to prevent PuTTY from exiting due to session timeout.
  
  After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run exit to exit the system after completing your operations.
4. Run the om_manager command to access the O&M page.
```
[OMUser@huawei1 ~]$ om_manager
######################################################################
###                     Welcome to the O&M mode                    ###
###                                                                ###
###   1.Run 'help' to query O&M commands                           ###
###   2.Run 'exit' to exit O&M mode                                ###
######################################################################
##
```
5. Enter help to view the O&M commands.
6. Run the data_collect command.

System Response

Linux: The collected information is saved to the /home/ICUser directory and named DataCollect.zip.