Tips for Troubleshooting WebPulse Services on a ProxySG or ASG Appliance

book

Article ID: 167150

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

This article provides general information on, and troubleshooting tips for, WebPulse, including the dynamic realtime rating (DRTR) service.

Q: How does a ProxySG or ASG appliance decide which service point to use for WebPulse?
A: Periodically, the ProxySG or ASG appliance polls several service points for their response times. After it decides which is fastest, it uses that service for the next several requests.

Q: What host (DNS name) does WebPulse use?
A: WebPulse performs a DNS lookup of sp.cwfservice.net for SGOS 6.5 and webpulse.es.bluecoat.com for SGOS 6.6. These IP addresses can change, but not often. Ensure the appliance in question returns at least four IP addresses; you can check them by using the command dig or conducting a DNS lookup of either hostname. Periodically, the appliance polls all of the service points for their response times. After it determines which is fastest, it uses that service for the next several requests.

Q: What does the error "Dynamic categorization error: Entity not currently in use" in WebPulse logs mean?
A: The log might display the following error:

"Dynamic categorization error: Entity not currently in use." 0> > 510000:1 ../protocols/cerberian/Cerberian_api.cpp:80

This means that the appliance determined that the WebPulse service is not available. Occasionally, this can occur just after an SGOS upgrade; disable WebPulse temporarily and re-enable it to prevent the error from being logged again.

Q:  How can I determine what IP addresses and DNS names the appliance can see?

A: To determine what addresses are returned for WebFilter or WebPulse health checks, use the following CLI command:
# test dns
Refer to the Command Line Interface Reference for details on the command.