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

    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

    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.

    cu
    Walter

Reply
  • 0 in reply to JamieBah1

    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.

    cu
    Walter

Children
No Data
Unfiltered HTML