TRITON - Web Security Help, Version 7.7 - Websense

TroubleshootingYou may see this message if:Log Server is installed on a different machine than Policy Server, and the LogServer IP address is incorrectly set to localhost in TRITON - Web Security.You are not using Websense reporting tools.Log Server is associated with a different Policy Server instance.To verify that the correct Log Server IP address is set in TRITON - Web Security:1. Select the Settings tab of the left navigation pane, and then go to General >Logging.2. Enter the IP address of the Log Server machine in the Log Server IP address orname field.3. Click OK to cache your change, and then click Save and Deploy.If you are not using Websense reporting tools, or if Log Server is associated with adifferent Policy Server instance, you can hide the alert message in TRITON - WebSecurity.1. On the Main tab of the left navigation pane, go to Status > Alerts.2. Under Active Alerts, click Advanced.3. Mark Hide this alert for the “No Log Server installed” message.4. Click Save Now. The change is implemented immediately.More than one Log Server is installed for a Policy ServerTRITON - Web Security Help | Web Security Solutions | Version 7.7.xEach Policy Server instance can connect to only one instance of Web Security LogServer. When multiple instances of Log Server attempt to connect to the same PolicyServer, log data is not recorded properly, causing problems with multiple reportingtools.To resolve this issue:If multiple, active Log Server instances are running, uninstall all but one of theLog Server instances connecting to the Policy Server that is reporting the error.If you would like to configure multiple Log Server instances to communicate witha central Log Server that is responsible for recording data in the Log Database, seeExtending your Web Security deployment in the Deployment and InstallationCenter.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 onanother machine. Later, a Policy Server instance was installed on the LogServer machine.In all of these cases, the safest way to address the problem is:TRITON - Web Security Help 487