UTM failing Up2Date as of 9.408-4

Instead of a complete log file, please show us about 50 lines containing the problem.  At first glance, I found a successful savi update.

Cheers - Bob

o yes, the record is quite large, however I seem to get 2-4 failures per day, and those have started to be reported since 9.408-4, where they were either happening and not being reported, or not happening, I'm not sure which, tbh.

This is the best I can do:

----

2016:11:22-05:13:02 gateway audld[6756]: no HA system or cluster node
2016:11:22-05:13:02 gateway audld[6756]: Starting Up2Date Package Downloader
2016:11:22-05:13:03 gateway audld[6756]: patch up2date possible
2016:11:22-05:13:21 gateway audld[6756]: Could not connect to Server 54.214.16.252 (status=500 Internal Server Error).
2016:11:22-05:13:22 gateway audld[6756]: Could not connect to Authentication Server 54.214.16.252 (code=500 500 Internal Server Error).
2016:11:22-05:13:22 gateway audld[6756]: id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
2016:11:22-05:28:02 gateway audld[8565]: no HA system or cluster node
2016:11:22-05:28:02 gateway audld[8565]: Starting Up2Date Package Downloader
2016:11:22-05:28:03 gateway audld[8565]: patch up2date possible
2016:11:22-05:28:31 gateway audld[8565]: id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
2016:11:22-05:43:02 gateway audld[10388]: no HA system or cluster node
2016:11:22-05:43:02 gateway audld[10388]: Starting Up2Date Package Downloader
2016:11:22-05:43:02 gateway audld[10388]: patch up2date possible
2016:11:22-05:43:08 gateway audld[10388]: id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
2016:11:22-05:58:01 gateway audld[12176]: no HA system or cluster node
2016:11:22-05:58:01 gateway audld[12176]: Starting Up2Date Package Downloader
2016:11:22-05:58:02 gateway audld[12176]: patch up2date possible
2016:11:22-05:58:08 gateway audld[12176]: id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
2016:11:22-06:13:02 gateway audld[13987]: no HA system or cluster node
2016:11:22-06:13:02 gateway audld[13987]: Starting Up2Date Package Downloader
2016:11:22-06:13:03 gateway audld[13987]: patch up2date possible
2016:11:22-06:13:13 gateway audld[13987]: >=========================================================================
2016:11:22-06:13:13 gateway audld[13987]: No service resource record found for (_https._tcp.utmu2d.sophos.com): SERVFAIL
2016:11:22-06:13:13 gateway audld[13987]: 
2016:11:22-06:13:13 gateway audld[13987]:  1. Modules::Logging::msg:46() /</sbin/audld.plx>Modules/Logging.pm
2016:11:22-06:13:13 gateway audld[13987]:  2. Modules::Audld::DNSQuery::_get_srv:73() /</sbin/audld.plx>Modules/Audld/DNSQuery.pm
2016:11:22-06:13:13 gateway audld[13987]:  3. Modules::Audld::DNSQuery::get:43() /</sbin/audld.plx>Modules/Audld/DNSQuery.pm
2016:11:22-06:13:13 gateway audld[13987]:  4. main::main:138() audld.pl
2016:11:22-06:13:13 gateway audld[13987]:  5. main::top-level:40() audld.pl
2016:11:22-06:13:13 gateway audld[13987]: <=========================================================================
2016:11:22-06:13:13 gateway audld[13987]: No Authentication Servers found in DNS. Using defaults
2016:11:22-06:13:33 gateway audld[13987]: Could not connect to Server us1.utmu2d.sophos.com (status=500 Can't connect to us1.utmu2d.sophos.com:443).
2016:11:22-06:13:53 gateway audld[13987]: Could not connect to Server sg1.utmu2d.sophos.com (status=500 Can't connect to sg1.utmu2d.sophos.com:443).
2016:11:22-06:14:13 gateway audld[13987]: Could not connect to Server eu1.utmu2d.sophos.com (status=500 Can't connect to eu1.utmu2d.sophos.com:443).
2016:11:22-06:14:33 gateway audld[13987]: Could not connect to Authentication Server us1.utmu2d.sophos.com (code=500 500 Can't connect to us1.utmu2d.sophos.com:443).
2016:11:22-06:14:47 gateway audld[13987]: id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
2016:11:22-06:14:49 gateway audld[13987]: id="3707" severity="info" sys="system" sub="up2date" name="Successfully synchronized fileset" status="success" action="download" package="aptp"
2016:11:22-06:14:50 gateway auisys[14202]: no HA system or cluster node
2016:11:22-06:14:50 gateway auisys[14202]: waiting for db_verify to return (30 seconds max)
2016:11:22-06:14:51 gateway auisys[14202]: not cleaning /var/up2date/sys-install in --nosys mode
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/appctrl43-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/aptp-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/cadata-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/geoip-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/geoipxtipv6-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/ipsbundle-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/man9-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/ohelp9-install'
2016:11:22-06:14:51 gateway auisys[14202]: removing '/var/up2date/savi-install'
2016:11:22-06:14:51 gateway auisys[14202]: Starting Up2Date Package Installer
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <man9> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <appctrl43> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <ohelp9> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <geoipxtipv6> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <cadata> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <geoip> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <ipsbundle> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: No suitable packages of type <savi> found, skipping
2016:11:22-06:14:51 gateway auisys[14202]: Install u2d packages <aptp>
2016:11:22-06:14:51 gateway auisys[14202]: Starting installing up2date packages for type 'aptp'
2016:11:22-06:14:51 gateway auisys[14202]: Installing up2date package: /var/up2date/aptp/u2d-aptp-9.19443.tgz.gpg
2016:11:22-06:14:51 gateway auisys[14202]: Verifying up2date package signature
2016:11:22-06:14:52 gateway auisys[14202]: Unpacking installation instructions
2016:11:22-06:14:52 gateway auisys[14202]: parsing installation instructions
2016:11:22-06:14:52 gateway auisys[14202]: Unpacking up2date package container
2016:11:22-06:14:52 gateway auisys[14202]: Running pre-installation checks
2016:11:22-06:14:52 gateway auisys[14202]: Starting up2date package installation
2016:11:22-06:15:05 gateway auisys[14202]: id="371Z" severity="info" sys="system" sub="up2date" name="Successfully installed Up2Date package" status="success" action="install" package_version="9.19443" package="aptp"
2016:11:22-06:15:05 gateway auisys[14202]: [INFO-306] New Pattern Up2Dates installed
2016:11:22-06:15:06 gateway auisys[14202]: Up2Date Package Installer finished, exiting
2016:11:22-06:15:06 gateway auisys[14202]: id="3716" severity="info" sys="system" sub="up2date" name="Up2Date Package Installer finished, exiting"

----
I've highlighted what/where it seems to fail.

Thanks, Oliver - much easier to see what's happening.

That you fail to reach all three servers at one point is an indication to me that you're having an issue with your ISP.  Make sure you haven't been bitten by the MTU bug.

As root at the command line, what happens withthe following?

/sbin/audld.plx --nosys --trigger --server v8up2date2.astaro.com:443

Cheers - Bob

When I run that command I get:

---

no HA system or cluster node
Starting Up2Date Package Downloader
patch up2date possible
Authenticating ...
Authentication successful!
Starting Up2Date Download
No new packages available, exiting.

---

So it looks like its working.  Now mind you, today my provider suddenly had a weird DNS issue (only certain websites became unreachable), so it is totally possible that it's my ISP. 

Matter of fact, I now tested all of the previously failing servers, and they all work.  I'm suspecting it was my ISP at this point. I'm going to wait 24hrs and see what happens.

Yup, since my ISP has made changes, the problem has gone away completely.

OliverBishop,

I saw your message about up2date failing,

a couple of things I always forget and have to look back at my notes but that hasn't happened

to me for over a year,

It was happening to me on 9.408 and 9.409

Here are my notes after digging forever.

First of all, the update servers are all on amazon 

one server is in usa, one in singapore, one in ireland, so make sure country blocking isn't on for those countries.

second thing from the past that was causing up2date to not work is using opendns, nortondns, comododns google dns etc. on the sophos utm dns forwarder.

DOH, only use nonfiltered dns /preferably or tiny issues that appear and disappear will drive us all nuts.

a lot of isps even rewrite ttl times that cause issues but that's a long shot.

cox 68.105.28.17 and 68.12.16.15 and 68.12.16.30 usually provide mostly unfiltered results, 68.105.28.17 doesn't block stuff except blatant virused servers etc.

google 8.8.8.8 and 8.8.4.4 cause issues that have driven me nuts before, 

I hope you have your issue solved by now,

I hope that helps at least shine a light on where the issue could be in the future.

OliverBishop,

I saw your message about up2date failing,

a couple of things I always forget and have to look back at my notes but that hasn't happened

to me for over a year,

It was happening to me on 9.408 and 9.409

Here are my notes after digging forever.

First of all, the update servers are all on amazon 

one server is in usa, one in singapore, one in ireland, so make sure country blocking isn't on for those countries.

second thing from the past that was causing up2date to not work is using opendns, nortondns, comododns google dns etc. on the sophos utm dns forwarder.

DOH, only use nonfiltered dns /preferably or tiny issues that appear and disappear will drive us all nuts.

a lot of isps even rewrite ttl times that cause issues but that's a long shot.

cox 68.105.28.17 and 68.12.16.15 and 68.12.16.30 usually provide mostly unfiltered results, 68.105.28.17 doesn't block stuff except blatant virused servers etc.

google 8.8.8.8 and 8.8.4.4 cause issues that have driven me nuts before, 

I hope you have your issue solved by now,

I hope that helps at least shine a light on where the issue could be in the future.