I'm actually facing the problem that one UTM 120 up2date does not work. Neither firmware nor patterns. Here's the log:
2014:06:19-10:19:31 device-12 audld[7008]: Starting Up2Date Package Downloader
2014:06:19-10:19:31 device-12 audld[7008]: patch up2date possible
2014:06:19-10:19:34 device-12 audld[7008]: Could not connect to Authentication Server 184.72.238.199:443 (code=500 500 proxy connect failed: proxy connect to my-central-ip:8080 failed: Connection refused).
2014:06:19-10:19:34 device-12 audld[7008]: Could not connect to Authentication Server 184.72.238.199:443 (code=500 500 proxy connect failed: proxy connect to my-central-ip:8080 failed: Connection refused).
2014:06:19-10:19:34 device-12 audld[7008]: Could not connect to Authentication Server 175.41.132.12:443 (code=500 500 proxy connect failed: proxy connect to my-central-ip:8080 failed: Connection refused).
2014:06:19-10:19:35 device-12 audld[7008]: Could not connect to Authentication Server 175.41.132.12:443 (code=500 500 proxy connect failed: proxy connect to my-central-ip:8080 failed: Connection refused).
2014:06:19-10:19:35 device-12 audld[7008]: Could not connect to Authentication Server 79.125.21.244:443 (code=500 500 proxy connect failed: proxy connect to my-central-ip:8080 failed: Connection refused).
2014:06:19-10:19:35 device-12 audld[7008]: Could not connect to Authentication Server 79.125.21.244:443 (code=500 500 proxy connect failed: proxy connect to my-central-ip:8080 failed: Connection refused).
2014:06:19-10:19:35 device-12 audld[7008]: >=========================================================================
2014:06:19-10:19:35 device-12 audld[7008]: All 6 Authentication Servers failed
2014:06:19-10:19:35 device-12 audld[7008]: '175.41.132.12:443' Code: '500'
2014:06:19-10:19:35 device-12 audld[7008]: '184.72.238.199:443' Code: '500'
2014:06:19-10:19:35 device-12 audld[7008]: '79.125.21.244:443' Code: '500'
2014:06:19-10:19:35 device-12 audld[7008]:
2014:06:19-10:19:35 device-12 audld[7008]: 1. Modules::Trad_Get_Filelist::contact:1605() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: 2. main::authenticate:616() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: 3. main::run:413() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: 4. main::top-level:27() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: [CRIT-310] Up2Date prefetch failed
2014:06:19-10:19:35 device-12 audld[7008]: |=========================================================================
2014:06:19-10:19:35 device-12 audld[7008]: id="3703" severity="error" sys="system" sub="up2date" name="Authentication failed, no valid answer from Authentication Servers"
2014:06:19-10:19:35 device-12 audld[7008]:
2014:06:19-10:19:35 device-12 audld[7008]: 1. main::alf:883() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: 2. main::authenticate:620() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: 3. main::run:413() audld.pl
2014:06:19-10:19:35 device-12 audld[7008]: 4. main::top-level:27() audld.pl
All devices were manually updated to V 9.2. All other devices' up2date is working. I saw that in licensing portal the device's S/N differed from the one the device itself shows but same is with some other devices (which I upgraded from rev.4 to rev.5)
Last I did: manually download all newer firmware files from ftp and upgraded via auisys.plx (hoping that would fix the error which it doesn't).
Also this is the only device where "Up2Date -> Advanced -> Parent Proxy" is greyed out. On the SUM Cache is disabled, too.
I hope someone can give me a hint on how to get up2date work again without reinstalling the device.
Cheers,
LoD
This thread was automatically locked due to age.