Proxy stops passing traffic, Client Workers (CWs) get maxed out and also SmartFilter content filter database is in use
All traffic through the Proxy halts and the client workers rise to the maximum possible on the Proxy.
Smartfilter is the Content Filter Database in use and Content Filter Memory Allocation is set to Normal
You are running an SGOS version below 5.4.3.*
Observing the content filter download status page URL https://<IP_Address_of_SG>:8082/ContentFilter/Status gives output similar to the following:
However, it can be seen in the above output that the database is larger than this setting:
Download size: 365737920
You may also see High CPU when this problem occurs. If so the majority of CPU consumption will be in HTTP policy Evaluation.
Upgrade to SGOS 188.8.131.52 or above and set the Content Filter Memory Allocation setting to HIGH
This can be done using the Management GUI:
Configuration > Content Filtering > General
If you are already on 184.108.40.206 then after setting the memory allocation to HIGH you may have to reboot the proxy in order for traffic to start flowing correctly again.
The amount of memory it is possible to allocate by each setting varies in accordance with the following table:
However, this setting is only a ceiling so the high setting won't result in the consumption of more memory than necessary for the database.
On a Proxy with less than 2GB of memory the current size of the Smartfilter Database is too large to fit into memory. Hence, you should consider upgrading your proxy, or if it is capable of running SGOS 5 upgrade it to SGOS 5.4.3.
5.4.3 allows better paging of the database to disk, but if this becomes necessary there is still the possibility of a performance degradation as a result.
Rate this Page
Please take a moment to complete this form to help us better serve you.