cancel
Showing results for 
Search instead for 
Did you mean: 

Random restart - GT-AX11000 - Logs

zebra-net
Level 7
Please can anyone help me, my GT-AX11000 restarts randomly and here are the logs. Can anyone give me any tips to fix it? Mac address not are not shown in logs i removed it into MA ADDRESS...:)
Thanks:)

Sep 29 22:12:23 rc_service: ntp 2845:notify_rc restart_diskmon
Sep 29 22:12:23 disk_monitor: Finish
Sep 29 22:12:23 disk monitor: be idle
Sep 29 22:12:24 kernel: random: nonblocking pool is initialized
Sep 29 22:12:24 httpd: Succeed to init SSL certificate...8443
Sep 29 22:12:24 httpd: Succeed to init SSL certificate...80
Sep 29 22:12:24 BONDING: option disabled
Sep 29 22:12:25 roamast: ROAMING Start...
Sep 29 22:12:25 kernel: SHN Release Version: 2.0.2 36f59aa
Sep 29 22:12:25 kernel: UDB Core Version: 0.2.20
Sep 29 22:12:25 kernel: sizeof forward pkt param = 280
Sep 29 22:12:25 BWDPI: fun bitmap = 83
Sep 29 22:12:27 A.QoS: qos_count=0, qos_check=0
Sep 29 22:12:31 dhcp client: bound 192.168.1.107/255.255.255.0 via 192.168.1.1 for 3600 seconds.
Sep 29 22:13:05 crond[1910]: time disparity of 2316427 minutes detected

Sep 29 22:13:23 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:13:23 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-42
Sep 29 22:13:31 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:13:31 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-60
Sep 29 22:13:33 kernel: bcm_i2c: bus 0: Failed to detect SFP: 100 retries exhausted
Sep 29 22:13:34 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:13:34 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-52
Sep 29 22:13:34 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:13:34 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-76
Sep 29 22:14:14 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7744)]periodic_check AM 4:1
Sep 29 22:14:14 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7783)]do webs_update
Sep 29 22:14:16 HMA: Download version info failed, retry=[4]
Sep 29 22:14:19 HMA: Download version info failed, retry=[3]
Sep 29 22:14:23 HMA: Download version info failed, retry=[2]
Sep 29 22:14:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7801)]retrieve firmware information
Sep 29 22:14:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7804)]user in use
Sep 29 22:14:26 HMA: Download version info failed, retry=[1]
Sep 29 22:14:30 HMA: Download version info failed, retry=[0]
Sep 29 22:14:31 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:14:31 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-64
Sep 29 22:14:36 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:14:36 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-73
Sep 29 22:14:42 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:14:42 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-50
Sep 29 22:14:48 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:14:48 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS, status: Successful (0), rssi:-69
Sep 29 22:14:49 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:14:49 wlceventd: wlceventd_proc_event(559): eth7: Assoc MAC ADDRESS status: Successful (0), rssi:-43
Sep 29 22:14:53 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7783)]do webs_update
Sep 29 22:14:53 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7801)]retrieve firmware information
Sep 29 22:14:53 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7804)]user in use
Sep 29 22:15:23 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7783)]do webs_update
Sep 29 22:15:23 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7801)]retrieve firmware information
Sep 29 22:15:23 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7804)]user in use
Sep 29 22:19:22 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:0
Sep 29 22:19:22 wlceventd: wlceventd_proc_event(559): eth7: AssocMAC ADDRESS status: Successful (0), rssi:-71
Sep 29 22:19:34 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind MAC ADDRESS, status: 0, reason: Unspecified reason (1), rssi:-77
Sep 29 22:19:34 wlceventd: wlceventd_proc_event(530): eth7: Auth MAC ADDRESS, status: Successful (0), rssi:-77
Sep 29 22:19:34 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc MAC ADDRESS, status: Successful (0), rssi:-77
2,322 Views
7 REPLIES 7

jzchen
Level 15
Sep 29 22:12:24 BONDING: option disabled

I don't have an AX11000, but do have an AXE11000

Have you bound devices to specific nodes/routers? If so turn it off. (I started out to try binding but if a node loses connection then the device would lose connection completely). Usually this was with an IoT and difficult to reconnect.

Also looks like automatic firmware update is turned on but having trouble. Maybe try turning it off...

My AXE11000 would restart whenever WAN side had a problem/connection loss. Try to check if WAN side from ISP is stable. ISP came and replaced cable from pole to house, tested signal from entry to modem, and said there was a problem with my wiring. I removed one splitter to boost signal and it stopped rebooting...

jzchen wrote:
Sep 29 22:12:24 BONDING: option disabled

I don't have an AX11000, but do have an AXE11000

Have you bound devices to specific nodes/routers? If so turn it off. (I started out to try binding but if a node loses connection then the device would lose connection completely). Usually this was with an IoT and difficult to reconnect.

Also looks like automatic firmware update is turned on but having trouble. Maybe try turning it off...

My AXE11000 would restart whenever WAN side had a problem/connection loss. Try to check if WAN side from ISP is stable. ISP came and replaced cable from pole to house, tested signal from entry to modem, and said there was a problem with my wiring. I removed one splitter to boost signal and it stopped rebooting...

Firmware Version:3.0.0.4.386_49599 automatic firmware is already turned off. Devices are not bound. isp device is proper stable and i have testet.

ahfoo
Level 13
This could be your ISP are renew their DHCP server, flushing server cache lead to this issue if you are not subscribe to fixed IP address services,. But having said that, if this happened once awhile randomly or happened many times a day? That the key point.

I saw this in your log:

Sep 29 22:12:31 dhcp client: bound 192.168.1.107/255.255.255.0 via 192.168.1.1 for 3600 seconds.
Sep 29 22:13:05 crond[1910]: time disparity of 2316427 minutes detected
I checked my log at around 22:13:05 and see no time disparity. That large amount of minutes I Googled is about 4.4 years. I'm beginning to suspect corrupted ASUSwrt (router OS) or malicious attack/code....

Maybe try reflash an OLDer BIOS then reflash the latest? (Have you already tried this)?

jzchen wrote:
I saw this in your log:

Sep 29 22:12:31 dhcp client: bound 192.168.1.107/255.255.255.0 via 192.168.1.1 for 3600 seconds.
Sep 29 22:13:05 crond[1910]: time disparity of 2316427 minutes detected
I checked my log at around 22:13:05 and see no time disparity. That large amount of minutes I Googled is about 4.4 years. I'm beginning to suspect corrupted ASUSwrt (router OS) or malicious attack/code....

Maybe try reflash an OLDer BIOS then reflash the latest? (Have you already tried this)?

OLDer BIOS then reflash the latest ? You means firmware?

zebra-net wrote:
OLDer BIOS then reflash the latest ? You means firmware?


Yes firmware. Sorry I see "BIOS & FIRMWARE" on the support pages and sometimes sloppily interchange them.

ahfoo wrote:
This could be your ISP are renew their DHCP server, flushing server cache lead to this issue if you are not subscribe to fixed IP address services,. But having said that, if this happened once awhile randomly or happened many times a day? That the key point.


I have never experience problem with Netgear XR500 but after GT-AX11000 i am facing this problem. Router restarts randly e.g few days or sometimes every day. i just disable QoS and til now no restart.