More than one Log Server is installed for a Policy Server

Troubleshooting > Log Server and Log Database issues > More than one Log Server is installed for a Policy Server

More than one Log Server is installed for a Policy Server

Web Security Help | Web Security Solutions | Version 7.8.x

Each Policy Server instance can connect to only one instance of Web Security Log Server. When multiple instances of Log Server attempt to connect to the same Policy Server, log data is not recorded properly, causing problems with multiple reporting tools.

To resolve this issue:

If multiple, active Log Server instances are running, uninstall all but one of the Log Server instances connecting to the Policy Server that is reporting the error.

If you would like to configure multiple Log Server instances to communicate with a central Log Server that is responsible for recording data in the Log Database, see Extending your Web Security deployment in the Deployment and Installation Center.

If this error appears, but only one instance of Log Server is active, it is likely that:

Policy Server was not running when a Log Server instance was uninstalled.

The Policy Server IP address was changed after Log Server was installed.

During installation, Log Server connected to a Policy Server instance on another machine. Later, a Policy Server instance was installed on the Log Server machine.

In all of these cases, the safest way to address the problem is:

Uninstall the Log Server instance or instances currently connected to the Policy Server instance displaying the error.

Stop Websense Policy Server (via the Windows Services tool or the /opt/Websense/WebsenseDaemonControl command).

Navigate to the Websense bin directory (C:\Program Files or Program Files (x86)\Websense\Web Security\bin or /opt/Websense/bin) and make a backup copy of config.xml in another location. Do not skip this step.

Open the original config.xml file in a basic text editor (not an XML or HTML editor).

Near the top of the file, locate the WebsenseLogServer container. This contains the ID for the "ghost" Log Server instance.

Delete the entire container, including the close tag. For example:

Save and close the config.xml file.

Delete the config.xml.bak file from the Websense bin directory.

Use the Windows Services tool or /opt/Websense/WebsenseDaemonControl command to start Websense Policy Server.

Troubleshooting > Log Server and Log Database issues > More than one Log Server is installed for a Policy Server