Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed To Download Update / Could not contact primary server

This morning, the Sophos icon displayed an X in the center of the shield but wasn't grayed out, and the first entry on the menu was a grayed out "Failed To Download Update".  Choosing "Update Now" causes the Sophos AutoUpdate Status window to open, briefly display the "downloading" bar, then end with "Could not contact primary server" and "Authentication Error" followed by the date and time.  Looking into the console, I see that early this morning there were a number of messages regarding Sophos, almost all of them along the following lines: "3/19/15 7:28:22.685 AM SophosSXLD[137]: [SMESXLInterface.m:437] no DNS addresses found", and similar messages appear to go back to at least March 13.

Is there a problem with the Sophos server, and if so what's the prognosis?  Or is it something with my computer, and if so what should I do?  I'm running Sophos Home Edition 9.2.4 (Threat detection engine 3.58.1, Threat data 5.12) on a Mac running OSX 10.9.5.

:1020416


This thread was automatically locked due to age.
Parents
  • Same problem started for me as well. Saw it on Sunday, then there was a successful update late Sunday night and several during the day today (using the default 4 hour update check interval). Now, I noticed that updating has begun failing again, as shown by these entries in the Sophos log:

    com.sophos.autoupdate: Updating catalogue information at 21:47:27 27 July 2015
    com.sophos.autoupdate: Catalogue updated at 21:47:28 27 July 2015
    com.sophos.autoupdate: Download started at 21:47:28 27 July 2015
    com.sophos.autoupdate: Error: Failed to read remote metadata at 21:50:06 27 July 2015
    com.sophos.autoupdate: Error: Could not contact primary server at 21:50 on 27 July 2015
    com.sophos.autoupdate: URL is invalid
    com.sophos.autoupdate:
    com.sophos.autoupdate: Proceed with manually triggered update from Sophos at 00:03:53 28 July 2015
    com.sophos.autoupdate: Updating catalogue information at 00:03:54 28 July 2015
    com.sophos.autoupdate: Catalogue updated at 00:07:23 28 July 2015
    com.sophos.autoupdate: Download started at 00:07:23 28 July 2015
    com.sophos.autoupdate: Error: Failed to read remote metadata at 00:10:02 28 July 2015
    com.sophos.autoupdate: Error: Could not contact primary server at 00:10 on 28 July 2015
    com.sophos.autoupdate: URL is invalid
    com.sophos.autoupdate:

    :1021391
Reply
  • Same problem started for me as well. Saw it on Sunday, then there was a successful update late Sunday night and several during the day today (using the default 4 hour update check interval). Now, I noticed that updating has begun failing again, as shown by these entries in the Sophos log:

    com.sophos.autoupdate: Updating catalogue information at 21:47:27 27 July 2015
    com.sophos.autoupdate: Catalogue updated at 21:47:28 27 July 2015
    com.sophos.autoupdate: Download started at 21:47:28 27 July 2015
    com.sophos.autoupdate: Error: Failed to read remote metadata at 21:50:06 27 July 2015
    com.sophos.autoupdate: Error: Could not contact primary server at 21:50 on 27 July 2015
    com.sophos.autoupdate: URL is invalid
    com.sophos.autoupdate:
    com.sophos.autoupdate: Proceed with manually triggered update from Sophos at 00:03:53 28 July 2015
    com.sophos.autoupdate: Updating catalogue information at 00:03:54 28 July 2015
    com.sophos.autoupdate: Catalogue updated at 00:07:23 28 July 2015
    com.sophos.autoupdate: Download started at 00:07:23 28 July 2015
    com.sophos.autoupdate: Error: Failed to read remote metadata at 00:10:02 28 July 2015
    com.sophos.autoupdate: Error: Could not contact primary server at 00:10 on 28 July 2015
    com.sophos.autoupdate: URL is invalid
    com.sophos.autoupdate:

    :1021391
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?