eSight Cannot Start Due to Failure of Core File Check

Question

When eSight is being started, eSight Console reports core file exceptions.

Answer

After installation, patch installation, upgrade, multi-subnet modification, and IP address change, eSight automatically backs up core files related to the running and basic services of eSight. During eSight startup and healthiness check, the system checks whether the XML structure of the core files is correct and whether the core files exist.

• When an error is reported during eSight environment check or the healthiness check is abnormal, users can perform the following operations to restore core files. In other scenarios, do not execute the core file restoration script.
• The restoration method described here can be used to restore only core files backed up the last time. Configurations generated in the interval between the last backup time and the restoration operation time are lost. If the fault persists after the core files are restored, contact Huawei technical support.
• In the high availability system, perform the following operations only on the active server.

• Windows operating system
  1. Log in to the server as the administrator.
  2. Access the directory eSight installation directory\mttools\tools.
  3. run the following script. caclsUser.bat
  4. Execute the corefile_backup.bat script.
  5. After the script is executed successfully, use eSight Console to start eSight.
• SUSE Linux or EulerOS operating system
  1. Log in to the server as the ossuser user.
  2. Access the directory.

     cd eSight installation directory/mttools/tools

     ossuser@SZV1000309581:cd /opt/eSight/mttools/tools

  3. Run the following command:

     sh corefile_backup.sh

     ossuser@SZV1000309581:/opt/eSight/mttools/tools> sh corefile_backup.sh

  4. After the script is executed successfully, restart eSight.