Reply
Highlighted
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1
Accepted Solution

AP-Pro keeps rebooting / disconnecting every day

[ Edited ]

Hi,

Since a week I own two AP-Pro units. One works well, while the other keeps rebooting every day. Sometimes it will reboot and come up again, sometimes I see a powerdown where a powercycle will help. Version of both units is the same:

Version 3.9.54.9373

Board Revision 33

Controller version: 5.9.29 (Build: atag_5.9.29_11384)

 

In the logging is a "panic" visible, enclosed as attachment. I swapped the PoE injectors, the problem stays in the same unit, I also tried a PoE switch that gave exact the same issue. Did already a factory reset. Also downgraded the firmware with the same result, afterwards again upgraded to the latest firmware. I'm out of options I'm afraid. Anybody a brilliant idea?

 

Thanks in advance!

 


Accepted Solutions
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

[ Edited ]

@UBNT-jeff wrote:
@rozenbergOne other thing, can you swap the two units with each other, to ensure that the problem follows the unit?


Forget to mention that I'm a tech guy myself. Did that already. Changed POE injectors, cables, isolated the unit in the network without users, isolated it with another SSID, etcetera. The problem moves with the unit ... As fas as I can see, a squasfs runs on the box running in RAM. Is there maybe a firmware version that only tests RAM in a loop and nothing more? Or maybe already available in the bootsector? Using a TTL to RS232 converter is standard practice here, but I don't know if there is something available to check/test...

View solution in original post


All Replies
Senior Member
Posts: 10,064
Registered: ‎08-04-2017
Kudos: 1631
Solutions: 493

Re: AP-Pro keeps rebooting / disconnecting every day

Hello @rozenberg,

 

Welcome to the community!

 

What firmware versions did you try?

Could you share your system config?

Settings > Maintenance > Support Info > Show System Config

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

[ Edited ]

Thanks for the warm welcome and the quick response Man Happy

 

System config attached, version is 5.9.29.

I tried a previous firmware version 3.9.27. And that is the same firmware branch I think, maybe a better idea to test a 3.8 version. On the other hand, my other AP-Pro works fine with the latest firmware. Both my AP-Pro's are from the same batch.

 

Thanks for your time & effort!

 

Kees

 

PS: I will change the language settings to US, a little bit easier to read for all of us Man Happy Now it is in Dutch

SystemConfig_US.JPG
Senior Member
Posts: 10,064
Registered: ‎08-04-2017
Kudos: 1631
Solutions: 493

Re: AP-Pro keeps rebooting / disconnecting every day

[ Edited ]

Hello @rozenberg,

 

Could you disable Band Steering to see if it makes a difference?

 

 

Regards,

Glenn R.

 

CC @UBNT-BenBuckley

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

[ Edited ]

Hi @AmazedMender16

 

Done, in both units. I will come back in max a day, or earlier if a reboot occurs ... Thanks again.

 

Update at 13:40 CET & 14:20 CET ...

 

Rebooted 17 minutes ago (13:23 CET), and 14:18 CET again ...

 

This logging found in my syslog:

 

Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syswrapper: ipready.br0 = 10.0.0.112
Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") init: process '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org' (pid 909) exited. Scheduling for restart.
Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") init: starting pid 976, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Nov 12 13:17:28 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ubnt_protocol.ubnt_usr1_handler(): Get DHCP IP
Nov 12 13:17:28 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ubnt_protocol.ubnt_usr1_handler(): my_ip is 10.0.0.112
Nov 12 13:17:28 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ubnt_protocol.ubnt_multicast_socket_init(): already drop membership
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syswrapper: hostapd update: conf=/etc/aaa2.cfg iterface= nas_ip=10.0.0.112 res=
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syswrapper: hostapd update: conf=/etc/aaa1.cfg iterface= nas_ip=10.0.0.112 res=
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") hostapd: ath0: STA 08:c5:e1:ef:f1:1b RADIUS: starting accounting session 5B9ADCE7-00000000
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath0: 08:c5:e1:ef:f1:1b / 10.0.0.106
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") hostapd: ath0: STA 08:c5:e1:ef:f1:1b WPA: group key handshake completed (RSN)
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") init: process '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p br0:22' (pid 910) exited. Sc
Nov 12 13:17:29 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") init: starting pid 1067, tty '/dev/null': '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] ------------[ cut here ]------------
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] WARNING: at net/core/dev.c:2885 net_rx_action+0xf4/0x1d8()
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] Modules linked in: ath_pktlog(P) umac ath_dev(P) ath_spectral(P) ath_dfs(P) ath_rate_atheros(P) ath_hal(P) adf(P)asf(P) athrs_gmac pktgen fuse sd_mod scsi_mod sha1_generic michael_mic md5 hmac des_generic arc4 aes_generic ecb cbc gpiodev(P) ubnthal(P) ubnt_common(P)
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] Call Trace:
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] [<8001359c>] dump_stack+0x8/0x34
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] [<8002c930>] warn_slowpath_common+0x70/0x98
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] [<8017896c>] net_rx_action+0xf4/0x1d8
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.496000] [<8003251c>] __do_softirq+0x98/0x13c
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000] [<80032608>] do_softirq+0x48/0x68
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000] [<8000242c>] ret_from_irq+0x0/0x4
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000] [<8000fb34>] r4k_wait_irqoff+0x20/0x24
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000] [<8001055c>] cpu_idle+0x24/0x44
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000] [<802779f0>] start_kernel+0x364/0x380
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000]
Nov 12 13:17:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 57.497000] ---[ end trace 896c83f80c1f1b54 ]---
Nov 12 13:18:02 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") crond[911]: time disparity of 25700417 minutes detected

 

Kees

Ubiquiti Employee
Posts: 1,286
Registered: ‎12-16-2015
Kudos: 292
Solutions: 9

Re: AP-Pro keeps rebooting / disconnecting every day

@rozenberg do you see the same dump every time it reboots?

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

[ Edited ]

Hi @UBNT-BenBuckley

 

No, sometimes there is nothing to see, in the crash 5 minutes ago I saw the below mentioned log. Just half an hour before I did a factory default (with reset button), "forgot" the device in the controller and dit the adopt process again. And within half an hour he (she?) crashed again.

 

An option to test memory/chipset from within a SSH window should be nice by the way. The only difference I see at the moment is dat the Uboot version differs from my two units. The version that works fine has version unifi-v1.6.15.278-g4ebbbcff, the version that keeps resetting unifi-v1.5.8.220-g6b7cde06. Got that from /var/tmp/sysinit.txt

 

The unit that works fine has MacAddress "0418d680dc31", only the last 3 digits differ from the one with the nasty reboot-habbit. So that must be from the same batch/factory date. In other words, with the same config, I suspect that they behave the same. Although that's not entirely the case for my twin son/daughter I think now. Or better: Entirely not Man Happy But that's another story.

 

I will sign up for Beta ... >> Done and pushed the last Beta in the box (4.0.6.9572), it updated Uboot also I see ... (added 18:15 CET)

 

Thanks and best regards,

 

Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] CPU 0 Unable to handle kernel paging request at virtual address 00000080, epc == 00000080, ra == 00000080
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Oops[#1]:
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Cpu 0
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $ 0 : 00000000 fffffff8 00000001 807e0000
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $ 4 : 000200da 00000000 80275788 00000000
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $ 8 : 84a94ac4 0780068b 2ab43330 000004d6
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $12 : 07383353 2ab43410 2ab3e5d0 00404ad1
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $16 : 004c9e7c 7faf69f4 8000242c 80093604
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $20 : 00000603 2aaecfff 8007b8f0 00030002
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $24 : 0000023b 2ab8d314
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] $28 : 85018000 85019e98 80093d1c 00000080
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Hi : 000002f4
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Lo : 0001cae9
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] epc : 00000080 0x80
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Tainted: P
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] ra : 00000080 0x80
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Status: 1100ff03 KERNEL EXL IE
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Cause : 00800008
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] BadVA : 00000080
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] PrId : 0001974c (MIPS 74Kc)
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Modules linked in: ath_pktlog(P) umac ath_dev(P) ath_spectral(P) ath_dfs(P) ath_rate_atheros(P) ath_hal(P) adf(P) asf(P) athrs_gmac pktgen fuse sd_mod scsi_mod sha1_generic michael_mic md5 hmac des_generic arc4 aes_generic ecb cbc gpiodev(P) ubnthal(P) ubnt_common(P) [last unloaded: athrs_gmac]
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Process tr (pid: 23636, threadinfo=85018000, task=84a9c4c0, tls=00000000)
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Stack : 00000000 fffffff8 84a9c978 802634c8 8002793c 7faf69f4 84a9c4f0 80260000
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] 84a9c4c0 84a9c558 802634c8 84a9c978 80027a34 2aaa8744 2aaa8374 2ab46188
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] 7faf6f67 00406260 87892c80 87892e00 84a9c4c0 8000b470 00408074 00000000
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] 000004d9 00408074 00000000 00000000 2abe07b8 00000003 004c0000 7faf69f4
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] 00001008 00000003 00408074 00000000 80002420 80002558 004c9e7c 004c9e2c
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] ...
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Call Trace:
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] [<8002793c>] set_next_entity+0x28/0x60
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] [<80027a34>] pick_next_task_fair+0x98/0xb8
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] [<8000b470>] schedule+0x424/0x470
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] [<80002420>] ret_from_exception+0x0/0xc
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] [<80002558>] work_resched+0x8/0x2c
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000]
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000]
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.803000] Code: (Bad address in epc)
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.805000]
Nov 12 17:41:05 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 1414.805000] Fatal exception: panic in 5 seconds
Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syswrapper: ipready.br0 = 10.0.0.112
Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") init: process '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org' (pid 913) exited. Scheduling for restart.
Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") init: starting pid 980, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Nov 12 17:41:56 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ubnt_protocol.ubnt_usr1_handler(): Get DHCP IP
Nov 12 17:41:56 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ubnt_protocol.ubnt_usr1_handler(): my_ip is 10.0.0.112
Nov 12 17:41:56 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syslog: ubnt_protocol.ubnt_multicast_socket_init(): already drop membership

 

And another one just behind it:

 

Nov 12 17:54:58 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") hostapd: ath1: STA 84:c7:ea:c0:ac:18 RADIUS: starting accounting session 5B9ADCE7-00000006
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.420000] CPU 0 Unable to handle kernel paging request at virtual address 00000080, epc == 00000080, ra == 00000080
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Oops[#1]:
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Cpu 0
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $ 0 : 00000000 fffffff8 00000001 807e0000
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $ 4 : 000200da 00000000 80275788 00000000
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $ 8 : 84b49d2c 0780068b 2ab43330 000004d6
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $12 : 07383353 2ab43410 2ab3e5d0 00404ad1
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $16 : 7f96f2a0 7f96f2a0 0000540d 80093604
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $20 : 00000603 2aaecfff 8007b8f0 00030002
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $24 : 0000023b 2ab8d314
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] $28 : 84986000 84987e98 80093d1c 00000080
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Hi : 000002f4
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Lo : 0001cae9
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] epc : 00000080 0x80
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Tainted: P
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] ra : 00000080 0x80
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Status: 1100ff03 KERNEL EXL IE
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Cause : 00800008
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] BadVA : 00000080
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] PrId : 0001974c (MIPS 74Kc)
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Modules linked in: ath_pktlog(P) umac ath_dev(P) ath_spectral(P) ath_dfs(P) ath_rate_atheros(P) ath_hal(P) adf(P) asf(P) athrs_gm ac pktgen fuse sd_mod scsi_mod sha1_generic michael_mic md5 hmac des_generic arc4 aes_generic ecb cbc gpiodev(P) ubnthal(P) ubnt_common(P)
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Process tr (pid: 9533, threadinfo=84986000, task=8791edd0, tls=00000000)
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Stack : 00000001 807ee0b0 08100871 8792b978 85598320 00000004 00000000 80260000
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] 00000603 8791ee68 00000001 08100873 84a56520 00401a0c 2aaed000 2aaec000
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] 2aaed000 00000000 2aaed000 00000001 fffffff7 7f96f2a0 0000540d 84a61760
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] 00000000 80093dd4 00000000 00000000 2abe07b8 00000003 004c0000 7f96f734
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] 00001008 00000003 00408074 00000000 80002420 80004144 004c9eb4 004c9e2c
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] ...
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Call Trace:
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] [<80093dd4>] sys_ioctl+0x50/0x88
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] [<80002420>] ret_from_exception+0x0/0xc
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] [<80004144>] stack_done+0x20/0x3c
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000]
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000]
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.421000] Code: (Bad address in epc)
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.423000]
Nov 12 17:55:35 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") kernel: [ 847.423000] Fatal exception: panic in 5 seconds
Sep 13 23:55:57 10.0.0.112 ("U7P,0418d680dd2a,v3.9.54.9373") syswrapper: ipready.br0 = 10.0.0.112

New Member
Posts: 17
Registered: ‎07-25-2018

Re: AP-Pro keeps rebooting / disconnecting every day

Interesting.

 

I am seeing the same issue on mine.

 

I have 2 AP's and routinely they restart, sometimes every 10-15 minutes or so. 

 

Have done similar things to others :-

 

Rebuilt my controller (i'm running it on a mac server)

Reset all my devices - USG, Switch (150W 16 port) and 2 AP Pro's - tested them all at factory settings and then updated the firmware. 

Changed cables, ports etc etc (the usual checks)

 

Still getting restarts. 

 

Turned off my controller and its server now to see if thats causing it somehow as I saw an earlier post where someone suggested that multiple controllers might be informing and adopting the AP.

 

I am seeing some interesting info in my logs where the inform status seems to get changed after a restart :-

 

[2018-11-12 16:37:47,225] <inform-137> INFO inform - from [fc:ec:da:3a:ac:86](PM Office AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=1, ext/stun_ip=10.0.1.35, dev_ip=10.0.1.35, up=80
[2018-11-12 16:38:33,108] <inform-147> INFO inform - from [fc:ec:da:74:66:4e](PM Switch POE 16 (150W), US16P150, 3.9.54.9373): state=CONNECTED, last_inform=76, ext/stun_ip=10.0.1.38, dev_ip=10.0.1.38, up=2002
[2018-11-12 16:38:45,505] <inform-150> INFO inform - from [fc:ec:da:3a:ac:86](PM Office AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=58, ext/stun_ip=10.0.1.35, dev_ip=10.0.1.35, up=138
[2018-11-12 16:38:45,525] <inform-151> INFO inform - from [fc:ec:da:3a:ac:86](PM Office AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=0, ext/stun_ip=10.0.1.35, dev_ip=10.0.1.35, up=138
[2018-11-12 16:38:45,883] <inform-152> INFO inform - from [fc:ec:da:3a:ac:86](PM Office AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=0, ext/stun_ip=10.0.1.35, dev_ip=10.0.1.35, up=138
[2018-11-12 16:38:47,305] <inform-154> INFO inform - from [fc:ec:da:3a:b1:cc](PM Lounge AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=89, ext/stun_ip=10.0.1.31, dev_ip=10.0.1.31, up=140
[2018-11-12 16:38:47,310] <inform_stat-8> INFO event - [event] User[68:fe:f7:2d:ab:73] roams from AP[fc:ec:da:3a:ac:86] to AP[fc:ec:da:3a:b1:cc] from "channel 1(ng)" to "channel 1(ng)" on "Penny_Meadow"
[2018-11-12 16:38:48,322] <inform-155> INFO inform - from [fc:ec:da:3a:b1:cc](PM Lounge AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=1, ext/stun_ip=10.0.1.31, dev_ip=10.0.1.31, up=141
[2018-11-12 16:38:48,345] <inform-156> INFO inform - from [fc:ec:da:3a:b1:cc](PM Lounge AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=0, ext/stun_ip=10.0.1.31, dev_ip=10.0.1.31, up=141
[2018-11-12 16:38:48,631] <inform-157> INFO inform - from [fc:ec:da:3a:b1:cc](PM Lounge AP, U7PG2, 3.9.54.9373): state=CONNECTED, last_inform=0, ext/stun_ip=10.0.1.31, dev_ip=10.0.1.31, up=141
[2018-11-12 16:38:55,253] <inform-165> INFO inform - from [fc:ec:da:48:ab:47](PM Unifi Security Gateway, UGW3, 4.4.29.5124210): state=CONNECTED, last_inform=85, ext/stun_ip=10.0.1.1, dev_ip=80.1.174.127, up=17078
[2018-11-12 16:39:07,733] <inform-169> INFO inform - from [fc:ec:da:74:66:4e](PM Switch POE 16 (150W), US16P150, 3.9.54.9373): state=CONNECTED, last_inform=34, ext/stun_ip=10.0.1.38, dev_ip=10.0.1.38, up=2037

 

Anyone got any ideas why this might be happening ?

Ubiquiti Employee
Posts: 1,286
Registered: ‎12-16-2015
Kudos: 292
Solutions: 9

Re: AP-Pro keeps rebooting / disconnecting every day

@rozenberg Are those two reboots after the upgrade to 4.0.6?

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

@UBNT-BenBuckley No Sir, that was before the upgrade. Having a stable system now for at least 54 minutes now Man Happy

 

If a reboot occurs, I will mention it directly!

 

Beste Regards, Kees

New Member
Posts: 17
Registered: ‎07-25-2018

Re: AP-Pro keeps rebooting / disconnecting every day

Which component was upgraded to 4.0.6 ?

New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

Hi @steveclarke0703, that is the Beta firmware (4.0.6) on one of the AP-Pro's I have, installed approx. one hour ago ...

 

Beste regards,

New Member
Posts: 17
Registered: ‎07-25-2018

Re: AP-Pro keeps rebooting / disconnecting every day

the beta is stable ?

 

Did it fix this type of issue in its release notes ?

Senior Member
Posts: 10,064
Registered: ‎08-04-2017
Kudos: 1631
Solutions: 493

Re: AP-Pro keeps rebooting / disconnecting every day

Hello @steveclarke0703,

 

Been running the firmware since it got released without any issues.

Your issue could be fixed in Miscellaneous bug fixes and improvements.

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 15
Registered: ‎10-26-2018
Solutions: 1

Re: AP-Pro keeps rebooting / disconnecting every day

Hi @steveclarke0703, I did'nt loose time to look for any release notes Man Happy Living on the edge ...

New Member
Posts: 17
Registered: ‎07-25-2018

Re: AP-Pro keeps rebooting / disconnecting every day

Still unclear on my issue.

 

I run my controller on my Mac server and i recently migrated mac servers to a new one. I restored from backup, including the controller. When I seemed to be getting restarts on the AP's, I thought the controller might not have restored correctly, so after much testing (cables, etc etc) I blew it all away (reset all gear, deleted the controller and reinstalled).

 

Still no luck.

 

I then turned OFF the mac running the controller s/w and my AP's are fine. So leads me to think there may be 2 controllers active somehow when I start up the Unifi controller app on the mac.

 

When the mac was down, i looked at the cloud setup and it shows 2 IP addresses for the controller. which is plain wrong....

 

Could I be on the right track ?

 

About to restart the mac server and see if it disrupts the AP's again....

 

 

Screenshot 2018-11-12 at 18.14.59.png
Senior Member
Posts: 10,064
Registered: ‎08-04-2017
Kudos: 1631
Solutions: 493

Re: AP-Pro keeps rebooting / disconnecting every day

Hello @steveclarke0703,

 

Please open a new thread with your issue.

 


Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 17
Registered: ‎07-25-2018

Re: AP-Pro keeps rebooting / disconnecting every day

Why ?  Its the same issue .

Senior Member
Posts: 10,064
Registered: ‎08-04-2017
Kudos: 1631
Solutions: 493

Re: AP-Pro keeps rebooting / disconnecting every day

Hello @steveclarke0703,

 

You're talking about a controller with 2 IPs? ( Does the server have 2 nics? )

Did you try the latest BETA releases?

 


Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 17
Registered: ‎07-25-2018

Re: AP-Pro keeps rebooting / disconnecting every day

2 AP's.

 

Not tried the beta releeases as yet. Not prepared to go there. 

 

 

Reply