Jump to content

Unable to connect to ERA after installing Rouge Detector


Interceptor
 Share

Go to solution Solved by Interceptor,

Recommended Posts

I tried to install Rouge Detector to already existing  ERA Server  on Ubuntu and now im unable to connect to webconsole.

Which logs should I  check? "last-error" from RDS or RA?

Link to comment
Share on other sites

  • ESET Staff

I tried to install Rouge Detector to already existing  ERA Server  on Ubuntu and now im unable to connect to webconsole.

Which logs should I  check? "last-error" from RDS or RA?

 

Please check ERA logs, especially SERVER's trace log. In status.html you should also see whether AGENTs are connecting. Are relevant ERA services running? Is network on this system working, as it may be affected by RogueDetectorSensor.

What kind of error do you get when logging to SERVER, or not even login page is shown?

Link to comment
Share on other sites

I can ping the server but I cant open webconsole page.

Service eraserver status says is start/running.

I'll check Your other suggestions.

Edited by Interceptor
Link to comment
Share on other sites

  • ESET Staff

I can ping the server but I cant open webconsole page.

Service eraserver status says is start/running.

I'll check Your other suggestions.

 

In case any won't help, try to restart Apache Tomcat, and also check JAVA_HOME and related environment variables are set correctly, especially in case you have updated Java runtime (jre/jdk) in the meantime.

Link to comment
Share on other sites

Trace log and status.html looks fine in my opinion.

But in catalina there are some errors it could be a reason?

Ill be glad if You take a look on those logs

 

-EDIT-

Logs removed

Edited by Interceptor
Link to comment
Share on other sites

  • ESET Staff

There are two interresting errors in log:

 

First one indicates there is something wrong with HTTPS certificate. Does file /home/administrator/eraserver.keystore exists? Are there sufficient permissions for user that is tomcat7 running under? Maybe SELinux is blocking access?

SEVERE: Failed to load keystore type JKS with path /home/administrator/eraserver.keystore due to /home/administrator/eraserver.keystore (Brak dostępu)

Second one is:

java.net.BindException: Adres jest już w użyciu

which indicates that tomcat failed to open port for listening because it was already taken. You can use command "netstat -tulpn" to check what processes are listening on which port. Maybe your original Webconsole port was taken by other application.

Edited by MartinK
Link to comment
Share on other sites

  • Solution

Keystroe access I have already solved.

Reason was probably:

java.net.BindException: Adres jest już w użyciu

I had to:

service tomcat7 stop
lsof |grep tomcat
kill -15 <PID>
service tomcat7 start

and now it works. Probably port was hold by old instance of tomcat and service or even server restart couldnt loose it.

Thanks MartinK Your support was very helpful

Edited by Interceptor
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...