scMerlin Odd behaviour from RT-AX56U offsite - web control panel down

[BikeHelmet]

Howdy all,

I have an RT-AX56U offsite that is acting odd. The Merlin http server is down, so no web control panel. Despite that I can putty in and explore just fine. It's routing stuff fine, performance is fine, but certain parts of it are rather broken. For example, in AMTM, I can't update anything - it just stalls when being told to update. And SCMerlin can't reboot anything either.

I thought rather than making a trip out there to power cycle it, someone could give me some tips on investigating the cause? I'd like to solve it if possible, to prevent a recurrence.

Cheers,

 

[BikeHelmet]

I'm still interested in solving this. Does anyone know what would cause SCMerlin's commands to stop working? Perhaps entware broke down or something? Where should I be looking for clues/answers?

Stalled at restarting uiScribe, just like everything else:

 

[BikeHelmet]

Well, I went onsite and rebooted it. Updated everything, then went into the web control panel and checked the logs.

There are approximately a million entries like this, with ~15 per second going back several days.

Jan 23 03:00:16 RT-AX56U wlceventd: wlceventd_proc_event(469): wl0.3: Deauth_ind 30:88:41:B3:D7:FC, status: 0, reason: Class 3 frame received from nonassociated station (7)

They have stopped after the reboot, but I am concerned that they might come back.

I went and checked the MAC online. It's from Sichuan AI-Link Technology Co., Ltd. - apparently they make IoT WiFi chips and whatnot. It may be part of a camera or smart lightbulb or some other device, which someone hooked up and connected to the WiFi? Anyone know how to get more info on it? I scanned it with AdvancedIPScanner and found nothing - no web control panel to connect to? What can I do to investigate the device?

I also found dozens of these in the other log files:

Jan 23 21:17:00 RT-AX56U kernel: 30:88:41:B3:D7:FC not mesh client, can't update it's ip

And these repeating entries, which appear to be completely separate, and are ongoing as of 20 minutes ago:

Jan 23 21:49:12 RT-AX56U kernel: potentially unexpected fatal signal 11.
Jan 23 21:49:12 RT-AX56U kernel: CPU: 1 PID: 10303 Comm: dcd Tainted: P           O    4.1.52 #1
Jan 23 21:49:12 RT-AX56U kernel: Hardware name: Generic DT based system
Jan 23 21:49:12 RT-AX56U kernel: task: d579f400 ti: d2232000 task.ti: d2232000
Jan 23 21:49:12 RT-AX56U kernel: PC is at 0xb6c0539c
Jan 23 21:49:12 RT-AX56U kernel: LR is at 0x1e808
Jan 23 21:49:12 RT-AX56U kernel: pc : [<b6c0539c>]    lr : [<0001e808>]    psr: 600f0010
Jan 23 21:49:12 RT-AX56U kernel: sp : be91b8e8  ip : 000a3050  fp : b5eff024
Jan 23 21:49:12 RT-AX56U kernel: r10: 000a33c8  r9 : b5eff904  r8 : 000a387c
Jan 23 21:49:12 RT-AX56U kernel: r7 : b5eff93c  r6 : 000a3876  r5 : 00000000  r4 : b5eff8e8
Jan 23 21:49:12 RT-AX56U kernel: r3 : 00000000  r2 : 6b498900  r1 : 0007e101  r0 : 00000000
Jan 23 21:49:12 RT-AX56U kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Jan 23 21:49:12 RT-AX56U kernel: Control: 10c5387d  Table: 1229404a  DAC: 00000015
Jan 23 21:49:12 RT-AX56U kernel: CPU: 1 PID: 10303 Comm: dcd Tainted: P           O    4.1.52 #1
Jan 23 21:49:12 RT-AX56U kernel: Hardware name: Generic DT based system
Jan 23 21:49:12 RT-AX56U kernel: [<c0026fe0>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Jan 23 21:49:12 RT-AX56U kernel: [<c0022c38>] (show_stack) from [<c048e07c>] (dump_stack+0x8c/0xa0)
Jan 23 21:49:12 RT-AX56U kernel: [<c048e07c>] (dump_stack) from [<c003ac88>] (get_signal+0x490/0x558)
Jan 23 21:49:12 RT-AX56U kernel: [<c003ac88>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Jan 23 21:49:12 RT-AX56U kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Jan 23 21:49:12 RT-AX56U kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)
Jan 23 22:02:34 RT-AX56U kernel: potentially unexpected fatal signal 11.
Jan 23 22:02:34 RT-AX56U kernel: CPU: 1 PID: 24067 Comm: dcd Tainted: P           O    4.1.52 #1
Jan 23 22:02:34 RT-AX56U kernel: Hardware name: Generic DT based system
Jan 23 22:02:34 RT-AX56U kernel: task: d4d54000 ti: d1e16000 task.ti: d1e16000
Jan 23 22:02:34 RT-AX56U kernel: PC is at 0xb6c6839c
Jan 23 22:02:34 RT-AX56U kernel: LR is at 0x1e808
Jan 23 22:02:34 RT-AX56U kernel: pc : [<b6c6839c>]    lr : [<0001e808>]    psr: 600f0010
Jan 23 22:02:34 RT-AX56U kernel: sp : befd08e8  ip : 000a3050  fp : b5eff024
Jan 23 22:02:34 RT-AX56U kernel: r10: 000a33c8  r9 : b5eff904  r8 : 000a387c
Jan 23 22:02:34 RT-AX56U kernel: r7 : b5eff93c  r6 : 000a3876  r5 : 00000000  r4 : b5eff8e8
Jan 23 22:02:34 RT-AX56U kernel: r3 : 00000000  r2 : 4ff66800  r1 : 0007e101  r0 : 00000000
Jan 23 22:02:34 RT-AX56U kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Jan 23 22:02:34 RT-AX56U kernel: Control: 10c5387d  Table: 0b97804a  DAC: 00000015
Jan 23 22:02:34 RT-AX56U kernel: CPU: 1 PID: 24067 Comm: dcd Tainted: P           O    4.1.52 #1
Jan 23 22:02:34 RT-AX56U kernel: Hardware name: Generic DT based system
Jan 23 22:02:34 RT-AX56U kernel: [<c0026fe0>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Jan 23 22:02:34 RT-AX56U kernel: [<c0022c38>] (show_stack) from [<c048e07c>] (dump_stack+0x8c/0xa0)
Jan 23 22:02:34 RT-AX56U kernel: [<c048e07c>] (dump_stack) from [<c003ac88>] (get_signal+0x490/0x558)
Jan 23 22:02:34 RT-AX56U kernel: [<c003ac88>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Jan 23 22:02:34 RT-AX56U kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Jan 23 22:02:34 RT-AX56U kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)
Jan 23 22:21:08 RT-AX56U kernel: potentially unexpected fatal signal 11.
Jan 23 22:21:08 RT-AX56U kernel: CPU: 1 PID: 758 Comm: dcd Tainted: P           O    4.1.52 #1
Jan 23 22:21:08 RT-AX56U kernel: Hardware name: Generic DT based system
Jan 23 22:21:08 RT-AX56U kernel: task: d1d36400 ti: d0804000 task.ti: d0804000
Jan 23 22:21:08 RT-AX56U kernel: PC is at 0xb6cc239c
Jan 23 22:21:08 RT-AX56U kernel: LR is at 0x1e808
Jan 23 22:21:08 RT-AX56U kernel: pc : [<b6cc239c>]    lr : [<0001e808>]    psr: 600f0010
Jan 23 22:21:08 RT-AX56U kernel: sp : beb428e8  ip : 000a3050  fp : b5fff024
Jan 23 22:21:08 RT-AX56U kernel: r10: 000a33c8  r9 : b5fff904  r8 : 000a387c
Jan 23 22:21:08 RT-AX56U kernel: r7 : b5fff93c  r6 : 000a3876  r5 : 00000000  r4 : b5fff8e8
Jan 23 22:21:08 RT-AX56U kernel: r3 : 00000000  r2 : cda67300  r1 : 0007e101  r0 : 00000000
Jan 23 22:21:08 RT-AX56U kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Jan 23 22:21:08 RT-AX56U kernel: Control: 10c5387d  Table: 0b97804a  DAC: 00000015
Jan 23 22:21:08 RT-AX56U kernel: CPU: 1 PID: 758 Comm: dcd Tainted: P           O    4.1.52 #1
Jan 23 22:21:08 RT-AX56U kernel: Hardware name: Generic DT based system
Jan 23 22:21:08 RT-AX56U kernel: [<c0026fe0>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Jan 23 22:21:08 RT-AX56U kernel: [<c0022c38>] (show_stack) from [<c048e07c>] (dump_stack+0x8c/0xa0)
Jan 23 22:21:08 RT-AX56U kernel: [<c048e07c>] (dump_stack) from [<c003ac88>] (get_signal+0x490/0x558)
Jan 23 22:21:08 RT-AX56U kernel: [<c003ac88>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Jan 23 22:21:08 RT-AX56U kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Jan 23 22:21:08 RT-AX56U kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)

Please share your wisdom, gurus!

 

[ColinTaylor]

The dcd crashes are a well known problem that is typically caused by an incompatibility between the Trend Micro modules and Diversion's pixelserv. Remove pixelserv.

The WiFi problem does seem likely to be caused by an IoT device. The million messages say that the device is "nonassociated" so it may not have ever connected properly to your network. wl0.3 is the 3rd guest network on the 2.4GHz band.

 

[BikeHelmet]

The dcd crashes are a well known problem that is typically caused by an incompatibility between the Trend Micro modules and Diversion's pixelserv. Remove pixelserv.

The WiFi problem does seem likely to be caused by an IoT device. The million messages say that the device is "nonassociated" so it may not have ever connected properly to your network. wl0.3 is the 3rd guest network on the 2.4GHz band.

Thanks for the reply, Colin,

What are the DCD crashes? Do they matter? What effect does it have on the operation of the router? I rather like how pixelserv blocks so many ads and threats. I'm more inclined to shut off the TrendMicro stuff than it, if I had to choose - but then would I lose QOS, or only AIProtection?

Yes, I suspect it failed during connecting and got confused in some manner. Hmm... that guest network isn't even turned on according to the Yazfi page. Although it does show up on the Guest Network page as Enabled. So perhaps it just isn't customized? Or could that be connected? I'm not up to date on how Yazfi and the default Guest feature interact.

Thank you for chiming in!

 

[ColinTaylor]

What are the DCD crashes? Do they matter? What effect does it have on the operation of the router? I rather like how pixelserv blocks so many ads and threats. I'm more inclined to shut off the TrendMicro stuff than it, if I had to choose - but then would I lose QOS, or only AIProtection?

dcd is part of the TrendMicro engine and runs when QoS or AiProtection is used. I don't know what effect the crashes have on the system as I never suffer from it. That's because I haven't enabled any of the TrendMicro stuff and therefore dcd is not running on my router. You could try running Diversion Lite which doesn't use pixelserv.

Yes, I suspect it failed during connecting and got confused in some manner. Hmm... that guest network isn't even turned on according to the Yazfi page. Although it does show up on the Guest Network page as Enabled. So perhaps it just isn't customized? Or could that be connected? I'm not up to date on how Yazfi and the default Guest feature interact.

I don't know how YazFi works but the guest network is definitely active to some extent (but perhaps misconfigured) or wl0.3 wouldn't exist.