Look for problems when temporary files not created on the Log Server machine

Before you begin

Log Server receives information from Filtering Service and stores it in temporary files before sending it to the Log Database. Problems on the Log Server machine can interfere with that process.

First, monitor the cache or BCP folder on the Log Server machine (C:\Program Files\Websense\Web Security\bin\Cache or bin\Cache\BCP, by default) to verify that temporary files are being created. If temporary files are being created and processed normally, files appear in the directory only briefly before the data is processed into the Log Database and the temporary file is deleted.

If temporary files are not being created, and there are no problems with Filtering Service communication:

Steps

  1. In the Web Security module of the Forcepoint Security Manager, verify that the Log Server IP address or hostname and port values on the Settings > General > Logging page are correct and match the IP address or hostname and port values shown on the Settings > Reporting > Log Server page.
    • If your deployment includes appliances, the Log Server IP address must be used.
    • Make sure that the actual IP address appears, and not 127.0.0.1.
  2. Check for firewalls that might be blocking the logging port (55805, by default).
  3. Make sure the Log Server executable version is correct:
    1. Navigate to the bin directory on the Log Server machine (C:\Program Files\Websense\Web Security\bin, by default).
    2. Right-click the LogServer.exe file and select Properties.
    3. Select the Details tab, and verify that the Product Version matches your current web protection product version. Find current version information on the Help > About Forcepoint Security Manager page in the Forcepoint Security Manager.
  4. Check the file paths set up for cache and BCP files on the Settings > Reporting > Log Server page to make sure the folders exist, and that Log Server has permission to write to them.
  5. If TestLogServer is being used, make sure it is set up to forward data to Log Server. (See Using TestLogSe rver forTroubleshooting for more information.)