Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 9858 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

No Pattern Update since Update to Firmware 9.506-2

BMattes

Hello all,

since Firmware Update to V. 9.506-2, my two SG 115 Appliances do not make Pattern Updates. The WabAdmin says "Your patterns are up to date" but there is Pattern Version 112414 installed. On my other Appliances I have Firmware V. 9.506-2 and Pattern Version 138485.

The Up2Date Logfile says:

2018:01:26-07:09:01 gate audld[13938]: no HA system or cluster node
2018:01:26-07:09:01 gate audld[13938]: Starting Up2Date Package Downloader
2018:01:26-07:09:03 gate audld[13938]: patch up2date possible
2018:01:26-07:09:03 gate audld[13938]: Using static update server list in HA mode
2018:01:26-07:09:38 gate audld[13938]: Could not connect to Server us1.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2018:01:26-07:10:13 gate audld[13938]: Could not connect to Server us2.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2018:01:26-07:10:48 gate audld[13938]: Could not connect to Server sg1.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2018:01:26-07:11:23 gate audld[13938]: Could not connect to Server eu1.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2018:01:26-07:12:08 gate audld[13938]: Could not connect to Authentication Server us1.utmu2d.sophos.com (code=500 500 proxy connect failed: alarm).
2018:01:26-07:12:53 gate audld[13938]: Could not connect to Authentication Server us2.utmu2d.sophos.com (code=500 500 proxy connect failed: alarm).
 

I hope someone can help me - Thank you all.

 



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

    Looks like DNS problem?!? Can you ping one of these addresses from UTM (us1.utmu2d.sophos.com...)?

    Can you ping other addresses? Can you ping IP 8.8.8.8 (Google DNS-Server) -> If this is working but ping on domain names is not working you sure have a DNS problem?

     

    Check your DNS-Forwarders on UTM - insert DNS-Server IP 8.8.8.8 as your DNS-Forwarder -> working now?

     

    Is there any other firewall/router before your UTM?

     

    regards

Reply
  • 0

    Looks like DNS problem?!? Can you ping one of these addresses from UTM (us1.utmu2d.sophos.com...)?

    Can you ping other addresses? Can you ping IP 8.8.8.8 (Google DNS-Server) -> If this is working but ping on domain names is not working you sure have a DNS problem?

     

    Check your DNS-Forwarders on UTM - insert DNS-Server IP 8.8.8.8 as your DNS-Forwarder -> working now?

     

    Is there any other firewall/router before your UTM?

     

    regards

Children
  • 0 in reply to SWeissflog

    Hello SWeissflog,

    THX for reply but DNS is not the Problem. I tested NS-Lookup, Traceroute and Ping before I posted my Problem here.

    See Console output

    gate:/home/login # nslookup us1.utm2d.sophos.com
    Server:         127.0.0.1
    Address:        127.0.0.1#53

    Non-authoritative answer:
    Name:   us1.utm2d.sophos.com
    Address: 62.138.238.45
    Name:   us1.utm2d.sophos.com
    Address: 62.138.239.45

    gate:/home/login # ping us1.utm2d.sophos.com
    PING us1.utm2d.sophos.com (62.138.239.45) 56(84) bytes of data.
    64 bytes from 62.138.239.45: icmp_seq=1 ttl=250 time=27.9 ms
    64 bytes from 62.138.239.45: icmp_seq=2 ttl=250 time=26.7 ms
    64 bytes from 62.138.239.45: icmp_seq=3 ttl=250 time=26.2 ms
    64 bytes from 62.138.239.45: icmp_seq=4 ttl=250 time=26.7 ms
    64 bytes from 62.138.239.45: icmp_seq=5 ttl=250 time=26.7 ms
    64 bytes from 62.138.239.45: icmp_seq=6 ttl=250 time=26.5 ms
    64 bytes from 62.138.239.45: icmp_seq=7 ttl=250 time=26.9 ms
    64 bytes from 62.138.239.45: icmp_seq=8 ttl=250 time=27.5 ms
    64 bytes from 62.138.239.45: icmp_seq=9 ttl=250 time=26.8 ms
    64 bytes from 62.138.239.45: icmp_seq=10 ttl=250 time=27.2 ms
    64 bytes from 62.138.239.45: icmp_seq=11 ttl=250 time=26.9 ms

  • 0 in reply to BMattes

    I think SWeissflog has it right - from the command line as root do:

    cc dns_flush_cache

    Now, ping us1.utm2d.sophos.com and you'll see that the IP has changed.

    You might want to consider the model in DNS best practice.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hello Bob,

    thank you for reply and the Tips for DNS configuration.

    The changes I made were not successful and the problem is still existing.

     

    I will try to reinstall th SG and restore config from Backup.

     

    Greez, Bernhard

  • 0 in reply to BMattes

    Sometimes an Up2Date "breaks" a configuration, Bernhard.  Before re-installing, try just doing a restore from just before the last time you applied Up2Dates.  Any luck with that?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hello Bob,

    thank you for reply!!!

    I don't know what is going wrong but no solution I tried was successful.

    We have 3 HA systems (210,320,430) and 4 single systems (115,125). All systems have V. 9.506-2 but only the two SG115 do not update patterns since firmwareupgrade.

    However, I find no similarities on the two systems...

    I think the only solution is to reinstall the systems.

     

    Regards, Bernhard

Unfiltered HTML