DRTR Service Failing on Edge Proxy Even After A Reboot
Article ID: 243381
Updated On:
Products
Issue/Introduction
Health check drtr.rating_service keeps constantly failing and you're getting warning message on an ASG.
It can be either one drtr server communication errors or all:
Enabled OK for some IPs UP
IP address: 168.149.132.81 Enabled Check failed DOWN
Last status: A communication error has occurred.
Environment
This is potential bugID#SG-26497, due to workaround this was never fixed.
Cause
This is potential bug, where the proxy sends request on port 80 and receives no response from upstream host.
To verify this, please start a pcap on proxy with failing DRTR server IP address and then go to Configuration -> Health checks -> General and perform drtr service health check to force the connection.
You can verify the pcap and port used.
Resolution
It is required to run below steps via CLI:
#(config) content-filter
#(config content-filter) bluecoat
#(config bluecoat) service disable
#(config bluecoat) service service-name webpulse.es.bluecoat.com
#(config bluecoat) service port secure 443
#(config bluecoat) service enable
Unfortunately sometimes when the service is failing it is difficult to disable. You can try this if above steps fails with error:
Warning: WebPulse service or its health check is in use by policy
% WebPulse service could not be disabled
#(config)health-check
#(config health-check)edit drtr.rating_service
#(config drtr.rating_service)threshold sick 10800
It might be required to reboot device after these steps to start all the proxy processes once again
This way proxy should reach out to drtr server on correct 443 port:
Attachments
Feedback
