Go to the table of contents Go to the previous page Go to the next page View or print as PDF
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:
*
*
Charts on the Status > Dashboard page stop updating
*
*
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.
Log Server may be unavailable if:
*
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.
*
Verify the amount of free disk space on the Log Server machine, and remove extraneous files, as needed.
*
*
See The Master Database is more than 1 week old and The Master 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.
*
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.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Copyright 2018 Forcepoint. All rights reserved.