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 79706 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.
Parents
  • 0

    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.

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

  • 0 in reply to BarryG

    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

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

  • 0 in reply to BarryG

    Please try and update us.

    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, 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
  • 0 in reply to sachingurung
    Hi, my AP30 still frequently reboots while web surfing. Anyone else experiencing this? Anyone else running an AP on 9.4?
  • 0 in reply to BarryG

    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

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BarryG
    No improvement in 9.404
  • 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.

Reply Children
  • 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.

Unfiltered HTML