WSA PROBLEM： The updater has been unable to communicate with the update server for at least 1h.

[cunfa xu]

Hey, gay

                    I haved meet a problem today. I received many error message on WSA S380.

===============================================================================================================

Subject: Warning <Updater> Abcwsa1.efg.com: The updater has been unable to communicate with the update s...

The Warning message is:

The updater has been unable to communicate with the update server for at least 1h.

Last message occurred 12 times between Fri Mar  4 10:40:56 2016 and Fri Mar  4 11:31:27 2016.

Product: Cisco S380 Web Security Appliance

Model: S380

Version: 8.5.2-027

Serial Number: E4AA5DAD17C8-FCH1938V381

Timestamp: 04 Mar 2016 11:31:49 +0800

To learn more about this alert, please visit the Cisco support Web site.

http://www.cisco.com/web/ironport/index.html

Additional assistance is available through a Support Request. From Cisco S380, go to the "Help and Support" menu in the upper right corner of the page and select "Open a Support Case".

=============================================================================================================================================

                                    My Feature key is normal.   I haven't nothing change on WSA.  WHy? Who  can help me ?

[Tao Yang · Accepted solution]

To troubleshoot the update issue, you could enable debug logging level of WSA update log and then try to get the detailed error message. If the update of WSA is working properly now, it may indicate it was due to a network connectivity issue.

[Tim Glen]

cunfa,

Once every several months I have this problem as well.  I experienced this issue on March 1, 2016 around 5 pm EST.  

Typically within a few hours the WSA is able to connect to the update server without me doing anything.   I've always assumed it was an issue with the update server as I still can browse the my commonly viewed web sites. 

Hope this helps

[Robert Sherwin]

We did experience a Data Center issue on March 1, 2016 at the time indicated.  This was resolved internally and updater servers restored to working order.

RCA attached.

-Robert