Web Security Log Server Troubleshooting Guide : Incorrect or missing data in Web Security reports
|
|
Windows: Use the Services dialog box (Start > Administrative Tools > Services) to verify that Websense Filtering Service is Started.
|
|
Linux: Use the /opt/Websense/WebsenseDaemonControl command to make sure that Filtering Service is running.
|
2.
|
Go to the Settings > General > Logging page in TRITON - Web Security and click Check Status to verify that Log Serveris listening at the specified IP address or hostname, and on the specified port.
|
|
Verify the Log Server IP address or hostname and port values. The values on the Settings > General > Logging page must match those on the Settings > Reporting > Log Server page.
|
|
Make sure no firewall is blocking the port (55805, by default).
|
|
Use a utility like telnet or ping to verify that the Log Server and Filtering Service machines can communicate.
|
|
1.
|
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.
|
a.
|
Navigate to the Websense bin directory on the Log Server machine (C:\Program Files (x86)\Websense\Web Security\bin, by default).
|
b.
|
c.
|
Select the Details tab, and verify that the Product Version matches your current Websense product version. Find current version information on the Help > About the TRITON Console page in the TRITON console.
|
4.
|
Check the file paths set up for cache and BCP files on the Settings > Reporting > Log Server page in TRITON - Web Security to make sure the folders exist, and that Log Server has permission to write to them.
|
5.
|
1.
|
If Log Server has been configured to use BCP insertion, go to the Settings > Reporting > Log Server page in TRITON - Web Security and change the insertion method to ODBC.
|
4.
|
Make sure there is only one copy of BCP.exe on the Log Server machine.
|
5.
|
If the Websense Log Server service is listed as Started in the Windows Services dialog box, and the alert "Service was not found" appears, follow the steps listed in Web Security Log Server and Windows registration.
|
|
Use the Settings > Reporting > Log Database page in TRITON - Web Security to delete or move older partitions. To do this, scroll to Available Partitions, mark each partition to be deleted and click Delete.
|
|
Make sure tempdb is not full. Tempdb filling up is often a symptom of other SQL Server problems. Check for SQL Server errors about tempdb to resolve the underlying issue. Once the issue is resolved, ask your Database Administrator or IT department to stop and restart the Microsoft SQL Server services to clear tempdb. (If the underlying issue is not resolved, tempdb may grow again very quickly.)
|
2.
|
If you are using Microsoft SQL Server Standard or Enterprise, make sure the SQL Server Agent service is running for the database instance that hosts the Log Database.
|
3.
|
|
The initial size (Init Size field value) for the data and log files (set on the Settings > Reporting > Log Database page) is not greater than maximum size set by your Database Administrator.
|
|
The File Path entries for the data and log files on the Settings > Reporting > Log Database page is correct and the folders exist.
|
|
5.
|
Verify that there is at least one current, active partition (a partition neither disabled nor marked for deletion) listed on the Settings > Reporting > Log Database page.
|
|
2.
|
a.
|
Locate the dbo.wse_etl_config table.
|
b.
|
c.
|
Check the value under max_buffer_size. If the value is negative, revert it to a positive value.
|
1.
|
Make sure you have enabled trend data retention on the Settings > Reporting > Log Database page in TRITON - Web Security.
|
3.
|
3.
|
Right-click a Websense database job, then select Properties.
|
4.
|
Look for the value in the Owner field.
|
2.
|
Locate Websense Log Server service.
|
3.
|
Right-click the service name, then select Properties.
|
4.
|
5.
|
6.
|
Click Start, then close the Properties window.
|
Web Security Log Server Troubleshooting Guide : Incorrect or missing data in Web Security reports
|