UTM Up2Date 9.708 stable?

Only at 3 customers (works fine), on all other SG's it seems that the Update to 9.708 is retracted ?!

/André

Why do you think it's been retracted?  It's on the site to download.  

I haven't seen anything wrong with it for home use.  The issues that seemed to plague UTM were in the previous version.

Updated my homebox yesterday.

All seems fine except WLAN took ages to come up again. So I checked the logs and it seems, that the new AP firmware failed to install

2021:12:17-20:54:32 fw awed[4627]: [MASTER] access point firmware available: APX120:11.0.016-1 AP15C:9500-wifi-ccd40c7-0df51d6 red20:1 RED15w:1 red60:1 AP100C:9500-wifi-ccd40c7c-0df51d6 AP100X:9500-wifi-ccd40c7-0df51d6 AP50:9500-wifi-88782b0d17-be66136 AP15:9500-wifi-ccd40c7c-0df51d6 AP100:9500-wifi-ccd40c7c-0df51d6 AP10:9500-wifi-88782b0d17-be66136 AP55C:9500-wifi-ccd40c7c-0df51d6 APX320:11.0.016-1 AP30:9500-wifi-88782b0d17-be66136 AP5:1 APX530:11.0.016-1 APX740:11.0.016-1 AP55:9500-wifi-ccd40c7c-0df51d6
2021:12:17-20:54:35 P322316YD9AZCBE kernel: [14970543.787432] [wifi1] FWLOG: [37804497] vap-2 AP PS: AID=4295584 select next response 
2021:12:17-21:00:29 P322316YD9AZCBE aweclient[1191]: Setting led mode to normal_operation
2021:12:17-21:00:29 fw awed[4647]: [MASTER] new connection from 192.168.144.212:59315<30>Dec 17 21:00:29 awed[6489]: [P322316YD9AZCBE] APX120 from 192.168.144.212:59315 identified as P322316YD9AZCBE
2021:12:17-21:00:29 fw awed[6489]: [P322316YD9AZCBE] (Re-)loaded identity and/or configuration
2021:12:17-21:00:29 P322316YD9AZCBE pdog[691]: src/process.c:317/unregister_process: process with name cloudclient is not registered before
2021:12:17-21:00:29 P322316YD9AZCBE aweclient[1191]: Unable to unsubscribe cloudclient from pdog
2021:12:17-21:00:29 P322316YD9AZCBE aweclient[1191]: Cloudclient not found on ubus.
2021:12:17-21:00:31 P322316YD9AZCBE kernel: [14970899.987648] 
2021:12:17-21:00:31 P322316YD9AZCBE kernel: [14970899.987648]  ieee80211_mlme_recv_deauth 1597  mac 18:74:2e:a7:4a:df reason 3
2021:12:17-21:00:31 P322316YD9AZCBE hostapd: ath102: STA 18:74:2e:a7:4a:df IEEE 802.11: disassociated
2021:12:17-21:00:31 P322316YD9AZCBE hostapd: ath102: STA 18:74:2e:a7:4a:df IEEE 802.11: Deauth - client left (code:3)
2021:12:17-21:00:34 fw awed[6489]: [P322316YD9AZCBE] sent firmware /etc/wireless/firmware/APX.uimage to device, releasing connection.
2021:12:17-21:00:34 P322316YD9AZCBE kernel: [14970902.835324] 
2021:12:17-21:00:34 P322316YD9AZCBE kernel: [14970902.835324]  ieee80211_mlme_recv_deauth 1597  mac 4c:34:88:36:8e:4f reason 1
2021:12:17-21:00:34 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: disassociated
2021:12:17-21:00:34 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: Unspecified error (code:1)
2021:12:17-21:00:35 P322316YD9AZCBE aweclient[1191]: Setting led mode to firmware_update
2021:12:17-21:00:37 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: associated
2021:12:17-21:00:37 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f RADIUS: starting accounting session DC1AF00C-0000002B
2021:12:17-21:00:37 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f WPA: pairwise key handshake completed (RSN)
2021:12:17-21:00:37 P322316YD9AZCBE kernel: [14970905.617903] [wifi1] FWLOG: [38175934] RATE: ChainMask 3, peer_mac 8e:4f, phymode 9, ni_flags 0x0203b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
2021:12:17-21:00:37 P322316YD9AZCBE kernel: [14970905.617945] [wifi1] FWLOG: [38175934] RTT_REPORT ( 0x2804, 0x3, 0x479, 0x0, 0x9 )
2021:12:17-21:00:41 P322316YD9AZCBE aweclient[1191]: aweclient.c (216) Starting firmware flashing.
2021:12:17-21:00:53 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: disassociated
2021:12:17-21:00:53 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: Unspecified error (code:1)
2021:12:17-21:00:53 P322316YD9AZCBE kernel: [14970921.495710] 
2021:12:17-21:00:53 P322316YD9AZCBE kernel: [14970921.495710]  ieee80211_mlme_recv_deauth 1597  mac 4c:34:88:36:8e:4f reason 1
2021:12:17-21:00:53 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: AP-STA-REASSOCIATE
2021:12:17-21:00:53 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: associated
2021:12:17-21:00:53 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f RADIUS: starting accounting session DC1AF00C-0000002C
2021:12:17-21:00:53 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f WPA: pairwise key handshake completed (RSN)
2021:12:17-21:00:53 P322316YD9AZCBE kernel: [14970921.609728] [wifi1] FWLOG: [38192494] RATE: ChainMask 3, peer_mac 8e:4f, phymode 9, ni_flags 0x0203b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
2021:12:17-21:00:53 P322316YD9AZCBE kernel: [14970921.609768] [wifi1] FWLOG: [38192494] RTT_REPORT ( 0x2804, 0x3, 0x479, 0x0, 0x9 )
2021:12:17-21:01:09 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: disassociated
2021:12:17-21:01:09 P322316YD9AZCBE kernel: [14970937.776956] 
2021:12:17-21:01:09 P322316YD9AZCBE kernel: [14970937.776956]  ieee80211_mlme_recv_deauth 1597  mac 4c:34:88:36:8e:4f reason 1
2021:12:17-21:01:09 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: Unspecified error (code:1)
2021:12:17-21:01:20 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f IEEE 802.11: associated
2021:12:17-21:01:20 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f RADIUS: starting accounting session DC1AF00C-0000002D
2021:12:17-21:01:20 P322316YD9AZCBE hostapd: ath100: STA 4c:34:88:36:8e:4f WPA: pairwise key handshake completed (RSN)
2021:12:17-21:01:21 P322316YD9AZCBE kernel: [14970949.596332] [wifi1] FWLOG: [38220356] RATE: ChainMask 3, peer_mac 8e:4f, phymode 9, ni_flags 0x0203b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
2021:12:17-21:01:21 P322316YD9AZCBE kernel: [14970949.596374] [wifi1] FWLOG: [38220356] RTT_REPORT ( 0x2804, 0x3, 0x479, 0x0, 0x9 )
2021:12:17-21:01:37 P322316YD9AZCBE kernel: [14970965.588438] [wifi1] FWLOG: [38236882] RATE: ChainMask 3, peer_mac 8e:4f, phymode 10, ni_flags 0x0203b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
2021:12:17-21:01:41 P322316YD9AZCBE /bin/update_image.sh: firmware update failed exitcode 0
2021:12:17-21:01:41 P322316YD9AZCBE aweclient[1191]: Setting led mode to booting
2021:12:17-21:01:41 P322316YD9AZCBE aweclient[1191]: aweclient.c (524) Firmware upgrade finished: quit and reboot.
2021:12:17-21:01:41 P322316YD9AZCBE aweclient[1191]: Closing log...
2021:12:17-21:01:41 P322316YD9AZCBE procd: - shutdown -
2021:12:17-21:01:41 P322316YD9AZCBE procd:

What do you think. Is there a way to check if the AP got the new firmware correctly? Is there a way to force a reinstall of the firmware somehow? (I searched the forum and it seems not possible o.o )

You may have to hard reset the AP then plug it back online to get the firmware to work.  I had to do that when I had an old AP15, but it finally died.

Maybe a recovery can help:

support.sophos.com/.../KB-000039314

This recovery tool would work for all except for my APX120... :/

To clarify, my AP and WLAN are working fine. However I think the new firmware did not get applied correctly and sadly it seems that there is no way to check this. Actually cant believe that…

So yeah, when I am in the mood I will try a reset and see if a new firmware will be pushed…. or maybe just will wait for another update with a new wifi firmware… lazy lol

Same here, after Update to 9.708  Firmware AP 15 and AP 120 getting no update. 

Error Message: 2021:12:20-19:00:36 P32004...... /bin/update_image.sh: firmware update failed exitcode 0

Would be nice to be able to manual update the AP the devices

You can try to unplug the AP, do the hardware reset for it, plug it back in and see if it gets the update.