Jump to content

Archived

This topic is now archived and is closed to further replies.

Aditu Prod

ESMC not functionning

Recommended Posts

Good morning all,

I have installed ESMC on a server (Windows Server 2008R2 Foundation). Everything has gone fine (ESEt Server, SQL Server, Tomcat ..) but my console at localhost/era/webconsole does not work: i have an error page with message error_connection_refused. My tomcat is OK at localhost:8080 but if i look at the process with netstat -aonb, tomcat is not listening.

Where are the logs to debug ? Any ideas ?

Thanks for any answers

Best regards,

David Alarcon

 

Share this post


Link to post
Share on other sites

Just to be sure: have you actuilly checked standard HTTP port 443? In case so, it might be problem of tomcat itself, which might be not compatible with Java you are using. I would recommend to check whether Apache Tomcat installed with ESMC is actually running and if not, please check it's logs.

Second most common issue is port conflict - please double check there is no other service listening on these ports -> we have had cases where IIS was present and blocking ports.

Share this post


Link to post
Share on other sites

Thanks MartinK for your reply. Yes, that is the problem: there is nothing listening at port 443 ! No IIS is installed. For Tomcat, as i had the problem with Tomcat7, i have installed Tomcat9. This is the one that is responing at localhost:8080. If i look at Tomcat catalina log, no errors (sample below):

19-Aug-2019 16:14:39.300 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.292] V1 [] <INFO> ERA Web Server starting...
19-Aug-2019 16:14:39.301 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.301] V1 [] <INFO> ERA Web Server Version: 7.0.429.0
19-Aug-2019 16:14:39.303 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.303] V1 [] <DEBUG> ERA Web Server starting...
19-Aug-2019 16:14:39.303 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.303] V1 [] <DEBUG> ERA Web Server Version:7.0.429.0
19-Aug-2019 16:14:39.338 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.338] V2 [] <INFO> Loaded config value: remote_address_source=connection
19-Aug-2019 16:14:39.338 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.338] V2 [] <INFO> Loaded config value: HSTS_enable=no value loaded
19-Aug-2019 16:14:39.370 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.370] V1 [] <INFO> ERA Web Server has started.
19-Aug-2019 16:14:39.370 INFOS [main] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-08-19 16:14:39.370] V1 [] <DEBUG> contextInitialized
19-Aug-2019 16:14:39.406 INFOS [main] org.apache.catalina.startup.HostConfig.deployWAR Le déploiement de l'archive de l'application web [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\era.war] s'est terminé en [7 237] ms
19-Aug-2019 16:14:39.407 INFOS [main] org.apache.catalina.startup.HostConfig.deployDirectory Déploiement du répertoire d'application web [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\docs]
19-Aug-2019 16:14:39.443 INFOS [main] org.apache.catalina.startup.HostConfig.deployDirectory Le déploiement du répertoire [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\docs] de l'application web s'est terminé en [36] ms
19-Aug-2019 16:14:39.444 INFOS [main] org.apache.catalina.startup.HostConfig.deployDirectory Déploiement du répertoire d'application web [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\manager]
19-Aug-2019 16:14:39.505 INFOS [main] org.apache.catalina.startup.HostConfig.deployDirectory Le déploiement du répertoire [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\manager] de l'application web s'est terminé en [60] ms
19-Aug-2019 16:14:39.505 INFOS [main] org.apache.catalina.startup.HostConfig.deployDirectory Déploiement du répertoire d'application web [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\ROOT]
19-Aug-2019 16:14:39.537 INFOS [main] org.apache.catalina.startup.HostConfig.deployDirectory Le déploiement du répertoire [C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\webapps\ROOT] de l'application web s'est terminé en [32] ms
19-Aug-2019 16:14:39.542 INFOS [main] org.apache.coyote.AbstractProtocol.start Démarrage du gestionnaire de protocole ["http-nio-8080"]
19-Aug-2019 16:14:39.558 INFOS [main] org.apache.coyote.AbstractProtocol.start Démarrage du gestionnaire de protocole ["ajp-nio-8009"]
19-Aug-2019 16:14:39.564 INFOS [main] org.apache.catalina.startup.Catalina.start Le démarrage du serveur a pris [7 527] millisecondes


But still nothing at 443 ... To compare, i have another customer with Eset and effectively Tomcat is listening in 443 ..

 

Any other ideas ? Best regards

Share this post


Link to post
Share on other sites

In case it is not tomcat installed by our installer (which is not as currently released versions were distributed with tomcat7), I would recommend to check tomcat configuration file and double check there is actually enabled connector on port 4443, i.e. thee should be something like this in server.xml file:

<Connector ... port="443" ... SSLEnabled="true" scheme="https" secure="true" ... keystoreFile="C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\tomcat.keystore" keystorePass="..." keyAlias="tomcat"/>

In case so, most common issue with startup of this connector is problem with TLS certificate. It should be visible from logs, but not sure which one - in case it won't be, check presence of certificate file.

Share this post


Link to post
Share on other sites

Finaly, i have found the solution !!! I have uninstalled Tomcat 9, then i have load ESET setup, choose ESET Webconsole so the wizard has installed ESMC and Tomcat 7. But at this point, Tomcat7 service was unable to start. So in a glimpse of an idea, i thought of Java ... So i have uninstalled Java and install Amazon Correto 8.222 and HOP ! everything works Now !!

So to summarize, the solution was to use Amazon Correto instead of Java ...

 

Again, thanks for all replies and support

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...