I have been having problems (described elsewhere) wit my semi-new GS-AX3000 crashing. So I have taken to watching for crashlogs in the system log file of the amin pages of the router.
Today I noticed that one occurred early Wednesday morning. This happens to be when I have a scheduled reboot happening. And indeed I see this in the log file:
Nov 9 04:30:23 reboot scheduler: [timecheck] The system is going down for reboot May 4 22:05:03 crashlog: LOG May 4 22:05:03 kernel: klogd started: BusyBox v1.24.1 (2021-07-16 19:17:53 CST) May 4 22:05:03 crashlog: <6> Hooking IMQ before NAT on POSTROUTING. May 4 22:05:03 crashlog: <6>PPP generic driver version 2.4.2 May 4 22:05:03 crashlog: <6>PPP BSD Compression module registered May 4 22:05:03 crashlog: <6>PPP Deflate Compression module registered May 4 22:05:03 crashlog: <6>PPP MPPE Compression module registered May 4 22:05:03 crashlog: <6>NET: Registered protocol family 24 ...
Now it seems to me that a scheduled reboot is a known and expected thing. There is a user interface for doing them (thankfully). But as such, it seems silly that they should produce a crashlog. It should be a simple reboot for a known reason. Most devices have a "clean" way to be brought down and rebooted. Such a clean reboot would not be considered a crash and would not create a crashlog.
Crashlogs are very helpful in trying to decipher what is going wrong with a system like a router. So cluttering up the log file with non-crash, crashlogs seems silly and confusing.