Thread Info
  • State Suggested Answer
  • +5 person also asked this people also asked this
  • Locked Locked
  • Replies 25 replies
  • Answers 2 answers
  • Subscribers 10 subscribers
  • Views 79119 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP30 unstable since 9.401

BarryG

Hi,

(currently running 9.402-7)

My AP30 frequently seems to reboot, after moving from 9.355 with VLANs to a new VM running 9.401 without VLANs.

Sometimes, I get email messages from the UTM "WARN-728 Access Point is Offline".

Here's the wireless.log entries from the last occurance:

2016:05:27-00:22:00 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 IEEE 802.11: authenticated
2016:05:27-00:22:00 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 IEEE 802.11: associated (aid 5)
2016:05:27-00:22:00 192.168.211.211 awelogger[1477]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="1c:5c:f2:9b:34:79" status_code="0"
2016:05:27-00:22:00 192.168.211.211 awelogger[1477]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="1c:5c:f2:9b:34:79" status_code="0"
2016:05:27-00:22:00 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 WPA: pairwise key handshake completed (RSN)
2016:05:27-00:22:00 192.168.211.211 awelogger[1477]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="1c:5c:f2:9b:34:79"
2016:05:27-00:23:51 192.168.211.211 hostapd: wlan1: STA 0c:d7:46:ab:84:00 IEEE 802.11: disassociated due to inactivity
2016:05:27-00:23:51 192.168.211.211 awelogger[1477]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="0c:d7:46:ab:84:00"
2016:05:27-00:23:52 192.168.211.211 hostapd: wlan1: STA 0c:d7:46:ab:84:00 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] kswapd0: page allocation failure: order:0, mode:0x20
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] CPU: 0 PID: 99 Comm: kswapd0 Not tainted 3.10.49 #3
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] Stack : 00000000 00000000 00000000 00000000 8054a0de 00000033 8182b3e8 00000000
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  80237544 8026c673 00000063 805437fc 8182b3e8 00000000 00000000 00000000
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  00000000 801e73cc 00000000 8015b69c 00000006 00000000 80239070 819a5a9c
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 819a5a28
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  ...
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] Call Trace:
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] [<80193870>] show_stack+0x48/0x70
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] [<801f8b7c>] warn_alloc_failed+0x108/0x12c
2016:05:27-00:26:40 fw awed[22827]: [A4000BE4D4BC5D2] ll_read: dead socket: Resource temporarily unavailable
2016:05:27-00:26:40 fw awed[22827]: [A4000BE4D4BC5D2] disconnected. Close socket and kill process.
2016:05:27-00:26:44 fw awed[4687]: [MASTER] new connection from 192.168.211.211:41002
2016:05:27-00:26:45 fw awed[23793]: [A4000BE4D4BC5D2] AP30 from 192.168.211.211:41002 identified as A4000BE4D4BC5D2
2016:05:27-00:26:45 fw awed[23793]: [A4000BE4D4BC5D2] (Re-)loaded identity and/or configuration




This thread was automatically locked due to age.
  • 0 in reply to BarryG

    Hi Barry,

    Do you still find the same logs?

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0 in reply to sachingurung

    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...

  • 0 in reply to BarryG

    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."

  • 0 in reply to BarryG

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

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0 in reply to sachingurung

    ´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 ?

  • 0 in reply to ChrisBKA

    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
  • 0 in reply to ChrisBKA

    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

  • 0

    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.

  • 0 in reply to JamieBah1

    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.

  • 0 in reply to JamieBah1

    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

Unfiltered HTML