Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Log Server and Log Database issues > Log Server has not received log files from Filtering Service
Log Server has not received log files from Filtering Service
Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.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:
*
See Filtering Service is not running for information about addressing this issue.
*
*
*
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 Web > Settings > General > Logging page in the Forcepoint 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:
*
*
netstat -ban > port.txt
*
*
See Network Agent issues and Configure Network Agent for information about addressing Network Agent configuration issues.
*
See the Content Gateway Online 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.
*
See Low disk space on the Log Server machine for more information about addressing this issue.
*
See No Log Server is installed for a Policy Server and Configuring how requests are logged for more information about addressing this issue.
*
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.
*
Use the following steps to verify that the Log Server service is registered properly with the Windows operating system:
1.
2.
Open a command prompt (Run > cmd) and navigate to the bin directory (C:\Program Files\Websense\Web Security\bin, by default).
3.
LogServer -c
*
*
4.
LogServer -u
5.
LogServer -i
6.
LogServer -c
If none of the items above addresses your issue:
*
1.
2.
Navigate to the bin directory (C:\Program Files\Websense\Web Security\bin, by default).
3.
LogServer -v
This should match the version shown on the Help > About... page in the Forcepoint Security Manager.
*
*
If Log Server stops running immediately after restarting and the runtime error "C error (Visual C Runtime Error)" displays, delete the LogServer.state file located in the Log Server Cache folder (C:\Program Files\Websense\Web Security\bin\Cache, by default) and restart the Websense Log Server service.
*
See support.forcepoint.com for detailed information about TestLogServer.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Log Server and Log Database issues > Log Server has not received log files from Filtering Service
Copyright 2018 Forcepoint. All rights reserved.