Log Server is not running

Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.x

If Log Server is not running, or if other web protection components are unable to communicate with Log Server:

Internet usage information is not stored.

Charts on the Status > Dashboard page stop updating

You may not be able to generate reports that contain recent data.

Sync Service cannot forward reporting data from the hybrid service.

Note that although Sync Service cannot forward the hybrid service reporting data, the information is not lost. Instead, Sync Service holds it until communication with Log Server resumes.

(With v8.5.4) Files are not forwarded to Cloud App Service for processing.

Log Server may be unavailable if:

It is unable to contact the Log Database after 20 attempts.

Make sure that the Log Database machine is running, that Microsoft SQL Server is operating properly, and that network communication has not been interrupted between the Log Server and Log Database machines.

There is insufficient disk space on the Log Server machine.

Verify the amount of free disk space on the Log Server machine, and remove extraneous files, as needed.

You changed the Microsoft SQL Server password without updating the ODBC or Log Server connection.

It has been more than 14 days since the Forcepoint URL Database was downloaded successfully.

See The Forcepoint URL Database is more than 1 week old and The Forcepoint URL Database does not download for information about addressing this issue.

The logserver.ini file is missing or corrupted.

Navigate to the bin directory (C:\Program Files\Websense\Web Security\bin, by default) and make sure that you can open logserver.ini in a text editor. If this file has been corrupted, replace it with a backup file.

You stopped Log Server to avoid logging Internet usage information.

Check the Windows Services tool to verify that Log Server has started, and restart the service if necessary (see Stopping and starting web protection services).

If none of these address the issue, check the Windows Event Viewer and websense.log file (in the bin directory) for error messages from Log Server in order to better understand the problem.