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

The Console Fails to Connect to the Log Server

Publication Date:  2012-07-24 Views:  40 Downloads:  0
Issue Description
Open the Internet Explorer on the console, enter the universal resource locator (URL) of the log sever on the address bar and then press Enter. The login interface of the log server cannot be accessed.
Alarm Information
None
Handling Process

1. Run the command described below on the console to check the network connection between the console and the log server.
ping LOG-SERVER-IP
"LOG-SERVER-IP" refers to the IP address of the log server. During the operations, ensure that you enter the IP address of the log server.

  •  If the system displays reply from..., it indicates that the network connection between the console and the log server is normal. Go to step 2 to continue.
  • If the system does not display reply from..., it indicates that the network connection between the console and the log server is abnormal. Contact the administrator to solve the network interworking problem.


2. Log in to the server where the log server resides as the administrator. Run the following command in the command line window to check whether another process occupies port 80:
netstat -abn
In normal cases, the process that occupies port 80 is tomcat6.exe. If there is another process occupying port 80, stop the process in Windows Task Manager, and then start the log server. The fault is located.
3. Log in to the server where the log server resides as the administrator. Run the following command in the command line window to check whether the Secospace eLog LogServer is started:
services.msc
If the service is not started, you need to start it.
4. Start the log server.
5. Log in to the Secospace eLog management interface again on the console.
If the Secospace eLog home page is displayed properly, it indicates that the fault is removed.

Root Cause

The possible reasons are described as follows:

  • The console fails to communicate with the log server.
  • Other services running on the server conflict with the services  of the log server.
  • The log server is not started.
Suggestions
None.

END