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>


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


eSight Web-Service stopped

Publication Date:  2017-03-24 Views:  662 Downloads:  0
Issue Description



The solution showed in the image has the proposed to provide Internet service to public places and governmental buildings.


In order to keep in monitor the services and NE managed on the network, eSight has been implemented on the Main-Site (Sitio Central).


eSight has been implemented on Linux.


Firewalls on the Main-Site provide high availability in VRRP and HRP.

The server of eSight is NAT from private IP-Address ( to Public IP-Address.




Customer uses the web services of eSight to get a report of the remote sites.

They don’t have access to the web service of eSight from public IP-Address, neither from the same LAN.


After to insert the URL of the eSight (Web-Services), the web-browser does not display the eSight portal.


Other services like LogCenter are available from public network. So, public IP-Address is reachable.


Handling Process


  1. 1.  From the Firewall of the Main-Site the private IP-Address ( of the server is reachable by PING.



13:04:17  2017/02/20

  PING 56  data bytes, press CTRL_C to break

    Reply from bytes=56 Sequence=1 ttl=64 time=1 ms

    Reply from bytes=56 Sequence=2 ttl=64 time=1 ms

    Reply from bytes=56 Sequence=3 ttl=64 time=1 ms

    Reply from bytes=56 Sequence=4 ttl=64 time=1 ms

    Reply from bytes=56 Sequence=5 ttl=64 time=1 ms


  --- ping statistics ---

    5 packet(s) transmitted

    5 packet(s) received

    0.00% packet loss

                      round-trip min/avg/max = 1/1/1 ms



  1. 2.  Firewall can register sessions of HTTPS request from the public network to the eSight-Server.
  2. 3. Getting connection by SSH with eSight-Server from the public network. The server replies.

         So, the issue is not related with a trouble in the network.


  1. 4. Review the listener status of the Oracle-DB.


eSightServer:~ # netstat -aon | grep 1521

tcp        0      0*                       LISTEN      off (0.00/0/0)

tcp        0      0         ESTABLISHED keepalive (4398.66/0/0)

tcp        0      0           ESTABLISHED keepalive (1219.96/0/0)

tcp        0      0          ESTABLISHED off (0.00/0/0)

tcp        0      0         ESTABLISHED keepalive (302.40/0/0)

tcp        0      0         ESTABLISHED keepalive (5054.06/0/0)

tcp        0      0         ESTABLISHED keepalive (7053.03/0/0)

tcp        0      0         ESTABLISHED keepalive (3022.32/0/0)

Root Cause

Listener port of Database is Off.


eSightServer:~ # netstat -aon | grep 1521

tcp        0      0*                       LISTEN      off (0.00/0/0)


Log information shows that server’s operating system has a reboot record on February 10 and 13. Days ago of the issue were reported.


eSightServer:/opt/eSight/AppBase/var/iemp/log # last

root     pts/1    Fri Feb 17 01:40   still logged in  

root     pts/0    Fri Feb 17 01:07   still logged in  

reboot   system boot  3.0.101-0.35-def Mon Feb 13 04:08         (3+22:40)  

reboot   system boot  3.0.101-0.35-def Fri Feb 10 14:38         (6+12:10) 


eSight logs shows that there was no login since February 10, indication that eSight has stopped since February 10, which is consistent with system record.


eSightServer:/opt/eSight/AppBase/var/iemp/log # ll

total 77948

-rw-------  1 ossuser ossgroup   769754 Feb 10 08:30

-rw-------  1 ossuser ossgroup   864491 Feb 10 09:32

-rw-------  1 ossuser ossgroup   902632 Feb 10 10:32

-rw-------  1 ossuser ossgroup   784375 Feb 10 11:21

-rw-------  1 ossuser ossgroup   884202 Feb 10 12:26

-rw-------  1 ossuser ossgroup   889212 Feb 10 13:29

-rw-------  1 ossuser ossgroup   921252 Feb 17 01:45

-rw-------  1 ossuser ossgroup   811188 Feb 17 01:51

-rw-------  1 ossuser ossgroup  1254697 Feb 17 01:58

-rw-------  1 ossuser ossgroup   832061 Feb 17 02:05

-rw-------  1 ossuser ossgroup  1013352 Feb 17 02:13


Logging by SSH to eSight-Server.

a)      Connect like ‘oracle’ user to review the status of Oracle-database.


                     eSightServer:~ # su – oracle

                     oracle@eSightServer:~> sqlplus / as sysdba


                     SQL*Plus: Release Production on Fri Mar 3 09:09:52 2017


                     Copyright (c) 1982, 2013, Oracle.  All rights reserved.


                     Connected to an idle instance.


b)      Initialize the SQL-DB service.


SQL> startup

ORACLE instance started.


Total System Global Area 3290345472 bytes

Fixed Size                  2257720 bytes

Variable Size             704646344 bytes

Database Buffers         2533359616 bytes

Redo Buffers               50081792 bytes

Database mounted.

Database opened.


c)       Initialize the eSight listener.


oracle@eSightServer:~> lsnrctl start esightlistener


LSNRCTL for Linux: Version - Production on 03-MAR-2017 10:08:15


Copyright (c) 1991, 2013, Oracle.  All rights reserved.


Starting /opt/oracle/product/11.2/db_1/bin/tnslsnr: please wait...


TNSLSNR for Linux: Version - Production

System parameter file is /opt/oracle/product/11.2/db_1/network/admin/listener.ora

Log messages written to /opt/oracle/diag/tnslsnr/eSightServer/esightlistener/alert/log.xml







Alias                     esightlistener

Version                   TNSLSNR for Linux: Version - Production

Start Date                03-MAR-2017 10:08:17

Uptime                    0 days 0 hr. 0 min. 0 sec

Trace Level               off

Security                  ON: Local OS Authentication

SNMP                      OFF

Listener Parameter File   /opt/oracle/product/11.2/db_1/network/admin/listener.ora

Listener Log File         /opt/oracle/diag/tnslsnr/eSightServer/esightlistener/alert/log.xml

Listening Endpoints Summary...



Services Summary...

Service "esight" has 1 instance(s).

  Instance "esight", status UNKNOWN, has 1 handler(s) for this service...

The command completed successfully



d)      Startup eSight services.


eSightServer:/opt/eSight/bin # su ossuser

ossuser@eSightServer:/opt/eSight/bin> sh

starting eSight system

starting watchdog

starting watchdog done.

starting sysmonitor

starting sysmonitor done.

starting eSight daemons


4 services will be executed


syslog  ............    RUNNING

iempssoAgent    ............    RUNNING

nodejs  ............    RUNNING

nginx   ............    RUNNING

starting eSight daemons done.

starting eSight svc agents


1 service will be executed



eSightAgent     ............    RUNNING

starting eSight svc agents done.

starting eSight system succeeded.