Log Server has not received log files from Filtering Service

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

Log Server receives Internet usage information from Filtering Service and stores it in the Log Database. If Log Server is not receiving files from Filtering Service, no data is being logged, recent data is not displayed on the Status > Dashboard page, and you cannot generate Internet usage reports that include recent data.

Log Server may not be receiving files from Filtering Service if:

Filtering Service is not running.

See Filtering Service is not running for information about addressing this issue.

The two services are not able to communicate across the network.

Verify that there have been no recent changes to firewall rules that might affect traffic between the machines on port 55805 (default), or the custom port your organization uses.

Use a utility like telnet or ping to verify that the machines can communicate.

Verify that the Log Server IP address and port (55805, by default) is correct on the Settings > General > Logging page in the Web Security manager.

If the loopback address (127.0.0.1) or "localhost" is shown, enter the actual IP address of the Log Server machine.

Use the Check Status button on the Settings > General > Logging page to verify that it is possible to connect to Log Server.

If the status check fails:

Verify there is no firewall blocking the port.

Run the following command on the Log Server machine to verify that Log Server is listening on the port:

netstat -ban > port.txt

Network Agent, Content Gateway, or a third-party integration product is not configured properly and not receiving Internet traffic.

See Network Agent issues and Network Configuration for information about addressing Network Agent configuration issues.

See the Deployment and Installation Center and Content Gateway Help for information about addressing Content Gateway configuration issues.

See the Deployment and Installation Center and your vendor's documentation for information about other supported integrations.

There is not sufficient disk space for Log Server to create new cache files.

See Low disk space on the Log Server machine for more information about addressing this issue.

Filtering Service is associated with a Policy Server that is not configured for logging or is sending logs to TestLogServer.

See No Log Server is installed for a Policy Server and Configuring how requests are logged for more information about addressing this issue.

Files cannot be written to the cache or BCP folders.

Verify that the path defined for ODBC cache files or BCP files on the Settings > Reporting > Log Server page is correct, and that the account used to run Log Server has permissions to write to the path.

Log Server did not install properly.

Use the following steps to verify that the Log Server service is registered properly with the Windows operating system:

Use the Windows Services tool to stop the Websense Log Server service.

Open a command prompt (Run > cmd) and navigate to the Websense bin directory (C:\Program Files or Program Files (x86)\Websense\Web Security\bin, by default).

Enter the following command.

LogServer .exe -c