AP30 unstable since 9.401

RE: AP30 unstable since 9.401

BarryG — Thu, 16 Feb 2017 13:35:24 GMT

FYIs, it turned out to be a detached heatsink on my AP30.

RE: AP30 unstable since 9.401

wk — Fri, 02 Dec 2016 05:56:16 GMT

I can also add my box. I have a second AP10 in a remote part of my house, that had not been used for some month.

The Ap10 does not even work for a short time. I reflashed it several times successfull, but it only shows as pending and when I accept it I have an endless loop. The logs show the same lines you all mentioned.

It took me some time to come accross your post because it is not an AP30, but the symtoms are the same.

RE: AP30 unstable since 9.401

JonZgoda — Tue, 29 Nov 2016 11:27:50 GMT

Any news on when this fix is getting released?

I'm on 9.408-4, and seem to be experiencing this on some of my AP30s.

Any news would be appreciated, thanks.

RE: AP30 unstable since 9.401

BarryG — Wed, 02 Nov 2016 12:52:53 GMT

[quote user="JamieBah1"]

Has anyone else noticed this in the log file?

Use of uninitialized value in concatenation (.) or string at awed_ng.pl line 347

[/quote]

Hi, I've seen that but I'm assuming its a red herring as it appears separately from the crashes as well, iirc.

RE: AP30 unstable since 9.401

BarryG — Wed, 02 Nov 2016 12:51:55 GMT

BTW, I've noticed the easiest way to trigger the AP reboot is to visit a web site with a lot of images on each page, such as Tumblr, and scroll through them (forcing them to be loaded by the browser).

Barry

RE: AP30 unstable since 9.401

Chr.Aschenbrenner — Wed, 02 Nov 2016 03:26:56 GMT

Sophos Support found a workaround on my Problem

They implemented an older FirmwareVersion for AP´s on my UTM 9.407-3
After flashing the Accesspoint and reconnecting the AP connected to UTM and pulled the older firmware

AP is now is working and doing what it has to do

This worked only after the UTM had been restartet

So now I must not Update the UTM till they they fix this

This has been send to Global Escalation Support BUg ID NUTM-5567

RE: AP30 unstable since 9.401

JamieBah1 — Tue, 01 Nov 2016 13:05:06 GMT

Has anyone else noticed this in the log file?

Use of uninitialized value in concatenation (.) or string at awed_ng.pl line 347

That message occurs after "accepting" the AP-30.

RE: AP30 unstable since 9.401

JamieBah1 — Tue, 01 Nov 2016 12:20:19 GMT

Throw my hat in the ring on this one also. Added an AP-30 to the network today, it had been offline, as in physically disconnected, for months, and same thing happened here.

Tried re-flash, that was successful, but still cannot get it (AP-30) to "stay attached" to the UTM...

Considering it is now November, and the original question/issue was brought to light in May, I would be calling tech support every day. This delay in fixing this issue is not acceptable.

RE: AP30 unstable since 9.401

BarryG — Wed, 12 Oct 2016 14:45:49 GMT

Hi Chris, as far as I know, there is no solution or workaround. I've applied the latest Up2Date last week.

Sophos support is still occasionally looking at my system, but they have not mentioned any workarounds. I'm really not sure what they're actually doing, they don't tell me much.

Case id is 6050739; I'm asking if there's also an ID for a bug tracker (Mantis or whatever they're using now).

The easiest way to crash my AP is to visit a site with a lot of images such as Tumblr. Unfortunately, this means I can't browse a lot of the sites that I like to on my tablet or other wireless devices.

I'm not happy with how long this has been going on with no workaround. If this was for business use, it would be completely unacceptable.

Barry

RE: AP30 unstable since 9.401

Chr.Aschenbrenner — Tue, 11 Oct 2016 08:25:55 GMT

Any solutions yet?

same problem on AP 30 with UTM Release 9.407-3

2016:10:11-15:25:10 mail awed[20785]: [A4001998DCDAB59] AP30 from 172.17.3.10:35354 identified as A4001998DCDAB59

2016:10:11-15:25:10 mail awed[20785]: [A4001998DCDAB59] (Re-)loaded identity and/or configuration

2016:10:11-15:25:11 mail awed[20785]: [A4001998DCDAB59] ll_read: short read or connection error:

2016:10:11-15:25:11 mail awed[20785]: [A4001998DCDAB59] disconnected. Close socket and kill process

RE: AP30 unstable since 9.401

ChrisBKA — Wed, 05 Oct 2016 07:09:44 GMT

´Hi,

tried your solution today .. didn't work for me ...

awed is telling me :

2016:10:05-08:23:09 firewall awed[4735]: [MASTER] new connection from 192.168.100.37:4621

2016:10:05-08:23:09 firewall awed[18383]: [A4000CA27E7A8XXX] AP30 from 192.168.100.37:4621 identified as A4000CA27E7A8XXX

2016:10:05-08:23:09 firewall awed[18383]: [A4000CA27E7A8XXX] (Re-)loaded identity and/or configuration

2016:10:05-08:23:10 firewall awed[18383]: [A4000CA27E7A8XXX] ll_read: short read or connection error:

2016:10:05-08:23:10 firewall awed[18383]: [A4000CA27E7A8XXX] disconnected. Close socket and kill process.

Same AP same Cabel anothe Appliance with 9.405 running - no problems ---

any suggestions ?

RE: AP30 unstable since 9.401

sachingurung — Mon, 04 Jul 2016 01:44:37 GMT

Confirmed, meanwhile can you please DM me the ticket#, I will follow up for further information.

Thanks

RE: AP30 unstable since 9.401

BarryG — Thu, 30 Jun 2016 13:13:24 GMT

FYIs, I contacted Sohpos Support, they looked into it and sent me this today:

"Your case has been escalated, we have reviewed the logs and it has been identified as a known issue with reference ID as NUTM-3128

Our development team is working to provide a fix and it was suppose to get released this Friday, but they found some technical issues further so it has now been delayed.

We shall keep you posted."

RE: AP30 unstable since 9.401

BarryG — Wed, 29 Jun 2016 12:23:53 GMT

Hi,

Yes I do... last night, I see the new firmware was pushed to the AP:

2016:06:28-19:14:51 fw awed[6856]: [A4000BE4D4BC5D2] sent firmware /etc/wireless/firmware/AP30.uimage to device, releasing connection.
2016:06:28-19:14:54 192.168.211.211 aweclient[716]: aweclient.c (369) Writing firmware to '/dev/mtdblock5'.
2016:06:28-19:15:48 192.168.211.211 aweclient[716]: aweclient.c (393) Firmware upgrade finished: quit and reboot.
2016:06:28-19:15:48 192.168.211.211 aweclient[716]: Closing log...
2016:06:28-19:15:48 192.168.211.211 syslog: - shutdown -
2016:06:28-19:15:48 192.168.211.211 syslog:
2016:06:28-19:15:48 192.168.211.211 syslog:
2016:06:28-19:16:29 fw awed[4709]: [MASTER] new connection from 192.168.211.211:59926
2016:06:28-19:16:29 fw awed[7287]: [A4000BE4D4BC5D2] AP30 from 192.168.211.211:59926 identified as A4000BE4D4BC5D2
2016:06:28-19:16:29 fw awed[7287]: [A4000BE4D4BC5D2] (Re-)loaded identity and/or configuration

but later while I was surfing, it reset again:

2016:06:28-23:02:23 fw awed[4709]: [MASTER] new connection from 192.168.211.211:46741
2016:06:28-23:02:24 fw awed[25181]: [A4000BE4D4BC5D2] AP30 from 192.168.211.211:46741 identified as A4000BE4D4BC5D2
2016:06:28-23:02:24 fw awed[25181]: [A4000BE4D4BC5D2] (Re-)loaded identity and/or configuration
2016:06:08-11:08:22 192.168.211.211 logread[867]: Logread connected to 192.168.211.1:415
2016:06:28-23:02:26 fw awed[7287]: [A4000BE4D4BC5D2] ll_read: dead socket: Interrupted system call
2016:06:28-23:02:26 fw awed[7287]: [A4000BE4D4BC5D2] disconnected. Close socket and kill process.

BTW, note the logs from the AP are off by 20 days. (bold above)

I'm going to email support...

RE: AP30 unstable since 9.401

sachingurung — Wed, 29 Jun 2016 03:14:00 GMT

Hi Barry,

Do you still find the same logs?

Thanks

RE: AP30 unstable since 9.401

BarryG — Wed, 29 Jun 2016 01:06:04 GMT

No improvement in 9.404

RE: AP30 unstable since 9.401

BAlfson — Mon, 13 Jun 2016 21:16:59 GMT

Thanks, again, Barry. Your thread helped me keep my clients that use Wireless Protection on 9.3. This is not a problem for everyone, but I would urge everyone that can to get a ticket open with Sophos Support.

Cheers - Bob

RE: AP30 unstable since 9.401

BarryG — Thu, 09 Jun 2016 01:03:53 GMT

Hi, my AP30 still frequently reboots while web surfing. Anyone else experiencing this? Anyone else running an AP on 9.4?

RE: AP30 unstable since 9.401

BarryG — Thu, 02 Jun 2016 01:43:05 GMT

Hi, I power cycled the ap30 about 10 minutes ago, and it was OK but then went offline about 5 minutes later. It's working again now. Barry

RE: AP30 unstable since 9.401

sachingurung — Thu, 02 Jun 2016 01:06:42 GMT

Please try and update us.

RE: AP30 unstable since 9.401

BarryG — Wed, 01 Jun 2016 12:47:45 GMT

Hi, the AP has still mostly been working, but I did get a message from the firewall at 23:10 that it was offline again (briefly).

I can try power-cycling the AP tonight if you think it'd help.

Barry

RE: AP30 unstable since 9.401

sachingurung — Wed, 01 Jun 2016 01:34:00 GMT

Hi Barry,

Such logs are usually generated when the boot process went wrong. What happens to AP now?

Yes, AP will boot to previous firmware and automatically update to the latest version during the flash process. Once the AP is connected back to the UTM, it will check the latest firmware version available for AP to upgrade.

Thanks

RE: AP30 unstable since 9.401

BarryG — Tue, 31 May 2016 13:47:16 GMT

Hi, after the awed restart, I am seeing the following in wireless.log:

2016:05:31-11:33:23 fw awed[10346]: [MASTER] new connection from 192.168.211.211         :59999
2016:05:31-11:33:23 fw awed[10386]: [A4000BE4D4BC5D2] AP30 from 192.168.211.211:         59999 identified as A4000BE4D4BC5D2
2016:05:31-11:33:23 fw awed[10386]: [A4000BE4D4BC5D2] (Re-)loaded identity and/o         r configuration
2016:05:31-11:33:23 192.168.211.211 aweclient[716]: Cloudclient not found on ubu         s.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
2016:05:31-11:41:45 192.168.211.211 netifd: lan (751): Sending renew...
2016:05:31-11:41:45 192.168.211.211 netifd: lan (751): Lease of 192.168.211.211 obtained, lease time 86400
2016:05:31-11:41:46 192.168.211.211 hostapd: wlan2: STA 00:14:d1:f1:c5:ba WPA: group key handshake completed (RSN)
2016:05:31-11:41:46 192.168.211.211 hostapd: wlan1: STA 00:d0:2d:26:37:2c WPA: group key handshake completed (RSN)
2016:05:31-11:41:46 192.168.211.211 hostapd: wlan1: STA 10:1c:0c:2a:f0:9f WPA: group key handshake completed (RSN)
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.
nl80211 not found.

currently on 9.403 btw.

RE: AP30 unstable since 9.401

BarryG — Tue, 31 May 2016 13:37:37 GMT

Hi Sachin,

I have run the awed restart command and will keep an eye on it.

However, I have already applied recent up2dates and rebooted, so I'm sure awed had restarted then.

Also, I am sure the AP was flashed during the 9.400 setup, and probably during the 9.401 & 9.402 up2dates as well. If you let me know what to look for in the logs to confirm that, I will check.

I had a hard time getting the AP30 working with 9.4xx without VLANs; if re-flashing the firmware with the RecoveryApp is going to revert me back to an older firmware and cause problems again, I'd rather avoid that if possible.

Thanks,

Barry

RE: AP30 unstable since 9.401

sachingurung — Mon, 30 May 2016 03:49:45 GMT

Hi,

Restart awed services, take SSH to UTM with root privileges. Run command: /var/mdw/scripts/awed restart.

Also, try reflashing AP30, please refer : https://www.sophos.com/en-us/support/knowledgebase/118843.aspx

Hope that helps.