System Log - General Log just shows a few hours back?

[Rici]

Hi,

How to get a longer logging, to see e.g. what happened three days back?

Thanks for helping me.

 

[L&LD]

What router? What firmware?

Is this a new issue?

 

[ColinTaylor]

To increase the size of the log file from 256kB to 1024kB (i.e. x4) SSH into the router an issue these commands:

nvram set log_size=1024
nvram commit
service restart_logger

 

[Tech9]

How to get a longer logging, to see e.g. what happened three days back?

What are your log settings? The default log file at default settings is big enough for many days.

 

[Rici]

Thank you, all.

Router is RT-AX86U, FW is 386.4.

Default log setting, I haven't hampered with them. It was on Debug - before I installed scribe yesterday. From what I observed, I can only see 12 hours back :-(

Installing scribe (tbh, not sure exactly it does, though) did not make a difference.

Haven't counted the number of lines, but is there a limit of 1024 entries?

 

[Rici]

To increase the size of the log file from 256kB to 1024kB (i.e. x4) SSH into the router an issue these commands:

nvram set log_size=1024
nvram commit
service restart_logger

Interesting! Is there a limit - or best-practice - for how much the size can be increased?

 

[ColinTaylor]

If you install Scribe you're replacing the router's system log management. Therefore my previous post becomes pointless.

Interesting! Is there a limit - or best-practice - for how much the size can be increased?

Increasing the default system log size increases the amount of memory and jffs storage used. Old Asus routers had very little spare memory and storage available. That's not so much of a problem anymore for the RT-AX86U.

If you want to retain all the old log information for a very long time you'll have to use Scribe to store it on a USB drive (or alternatively send the information to a remote log server). If you're only interested in increasing the visible log by x4 I suggest you uninstall Scribe and make the change in post #3.

 

[L&LD]

The first thing I would do is flash RMerlin 386.5_0 and follow with a full reset.

[Wireless] ASUS router Hard Factory Reset | Official Support | ASUS Global


Confirm by running at defaults (see below for suggested defaults) for the next few days to know the logging works properly. Then, you may add a freshly formatted USB drive (formatted on a PC, not the router) to add the scripts you want.

Fully Reset / Best Practice Setup / More

 

[ColinTaylor]

The first thing I would do is flash RMerlin 386.5_0 and follow with a full reset.

Why? This has nothing to do with what he's asking.

 

[L&LD]

Maybe not, but running firmware with known issues doesn't make sense either.

Since he'll be doing almost all the steps anyway, may as well begin with the best version of the firmware available today.

 

[ColinTaylor]

Maybe not,

It won't solve his problem.

but running firmware with known issues doesn't make sense either.

That's not relevant to his question. Even when he does update his firmware he doesn't need to go through the whole reset and setup process.

 

[L&LD]

We don't know if it will solve the problem or not, yet.

I don't believe it's not (necessarily) relevant to his question. We also don't know which firmware he updated from and if the problem was present in that previous version too.

I prefer to get a complete picture by asking questions first, rather than assuming (even about assuming issues that may exist or not in the firmware that otherwise shouldn't have these specific issues).

For instance, we didn't know third-party scripts were used (initially), nor how they've been modified/installed either.

 

[Tech9]

Router is RT-AX86U, FW is 386.4

Perhaps related to your issue? You lose the logs on reboot with 386.4 firmware.

Asuswrt-Merlin 386.5 changelog:

- FIXED: Earlier syslog content was missing on RT-AX86U and RT-AX68U after a reboot.

 

[ColinTaylor]

I prefer to get a complete picture by asking questions first, rather than assuming

Except that's exactly the opposite of what you did. You don't understand his problem so your immediate reaction was to tell him to change his firmware and factory reset his router. You made no attempt to diagnose the problem.

 

[L&LD]

No, it's not. You forget about post 2 and 5.

Your first response was a good guess, but still an assumption on your part as you indicate in a later post.

 

[ColinTaylor]

No, it's not. You forget about post 2 and 5.

Asking your stock question, doing nothing with the information provided and then posting your stock reply does nothing to try and understand the cause of the issue. Do you reformat your PC's hard drive and reinstall the OS every time you notice something you don't understand?

 

[Tech9]

Do you reformat your PC's hard drive and reinstall the OS every time you notice something you don't understand?

No. Reboot regularly to keep it going.

WiFi Adapter Keeps Disabling Itself

I'm unsure if this forum is correct for help with my adapter but here's hoping. I have an Asus mobo with a built in intel AX200 wifi adapter. The specific motherboard for reference is an Asus ROG Crosshair VIII Formula. For a long while now I've been having an issue where my wifi just randomly...

www.snbforums.com

 

[L&LD]

So, knowing what router we're talking about, what firmware it is on, and if this is a new issue or not is a stock question? Okay. Still pertinent.

And I did reply based on the new information presented. You just don't like my suggestion.

386.4 is not a firmware to base a router/network on when 386.5 is available. This is a fact. Look at the changelog for the answers.

BTW, re-installing Windows is not equivalent to flashing new firmware (but you already know that).

 

[Rici]

OK, I updated to 386.5 in the meantime. So that is addressed.
Albeit I don't think this caused the issue, since the router was running for 30 days sind the last reboot flawlessly.

Before I installed scribed, I could specify the level of detail that is logged (debug, information, warning etc.). After the scribed installation, that option is gone.

Where to find it with scribed installed?

 

[Rici]

Before I installed scribed, I could specify the level of detail that is logged (debug, information, warning etc.). After the scribed installation, that option is gone.

Where to find it with scribed installed?

Where can I find those detail level specification option now, that I have scribed installed? Any hints?