Technical Library | Support

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 > More than 100 files in the Log Server cache directory
More than 100 files in the Log Server cache directory
Web Security Help | Web Security Solutions | Version 7.8.x
Normally, Log Server ODBC cache files or BCP files are moved to the Log Database at a steady rate. If temporary files are accumulating on the Log Server machine, current Internet usage information is not being sent to the Log Database.
Log Server may be unable to process temporary files if:
*
The Log Database is not running, the connection to the Microsoft SQL Server machine is down, or the database is busy. See Log Database is not available.
*
The Log Database is not installed properly or is the wrong version. See Log Database was not created.
*
The ETL job has stopped running and the incoming buffer is full.
*
The Log Database is out of allocated disk space. See Log Server is not recording data in the Log Database.
*
The database creation path is invalid.
*
There is no current active partition.
*
There is a problem with BCP insertion.
*
There is a problem with the size of tempdb.
To troubleshoot the problem:
*
Make sure Microsoft SQL Server is running (see Log Database is not available), and that no other processes that use significant resources, such as a full backup or antivirus scan, are running.
Also check the disk IO to verify that the machine is able to handle a fast insertion rate into the database.
*
Verify that you are using a certified version of Microsoft SQL Server:
*
SQL Server 2008 SP3 (or the latest service pack from Microsoft)
*
SQL Server 2008 R2 SP2 (or the latest service pack from Microsoft)
*
SQL Server 2012 SP1 (or the latest service pack from Microsoft)
*
For very small networks and evaluation environments, SQL Server 2008 R2 Express SP 2 (packaged in the TRITON Unified Installer).
*
Use SQL Server Management Studio to verify that the ETL job is running.
If you are using SQL Server Enterprise or Standard, and the ETL job is not running, make sure the SQL Server Agent service is running on the machine.
If SQL Server Agent is running:
*
Expand the catalog database (wslogdb70) and verify that there are records in the INCOMINGBUFFER. If the INCOMINGBUFFER is full, Log Server cannot add additional records.
*
If records exist in the INCOMINGBUFFER table:
*
Locate the wse_etl_config table.
*
Right-click, then select Open Table.
*
Change the value for max_buffer_size to 40000.
*
Use SQL Server Management Studio to verify that the Auto Growth option is enabled for the catalog database.
*
Go to the Settings > Reporting > Log Database page in the Web Security manager and verify that:
*
The File Path entries under Partition Management are valid.
*
There is at least one active partition listed under Available Partitions.
*
If Log Server has been configured to use BCP insertion, but BCP files are not being processed, change the insertion method to ODBC and see if new cache files are processed:
1.
Go to the Settings > Reporting > Log Server page in the Web Security manager.
2.
Expand the Log Record Creation section.
3.
Select the ODBC (Open Database Connectivity) radio button.
4.
Click OK to cache your changes, then click Save and Deploy to implement them.
By default, ODBC cache files are created in the C:\Program Files or Program Files (x86)\Websense\Web Security\bin\Cache directory.
*
The log (ldf) file for the database tempdb may be full. Restart the Microsoft SQL Server (MSSQLSERVER) services to clear the tempdb database.

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 > More than 100 files in the Log Server cache directory
Copyright 2016 Forcepoint LLC. All rights reserved.