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>Search


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


Failed to Start eSight After Upgrade

Publication Date:  2019-04-12 Views:  189 Downloads:  0

Issue Description

After eSight is upgraded and started in the SUSE11 environment, log in to the web GUI of eSight.

The maintenance GUI can be logged in successfully through port 8088. Stop eSight as the ossuser and then start eSight. Information in the following figure is displayed.

Handling Process

Verify that eSight is upgraded successfully. Check whether the version of struts2-core is 2.3.32 in the /opt/eSight/mttools/lib/web.common.lib file.

Check the database.

Run the #lsnrctl status esightlistener command to check the Oracle listener.

The command output indicates that the listener is not started.

Run the lsnrctl start esightlistener command to start the listener and database.

Log in to the CLI as the ossuser user, go to /opt/eSight/bin, and start eSight.

Log in to the web GUI of eSight. The login is successful.


The server restarts after each upgrade. In some systems, the database and listener are not automatically restarted. You need to manually start the database and listener using commands. If the database listener is abnormal, the login to eSight is abnormal.