UTM 9 Firmware 9.406-3 "Last check" never.

Please insert pictures of the three tabs in 'Management >> Up2Date'.

Cheers - Bob

Bob,

I restored the backup to 9.405-5 and that fixed it but after a few update checks,  it stopped updating again. 

the log;

Could not connect to Authentication Server us1.utmu2d.sophos.com (code=500 500 Can't connect to us1.utmu2d.sophos.com:443).

Could not connect to Authentication Server sg1.utmu2d.sophos.com (code=500 500 Can't connect to sg1.utmu2d.sophos.com:443).

The configuration backups made on the UTM are marked with the version because you can't restore a version 9.47 backup to firmware version 9.405.  You restored a backup made when your UTM was at firmware level 9.405.

The error in your log is interesting, and the inability to reach that server is your issue.  Let's first make sure there's not a firewall rule blocking that (unlikely).  Go to the UTM command line and try to ping sg1.utmu2d.sophos.com and then start the Firewall Live Log.

If the ping executes and there are no blocks in the Live Log, then it's a problem with that server.  In that case, as root at the command line:

audld.plx --server v8up2date2.astaro.com:443

What was the result of those commands?  Does the "Never" still appear?  Confirm that the log doesn't show the code=500 error.

Cheers - Bob

I am getting access denied when trying to login on ssh Putty.  I turned on Shell Access and created a ps.

I figured it out what cause the Up2date issue.  I didn't have a network device in "Network Services" " DNS" "Global" tab list.

is it normal that sometimes it fail to connect?

2016:10:12-08:10:17 Could not connect to Server us1.utmu2d.sophos.com (status=500 Internal Server Error).

2016:10:12-08:10:36 id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"

Thanks again.

If you haven't created an RSA key with puttygen and configured key access in WebAdmin, then you will need to login first as loginuser and then su - to login as root.

Cheers - Bob

Hello all,

I have the same issue. My UTM Home HA cluster with release 9.407-3 doesn't get updates. Here is the Up2Date log:

2016:11:07-20:18:01 node-2 audld[12593]: running on HA master system or cluster node
2016:11:07-20:18:01 node-2 audld[12593]: Starting Up2Date Package Downloader
2016:11:07-20:18:06 node-2 audld[12593]: patch up2date possible
2016:11:07-20:18:06 node-2 audld[12593]: Using static update server list in HA mode
2016:11:07-20:18:41 node-2 audld[12593]: Could not connect to Server us1.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2016:11:07-20:19:16 node-2 audld[12593]: Could not connect to Server sg1.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2016:11:07-20:19:51 node-2 audld[12593]: Could not connect to Server eu1.utmu2d.sophos.com (status=500 proxy connect failed: alarm).
2016:11:07-20:20:31 node-2 audld[12593]: Could not connect to Authentication Server us1.utmu2d.sophos.com (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
2016:11:07-20:21:11 node-2 audld[12593]: Could not connect to Authentication Server sg1.utmu2d.sophos.com (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
2016:11:07-20:21:51 node-2 audld[12593]: Could not connect to Authentication Server eu1.utmu2d.sophos.com (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
2016:11:07-20:21:51 node-2 audld[12593]: >=========================================================================
2016:11:07-20:21:51 node-2 audld[12593]: All 3 Authentication Servers failed
2016:11:07-20:21:51 node-2 audld[12593]:
2016:11:07-20:21:51 node-2 audld[12593]:  1. Modules::Logging::msg:46() /</sbin/audld.plx>Modules/Logging.pm
2016:11:07-20:21:51 node-2 audld[12593]:  2. Modules::Audld::Authentication::_handle_failure:235() /</sbin/audld.plx>Modules/Audld/Authentication.pm
2016:11:07-20:21:51 node-2 audld[12593]:  3. Modules::Audld::Authentication::start:66() /</sbin/audld.plx>Modules/Audld/Authentication.pm
2016:11:07-20:21:51 node-2 audld[12593]:  4. main::main:174() audld.pl
2016:11:07-20:21:51 node-2 audld[12593]:  5. main::top-level:40() audld.pl
2016:11:07-20:21:51 node-2 audld[12593]: |=========================================================================
2016:11:07-20:21:51 node-2 audld[12593]: id="3703" severity="error" sys="system" sub="up2date" name="Authentication failed, no valid answer from Authentication Servers"
2016:11:07-20:21:51 node-2 audld[12593]:
2016:11:07-20:21:51 node-2 audld[12593]:  1. Modules::Logging::alf:100() /</sbin/audld.plx>Modules/Logging.pm
2016:11:07-20:21:51 node-2 audld[12593]:  2. Modules::Audld::Authentication::start:70() /</sbin/audld.plx>Modules/Audld/Authentication.pm
2016:11:07-20:21:51 node-2 audld[12593]:  3. main::main:174() audld.pl
2016:11:07-20:21:51 node-2 audld[12593]:  4. main::top-level:40() audld.pl

Ping to us1/sg1/eu1.utmu2d.sophos.com is working:

PING us1.utmu2d.sophos.com (54.214.16.252) 56(84) bytes of data.
64 bytes from ec2-54-214-16-252.us-west-2.compute.amazonaws.com (54.214.16.252): icmp_seq=1 ttl=35 time=212 ms
64 bytes from ec2-54-214-16-252.us-west-2.compute.amazonaws.com (54.214.16.252): icmp_seq=2 ttl=35 time=207 ms
64 bytes from ec2-54-214-16-252.us-west-2.compute.amazonaws.com (54.214.16.252): icmp_seq=3 ttl=35 time=205 ms
64 bytes from ec2-54-214-16-252.us-west-2.compute.amazonaws.com (54.214.16.252): icmp_seq=4 ttl=35 time=203 ms
64 bytes from ec2-54-214-16-252.us-west-2.compute.amazonaws.com (54.214.16.252): icmp_seq=5 ttl=35 time=211 ms

PING sg1.utmu2d.sophos.com (175.41.132.12) 56(84) bytes of data.
64 bytes from v8up2date3.astaro.com (175.41.132.12): icmp_seq=1 ttl=52 time=381 ms
64 bytes from v8up2date3.astaro.com (175.41.132.12): icmp_seq=2 ttl=52 time=380 ms
64 bytes from v8up2date3.astaro.com (175.41.132.12): icmp_seq=3 ttl=52 time=381 ms
64 bytes from v8up2date3.astaro.com (175.41.132.12): icmp_seq=4 ttl=52 time=380 ms
64 bytes from v8up2date3.astaro.com (175.41.132.12): icmp_seq=5 ttl=52 time=380 ms

PING eu1.utmu2d.sophos.com (79.125.21.244) 56(84) bytes of data.
64 bytes from v8up2date1.astaro.com (79.125.21.244): icmp_seq=1 ttl=49 time=48.1 ms
64 bytes from v8up2date1.astaro.com (79.125.21.244): icmp_seq=2 ttl=49 time=47.6 ms
64 bytes from v8up2date1.astaro.com (79.125.21.244): icmp_seq=3 ttl=49 time=47.6 ms
64 bytes from v8up2date1.astaro.com (79.125.21.244): icmp_seq=4 ttl=49 time=47.3 ms
64 bytes from v8up2date1.astaro.com (79.125.21.244): icmp_seq=5 ttl=49 time=47.4 ms

And audld.plx to these servers doesn't work. Here is an example:

audld.plx --server v8up2date3.astaro.com:443
running on HA master system or cluster node
Starting Up2Date Package Downloader
patch up2date possible
Could not connect to Server v8up2date3.astaro.com (status=500 proxy connect failed: alarm).
Authenticating ...
Could not connect to Authentication Server v8up2date3.astaro.com (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
All 1 Authentication Servers failed
Authentication failed, no valid answer from Authentication Servers

How can I fix this issue?

As root, run:

grep '_Ip' /etc/up2date/servers.sorted.rpmsave

Replace v8up2date3.astaro.com in the command above with one of those IPs.  Did any IP work?

Cheers - Bob

When runnning grep '_Ip' /etc/up2date/servers.sorted.rpmsave I get the following output:

grep: /etc/up2date/servers.sorted.rpmsave: No such file or Directory

Doing ls -lh on /etc/up2date:

total 52K
-rw-r--r-- 1 root root    6 Oct 10 02:27 global_pattern_revision
-rw-r--r-- 1 root root  15K Jan 18  2016 progress.tmpl
-rw-r--r-- 1 root root  113 Oct 10 03:05 proxy.conf
-rw-r--r-- 1 root root  180 Jan 18  2016 proxy.conf-default
-rw-r--r-- 1 root root 1018 Jan 18  2016 srvrstrn.ph
-rw-r--r-- 1 root root   10 Sep 27 14:48 system_version
-rw-r--r-- 1 root root 3.8K Oct 10 03:05 up2date.conf
-rw-r--r-- 1 root root 4.1K Jan 18  2016 up2date.conf-default
-rw-r--r-- 1 root root  738 Oct 10 03:05 up2date_status

I just did:

utm:/home # grep '_Ip' /etc/up2date/servers.sorted.rpmsave
            'Fallback_Ip' => '79.125.21.244'
            'Fallback_Ip' => '175.41.132.12'
            'Fallback_Ip' => '184.72.238.199'
utm:/home #

Cheers - Bob

As you can see in my last post there's no such a file. Should I create it? What's in this file?

Trying audld.plx with the IP instead of the FQDN doesn't work:

audld.plx --server 79.125.21.244:443
running on HA master system or cluster node
Starting Up2Date Package Downloader
patch up2date possible
Could not connect to Server 79.125.21.244 (status=500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
Authenticating ...
Could not connect to Authentication Server 79.125.21.244 (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
All 1 Authentication Servers failed
Authentication failed, no valid answer from Authentication Servers

audld.plx --server 175.41.132.12:443
running on HA master system or cluster node
Starting Up2Date Package Downloader
patch up2date possible
Could not connect to Server 175.41.132.12 (status=500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
Authenticating ...
Could not connect to Authentication Server 175.41.132.12 (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
All 1 Authentication Servers failed
Authentication failed, no valid answer from Authentication Servers

audld.plx --server 184.72.238.199:443
running on HA master system or cluster node
Starting Up2Date Package Downloader
patch up2date possible
Could not connect to Server 184.72.238.199 (status=500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
Authenticating ...
Could not connect to Authentication Server 184.72.238.199 (code=500 500 proxy connect failed: PROXY ERROR HEADER, could be non-SSL URL:).
All 1 Authentication Servers failed
Authentication failed, no valid answer from Authentication Servers

Because of "status=500 proxy connect failed: PROXY ERROR HEADER" I added the RegEx "^https?://[A-Za-z0-9.-]*\.utmu2d\.sophos\.com/" and "^https?://[A-Za-z0-9.-]*\.astaro\.com/" to Web Protection | Filtering Options | Exceptions | Sophos Services for bypassing some of the proxy checks, i. e. SSL intercept. And I added all network addresses of the UTM to the allowed networks. But this doesn't solve the issue.