AX88U Weird log entries

[keef]

I got up this AM to no Internet. I saw some really weird log entries. Everything started around 1:05am then nothing until I rebooted at 7:30.
Asus RT AX88u Pro currently with no USB drive. Wireguard VPN was running.

This is an edited log file.

thanks

 

[ColinTaylor]

There is nothing useful or unusual in the edited log file.

 

[keef]

Can you tell me what these entries mean?

May 5 01:05:19 kernel: 6%^[[1A
May 5 01:05:19 kernel: 7%^[[1A
May 5 01:05:19 kernel: 7%^[[1A
May 5 01:05:19 kernel: 7%^[[1A
May 5 01:05:19 kernel: 8%^[[1A

and

ay 5 01:05:19 kernel: Reset the processors to start execution of the code in the on-chip memory
May 5 01:05:19 kernel: Verify that the processors are running: OK
May 5 01:05:19 kernel: Verify that the firmware has been loaded with good CRC: OK
May 5 01:05:19 kernel: Firmware loading completed successfully: v2.2.8
May 5 01:05:19 kernel: Loading firmware into detected PHYs: map=0x20000 count=1
May 5 01:05:19 kernel: Halt the PHYs processors operation
May 5 01:05:19 kernel: Upload the firmware into the on-chip memory: file=/rom/etc/fw/longfin_a0_firmware.bin size=29470

thanks

 

[ColinTaylor]

They are just standard initialization messages for the specific hardware in your router. Nothing unusual there. Those messages have always been there (for that model). Take a look at the bootup messages of any Linux PC and you'll see similar sorts of messages.

 

[keef]

The curious thing is that at the 1:05am reboot I was in bed. There was no reboot scheduled. What would make it attempt a reboot on its own? I say attempt since the reboot failed, there was no network available after this. There is nothing logged after the reboot until I did it manually.

thanks

 

[dave14305]

The curious thing is that at the 1:05am reboot I was in bed.

How do you know it occurred at 1:05am? The system log is only showing the default date and time once the clock gets reset after a reboot. As Colin said, your log was lacking any meat to give you any answers.

 

[keef]

How do you know it occurred at 1:05am? The system log is only showing the default date and time once the clock gets reset after a reboot. As Colin said, your log was lacking any meat to give you any answers.

I figured this clock time was accurate. Is this a reboot?

May 5 01:05:19 kernel: 54991E B0 3590:5099 --> 0x13
May 5 01:05:19 kernel: 4912M 3590:51cd --> 0x11
May 5 01:05:19 kernel: Loading firmware into detected PHYs: map=0x80000 count=1
May 5 01:05:19 kernel: Halt the PHYs processors operation
May 5 01:05:19 kernel: Upload the firmware into the on-chip memory: file=/rom/etc/fw/blackfin_b0_firmware.bin size=294708

 

[ColinTaylor]

I figured this clock time was accurate. Is this a reboot?

May 5 01:05:19 kernel: 54991E B0 3590:5099 --> 0x13
May 5 01:05:19 kernel: 4912M 3590:51cd --> 0x11
May 5 01:05:19 kernel: Loading firmware into detected PHYs: map=0x80000 count=1
May 5 01:05:19 kernel: Halt the PHYs processors operation
May 5 01:05:19 kernel: Upload the firmware into the on-chip memory: file=/rom/etc/fw/blackfin_b0_firmware.bin size=294708

The date and time resets to 5th May each time the router starts up. You need to look at the log messages before this point.

 

[keef]

Here is a couple of minutes before the errant reboot.

thanks

 

[ColinTaylor]

Here is a couple of minutes before the errant reboot.

thanks

We can see you rebooting the router at 07:27:22 but there's nothing particularly unusual in the preceding 10 minutes. If there are any clues in the log it must be before this point.

If you want us to look into this further post the entire unedited log rather than just snippets.

 

[keef]

here it is.

thank you

 

[ColinTaylor]

Thanks. There's nothing leaping out of the log file that suggests a problem (but maybe someone else can spot something I've missed). So my suspicion would now turn to it being an ISP issue. If you have an ISP modem you can log into check the overnight logs on that.

 

[dave14305]

It looks like you are running a DNS server on the NAS device at 192.168.50.102, and pointing WAN DNS there. That device was chatty as hell with frequent DHCP renewals until about 2:40AM. Perhaps it went offline, leaving you with no DNS (which might feel like “no Internet”). It didn’t reappear in the logs until after the reboot. Check the logs on NAS for further clues.

EDIT: you should also upgrade the firmware to 3004.388.8_4. You seem to be running the AiCloud-vulnerable 3004.388.8_2.

 

[keef]

Thanks. There's nothing leaping out of the log file that suggests a problem (but maybe someone else can spot something I've missed). So my suspicion would now turn to it being an ISP issue. If you have an ISP modem you can log into check the overnight logs on that.

Hopefully the rebooting does not become an issue. I appreciate your time. Thanks

 

[keef]

It looks like you are running a DNS server on the NAS device at 192.168.50.102, and pointing WAN DNS there. That device was chatty as hell with frequent DHCP renewals until about 2:40AM. Perhaps it went offline, leaving you with no DNS (which might feel like “no Internet”). It didn’t reappear in the logs until after the reboot. Check the logs on NAS for further clues.

EDIT: you should also upgrade the firmware to 3004.388.8_4. You seem to be running the AiCloud-vulnerable 3004.388.8_2.

I went to 8_4 and my VPN went down, sigh....I may move AGH to a USB drive on the router and take it off the NAS. I only put it there because I wanted to try it out AGH and could not find a spare USB drive at the time.

I am haunted.