The WEBFILTER_REQUEST_NOT_CHECKED message is reported into the system message file whenever the webfilter (integrated web filtering) process failed to check a web request. This article documents an approach to troubleshoot this problem.
Integrated web filtering is currently only supported on J-Series and SRX devices.
The problem related to this syslog message is described in the following sections:
The WEBFILTER_REQUEST_NOT_CHECKED message is logged each time the web filter process fails to check a web request.
When the WEBFILTER_REQUEST_NOT_CHECKED event occurs, a message similar to the following is reported:
WEBFILTER_REQUEST_NOT_CHECKED: Error encountered: server down, failed to check request www.google.com
WEBFILTER_REQUEST_NOT_CHECKED: Error encountered: server down, failed to check request wonderwall.msn.com
The message includes the server URL that was not checked.
The cause of the message can be a failure to communicate with the SurfControl server, a temporary lack of system memory or an internal software error.
The failure to communicate with the SurfControl server may be due to issues with the SurfControl server itself, network communication issues or internal issues with the router.
The lack of system memory can be a temporary issue due to usage or can be due to hardware memory failure.
Examine the following output to help determine the cause of this message:
show log messages
show security utm web-filtering status
Look for any related events that occurred at or just before the WEBFILTER_REQUEST_NOT_CHECKED message. Messages showing memory issues or memory hardware failures indicate that the WEBFILTER_REQUEST_NOT_CHECKED message is likely due to hardware failure.
If there are messages indicating memory issues but no hardware failure indications, determine the frequency of the messages to see if they are due to a chronic lack of memory.
If the WEBFILTER_REQUEST_NOT_CHECKED messages occur immediately following or at the same time as messages like the following, then the WEBFILTER_REQUEST_NOT_CHECKED messages are likely due to internal software issues.:
WEBFILTER_SERVER_CONNECTED: Successfully connected to webfilter server uk1i.SurfCPA.com
If none of the above situations apply, the messages are likely due to SurfControl server or network communications issues.
Perform these steps:
- If the messages are due to a hardware failure, open a technical support case with a technical support representative to resolve the hardware failure.
- During a maintenance window, as it will impact transit traffic, try restarting the utmd process with the command: restart utmd. For more information on restarting a process, refer to Restart a Junos Software Process.
- If the messages return after restarting, open a case with your technical support representative to investigate the issue further.
Perform the following steps to resolve issues with the SurfControl server or network communications:
- Ensure that the SurfControl server is up and operational.
- Ping the server from the router to ensure that the router can reach the server.
- Examine logs on the server to ensure that it is not recording errors when receiving requests from the router.