No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight failed to start the services after unexpected reboot/failed to reinstall

Publication Date:  2017-05-25 Views:  591 Downloads:  0
Issue Description

Fault symptom: After the customer restarted the server without stopping the eSight, the eSight couldn't be started anymore :

Version Information: V300R006SPC502


Handling Process

First step: start the console from command prompt and provide us the output: 

From the commad to start eSight steps:

(1) Open the CMD windows

(2) execute command :

cd /d d:\eSight\bin  //the d:\eSight is eSight default directory.

(3)execute script

shutdown.bat  //stop the eSight server

startup.bat  //start the eSight server


Second step: Try to fix the MySQL service:



Third step :during remote session we found that there was a database that wasn’t existing anymore after the server was restarted without stopping the eSight. We tried to create again the database but without success. We couldn’t also restore the eSight because there wasn’t performed manual or automatic backup from eSight.

Root Cause

there was a database that wasn’t existing anymore after the server was restarted without stopping the eSight. We tried to create again the database but without success. We couldn’t also restore the eSight because there wasn’t performed manual or automatic backup from eSight.

Solution

Reinstalling the eSight server and check the below steps to be matched :

(1) Execute “set | findstr ENT_ROOT” command to get to the eSight install director, then check if the eSight install directory exists. If it exists, delete it.

(2) Execute “tasklist | findstr java” command to check whether the Java process still exists.

If you don’t have the java process, it’s shown normal.


(3)Execute “tasklist | findstr mysqld” command to check whether the mysql process still exists.

If haven’t mysql process, it shows normal.



After checking that all these processes/directories doesn't exist the installation of eSight can continue without getting this error :



Suggestions

Perform the periodic backup of the eSight server and database.

END