Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 9 subscribers
  • Views 5725 views
  • Users 0 members are here
Options
Suggested
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

Slow Installs Server Protection

LRB

Hi, 

 

We are finding the Sophos install are taking very long time to install.

As per the logs below - its checking for the various caching servers and taking up to 1-minutes to check each cache before moving on to the next. In the install below it actually connecting to a cache that would have MUCH slower connection then if it was to download directly from the internet. 

What is going on?  Will there be a full installer soon? This is currently a nightmare to install on AWS servers. 

 

2018-09-14T03:51:39.7380189Z INFO : Analyzing whether to update from Sophos CDN or update cache
2018-09-14T03:51:39.7395034Z WARNING : Warning no ipv6 addresses found for devsophoscache1.company.local:8191.
2018-09-14T03:51:39.7396466Z WARNING : Warning no ipv6 addresses found for prdsophoscache1.company.local:8191.
2018-09-14T03:51:39.7396466Z WARNING : Warning no ipv6 addresses found for ukrsophoscache1.company.local:8191.
2018-09-14T03:51:39.7396466Z WARNING : Warning no ipv6 addresses found for darhvdp01.company.local:8191.
2018-09-14T03:51:39.7396466Z WARNING : Warning no ipv6 addresses found for meldp1.company.local:8191.
2018-09-14T03:51:39.7396466Z INFO : Checking access to update cache: devsophoscache1.company.local:8191
2018-09-14T03:51:39.7396466Z INFO : Updating configured to use: HTTPS
2018-09-14T03:51:39.7396466Z INFO : Update Cache Cert Path folder: C:\\ProgramData\\Sophos\\Certificates\\AutoUpdate\\Cache
2018-09-14T03:52:59.8611444Z INFO : Could not reach cache
2018-09-14T03:52:59.8611444Z INFO : Checking access to update cache: ukrsophoscache1.company.local:8191
2018-09-14T03:52:59.8611444Z INFO : Updating configured to use: HTTPS
2018-09-14T03:52:59.8611444Z INFO : Update Cache Cert Path folder: C:\\ProgramData\\Sophos\\Certificates\\AutoUpdate\\Cache
2018-09-14T03:54:15.8749841Z INFO : Could not reach cache
2018-09-14T03:54:15.8749841Z INFO : Checking access to update cache: prdsophoscache1.company.local:8191
2018-09-14T03:54:15.8749841Z INFO : Updating configured to use: HTTPS
2018-09-14T03:54:15.8749841Z INFO : Update Cache Cert Path folder: C:\\ProgramData\\Sophos\\Certificates\\AutoUpdate\\Cache
2018-09-14T03:55:29.7326244Z INFO : Could not reach cache
2018-09-14T03:55:29.7326244Z INFO : Checking access to update cache: wgtmeldp1.company.local:8191
2018-09-14T03:55:29.7326244Z INFO : Updating configured to use: HTTPS
2018-09-14T03:55:29.7326244Z INFO : Update Cache Cert Path folder: C:\\ProgramData\\Sophos\\Certificates\\AutoUpdate\\Cache
2018-09-14T03:56:43.9183867Z INFO : Could not reach cache
2018-09-14T03:56:43.9183867Z INFO : Checking access to update cache: wgtdarhvdp01.company.local:8191
2018-09-14T03:56:43.9183867Z INFO : Updating configured to use: HTTPS
2018-09-14T03:56:43.9183867Z INFO : Update Cache Cert Path folder: C:\\ProgramData\\Sophos\\Certificates\\AutoUpdate\\Cache
2018-09-14T03:56:44.3246065Z INFO : Successfully connected to cache
2018-09-14T03:56:44.3246065Z INFO : Cache response time: 418ms
2018-09-14T03:56:44.3246065Z INFO : Analysis complete - Using update cache: darhvdp01.company.local:8191
2018-09-14T03:56:44.3246065Z INFO : Updating from cache: wgtdarhvdp01.company.local:8191
2018-09-14T03:56:44.3246065Z INFO : Updating configured to use: HTTPS
2018-09-14T03:56:44.3246065Z INFO : Initial download: attempting to use bulk metadata
2018-09-14T03:56:44.3402345Z INFO : Calling SULDownloader addGlobalFilter...
2018-09-14T03:56:44.3402345Z INFO : Subscription: Base



This thread was automatically locked due to age.
Parents
  • 0

    Hello LRB,

    can't say why it takes 80+ seconds to determine that a cache can't be reached (and why it can't reach them as, if I understand you correctly, at least one of these should provide a faster connection. Or would you prefer that it doesn't use a cache at all?

    After installation when subsequently updating did/does it use the same cache or one of the others it couldn't reach at first?

    Christian

  • 0 in reply to QC

    It should reach some of the other caches servers, but even if not, then it should have downloaded via internet. 

     

    However, the main issue here is the 90secs to check caching servers. What would cause this?

  • 0 in reply to LRB

    Hello LRB,

    what would cause this
    the connection is HTTPS to port 8191. I don't think that the TCP SYN has a timeout or a number of retries that would generally amount to an 80 seconds delay for an unreachable cache. Doesn't look like a "simple" networking error like not reachable (even if no ICMP message is returned). And you said It should reach some of the other caches. My question is - does it? If still only just the one cache that has initially been used can be reached then it's not an Installer issue.
    I'd trace the traffic on port 8191 and the behaviour is still the same then it's easier to obtain the trace than with a new install.

    Christian

Reply
  • 0 in reply to LRB

    Hello LRB,

    what would cause this
    the connection is HTTPS to port 8191. I don't think that the TCP SYN has a timeout or a number of retries that would generally amount to an 80 seconds delay for an unreachable cache. Doesn't look like a "simple" networking error like not reachable (even if no ICMP message is returned). And you said It should reach some of the other caches. My question is - does it? If still only just the one cache that has initially been used can be reached then it's not an Installer issue.
    I'd trace the traffic on port 8191 and the behaviour is still the same then it's easier to obtain the trace than with a new install.

    Christian

Children
No Data
Unfiltered HTML