Logger not working on GL iNet X3000 and 24.10.0

Installing and Using OpenWrt
1

Good day!

I am facing an issue with the basic logger: It is not writing to syslog. Log read -f doesn't get anything. So, really nothing, also no error, no info at that time when I test smth like

logger "Hello"

In the System Log settings, I have changed the level and saved and tried another, but it doesn't help much.

Is there anything I can do or is this a known issue?

root@fritz:~# ubus call system board
{
	"kernel": "6.6.73",
	"hostname": "fritz.box",
	"system": "ARMv8 Processor rev 4",
	"model": "GL.iNet GL-X3000",
	"board_name": "glinet,gl-x3000",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "24.10.0",
		"revision": "r28427-6df0e3d02a",
		"target": "mediatek/filogic",
		"description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
		"builddate": "1738624177"
	}
}

root@fritz:~# cat /etc/config/system 

config system
	option hostname 'fritz.box'
	option ttylogin '0'
	option log_size '128'
	option urandom_seed '0'
	option zonename 'UTC'
	option log_proto 'udp'
	option conloglevel '8'
	option cronloglevel '7'

root@fritz:~# which logger
/usr/bin/logger

BR, Frood

2

it's working on 24.10 for me.

Have you made any other system changes? Maybe set the timezone option?

3

I recently tried manually running logd --help to see if it would provide any help and later found out that messages sent to the system log via logger after that never got logged. A service logd restart cleared the existing log entries but new logger entries logged fine. A reboot would do the same.

I mention this in case you might have done something similar. It might be good to reboot and check if logger messages show up again. Also check any config customization you have done for similar effects.

4

What does that mean? “Timezone option”?

5

Reboot, I tried that too.
Other messages are logged fine.
It just that the manual logger messages do not appear.
BTW on another router, the “one” it works fine.
Seems to be related to that x3000 model / build.

6

I think what @psherman is referring to is the timezone setting for the system.
From command line, you can see it with either uci show system and look at the line that starts like system.@system[0].timezone=
or you can grep "timezone" /etc/config/system to see a line that starts with option timezone.

You can also see the timezone setting in the luci web interface.
in luci, select the "System" menu item from the "System" menu. "Timezone" should be about the 5th item down on the "General Settings" tab.

I do not know the significance of such a change if a reboot occurred after the change though.

7

As a test, to see if something in the startup process breaks the ability to use logger, I think it would be good to restart the log service and test logger.
If you don't mind loosing your current log buffer, try restarting log and try logger.

From command line type service log restart, wait a minute and then test a simple logger command and see if it show up.

8

Why have you set this?
I think this enables remote logging, but you have not set up the target ip address (with option log_ip). Quite possibly why logging fails.

On the same hardware, for me the system config looks like this:

config system
	option hostname 'meshnode-8ecb'
	option timezone 'GMT0'
	option zonename 'UTC'
	option ttylogin '0'
	option log_size '128'
	option urandom_seed '0'

config timeserver 'ntp'
	option enabled '1'
	option enable_server '0'
	list server '0.openwrt.pool.ntp.org'
	list server '1.openwrt.pool.ntp.org'
	list server '2.openwrt.pool.ntp.org'
	list server '3.openwrt.pool.ntp.org'

Also note that logread -f means "follow". This will echo things going to syslog when they happen. Typically not much happens so you might not see anything for hours.
Running just logread should show everything in the buffer to that moment.

Logread cli options I get are:

root@meshnode-8ecb:~# logread --help
logread: unrecognized option: -
Usage: logread [options]
Options:
    -s <path>		Path to ubus socket
    -l	<count>		Got only the last 'count' messages
    -e	<pattern>	Filter messages with a regexp
    -r	<server> <port>	Stream message to a server
    -F	<file>		Log file
    -S	<bytes>		Log size
    -p	<file>		PID file
    -h	<hostname>	Add hostname to the message
    -P	<prefix>	Prefix custom text to streamed messages
    -z	<facility>	handle only messages with given facility (0-23), repeatable
    -Z	<facility>	ignore messages with given facility (0-23), repeatable
    -f			Follow log messages
    -u			Use UDP as the protocol
    -t			Add an extra timestamp
    -0			Use \0 instead of \n as trailer when using TCP

root@meshnode-8ecb:~#
1 Like
9

here we go, a

service log restart

gives me

Failed to find log object: Not found

in logread -f

Actually, it is this command

service log stop

That throws this message.

And after that, the logread is empty! Ok, that seems to be a hint, isn't it?

10

The timezone setting in Luci results in this item

option zonename 'UTC'
11

Yeah, I am always following the log in a separate window, to see everything what is happening. The output is sequentially the same as in logread.

The UDP is a leftover, I deleted it, but it doesnt make a difference.

12

After service log stop you also need a service log start.
You may need to restart your logread -f after that as well since the socket or file descriptor etc probably changes with the log restart.

13

Ok then. I have a brand new x3000 here so just flashed it with 24.10.0.
Logread gives the expected output.
The only conclusion is that you have done something to break it.

Try reflashing it again from scratch...

Here is my logread output, time set on boot to the time of build as there is no upstream connection for NTP:

BusyBox v1.36.1 (2025-02-03 23:09:37 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 24.10.0, r28427-6df0e3d02a
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:~# logread
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Mon Feb  3 23:09:41 2025 kern.notice kernel: [    0.000000] Linux version 6.6.73 (builder@buildhost) (aarch64-openwrt-linux-musl-gcc (OpenWrt GCC 13.3.0 r28427-6df0e3d02a) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 SMP Mon Feb  3 23:09:37 2025
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Machine model: GL.iNet GL-X3000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] OF: reserved mem: 0x0000000042ff0000..0x0000000042ffffff (64 KiB) map non-reusable ramoops@42ff0000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] OF: reserved mem: 0x0000000043000000..0x000000004302ffff (192 KiB) nomap non-reusable secmon@43000000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] OF: reserved mem: 0x0000000047c80000..0x0000000047d7ffff (1024 KiB) nomap non-reusable wmcpu-reserved@47c80000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] OF: reserved mem: 0x0000000047d80000..0x0000000047dbffff (256 KiB) nomap non-reusable wo-emi@47d80000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] OF: reserved mem: 0x0000000047dc0000..0x0000000047ffffff (2304 KiB) nomap non-reusable wo-data@47dc0000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Zone ranges:
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   DMA      [mem 0x0000000040000000-0x000000005fffffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   DMA32    empty
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   Normal   empty
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Movable zone start for each node
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Early memory node ranges
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000040000000-0x0000000042ffffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000043000000-0x000000004302ffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000043030000-0x0000000047c7ffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000047c80000-0x0000000047ffffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000048000000-0x000000005fffffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000005fffffff]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] psci: probing for conduit method from DT.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] psci: PSCIv1.1 detected in firmware.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] psci: Using standard PSCI v0.2 function IDs
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] psci: MIGRATE_INFO_TYPE not supported.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] psci: SMC Calling Convention v1.2
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] percpu: Embedded 18 pages/cpu s35560 r8192 d29976 u73728
Mon Feb  3 23:09:41 2025 kern.debug kernel: [    0.000000] pcpu-alloc: s35560 r8192 d29976 u73728 alloc=18*4096
Mon Feb  3 23:09:41 2025 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Detected VIPT I-cache on CPU0
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] CPU features: detected: GIC system register CPU interface
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] CPU features: kernel page table isolation disabled by kernel configuration
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] alternatives: applying boot alternatives
Mon Feb  3 23:09:41 2025 kern.notice kernel: [    0.000000] Kernel command line: console=ttyS0,115200n8 root=PARTLABEL=rootfs rootwait
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129024
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] software IO TLB: SWIOTLB bounce buffer size adjusted to 0MB
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] software IO TLB: area num 2.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] software IO TLB: mapped [mem 0x000000005fd67000-0x000000005fde7000] (0MB)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Memory: 497036K/524288K available (9024K kernel code, 998K rwdata, 1672K rodata, 448K init, 305K bss, 27252K reserved, 0K cma-reserved)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] rcu: Hierarchical RCU implementation.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] 	Tracing variant of Tasks RCU enabled.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] GICv3: 640 SPIs implemented
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] GICv3: 0 Extended SPIs implemented
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] Root IRQ handler: 0xffffffc080010080
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] GICv3: GICv3 features: 16 PPIs
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x000000000c080000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] arch_timer: cp15 timer(s) running at 13.00MHz (phys).
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2ff89eacb, max_idle_ns: 440795202429 ns
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000000] sched_clock: 56 bits at 13MHz, resolution 76ns, wraps every 4398046511101ns
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000085] Calibrating delay loop (skipped), value calculated using timer frequency.. 26.00 BogoMIPS (lpj=130000)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.000093] pid_max: default: 32768 minimum: 301
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.003042] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.003050] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.warn kernel: [    0.005241] cacheinfo: Unable to detect cache hierarchy for CPU 0
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.005782] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=2.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.005927] rcu: Hierarchical SRCU implementation.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.005930] rcu: 	Max phase no-delay instances is 1000.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006328] smp: Bringing up secondary CPUs ...
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006694] Detected VIPT I-cache on CPU1
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006740] GICv3: CPU1: found redistributor 1 region 0:0x000000000c0a0000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006771] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006841] smp: Brought up 1 node, 2 CPUs
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006847] SMP: Total of 2 processors activated.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006850] CPU features: detected: 32-bit EL0 Support
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006854] CPU features: detected: CRC32 instructions
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006887] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006890] CPU: All CPU(s) started at EL2
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.006892] alternatives: applying system-wide alternatives
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.010662] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.010679] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.011971] pinctrl core: initialized pinctrl subsystem
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.013056] NET: Registered PF_NETLINK/PF_ROUTE protocol family
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.013643] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.013670] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.013691] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.014062] thermal_sys: Registered thermal governor 'fair_share'
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.014066] thermal_sys: Registered thermal governor 'bang_bang'
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.014069] thermal_sys: Registered thermal governor 'step_wise'
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.014071] thermal_sys: Registered thermal governor 'user_space'
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.014143] ASID allocator initialised with 65536 entries
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.015085] pstore: Using crash dump compression: deflate
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.015089] pstore: Registered ramoops as persistent store backend
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.015092] ramoops: using 0x10000@0x42ff0000, ecc: 0
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.016648] /soc/interrupt-controller@c000000: Fixed dependency cycle(s) with /soc/interrupt-controller@c000000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.023145] Modules: 29616 pages in range for non-PLT usage
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.023154] Modules: 521136 pages in range for PLT usage
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.024145] cryptd: max_cpu_qlen set to 1000
Mon Feb  3 23:09:41 2025 kern.notice kernel: [    0.025297] SCSI subsystem initialized
Mon Feb  3 23:09:41 2025 kern.debug kernel: [    0.025582] libata version 3.00 loaded.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.027214] clocksource: Switched to clocksource arch_sys_counter
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.029472] NET: Registered PF_INET protocol family
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.029596] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031101] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031118] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031128] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031157] TCP bind hash table entries: 4096 (order: 5, 131072 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031255] TCP: Hash tables configured (established 4096 bind 4096)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031585] MPTCP token hash table entries: 512 (order: 1, 12288 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031696] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031711] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.031990] NET: Registered PF_UNIX/PF_LOCAL protocol family
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.032017] PCI: CLS 0 bytes, default 64
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.033390] workingset: timestamp_bits=46 max_order=17 bucket_order=0
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.038417] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.038427] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.071540] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.073372] gpio-export gpio-export: 4 gpio(s) exported
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.074177] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
Mon Feb  3 23:09:41 2025 kern.debug kernel: [    0.074206] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.074218] mtk-pcie-gen3 11280000.pcie:      MEM 0x0020000000..0x002fffffff -> 0x0020000000
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.083999] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.087771] printk: console [ttyS0] disabled
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.108163] 11002000.serial: ttyS0 at MMIO 0x11002000 (irq = 72, base_baud = 2500000) is a ST16650V2
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.108205] printk: console [ttyS0] enabled
Mon Feb  3 23:09:41 2025 kern.info kernel: [    0.895285] loop: module loaded
Mon Feb  3 23:09:41 2025 kern.info kernel: [    1.028904] i2c_dev: i2c /dev entries driver
Mon Feb  3 23:09:41 2025 kern.info kernel: [    1.035007] mtk-wdt 1001c000.watchdog: Watchdog enabled (timeout=31 sec, nowayout=0)
Mon Feb  3 23:09:41 2025 kern.info kernel: [    1.044509] NET: Registered PF_INET6 protocol family
Mon Feb  3 23:09:41 2025 kern.info kernel: [    1.050540] Segment Routing with IPv6
............................

.............
14

Yeah after stop I started it - both instead of restart.
Restarting means: stop & start
But it’s gone. Seems like log gets written after some 20-30 minutes but first, it is empty. Mate that’s the expected result after the stop.
Stop = clean

15

The thread is about
Logger

I also have a log in logread, that’s not the problem.
Do you get logs written with
Logger “hello”
?
This is what I am missing in the logs

16

Let's see what happens when you issue the following:

logger hello
logread -t 5

(please copy and paste the terminal session into this forum in the </> code formatter)

17

Yes.

root@OpenWrt:~# logger hello
root@OpenWrt:~# logread -e "root"
Sat Mar  8 09:19:56 2025 user.notice root: hello
root@OpenWrt:~#
18

Unfortunately this is not "tail". It just adds a "stardate" style timestamp.

The option to use would be -e, a filter on on the tag used by logger, but no tag is specified, so the default is the username that invoked the logger command, ie root.

1 Like
19

For me,
logger “hello”
Or
logger hello
Or
Adding tags or similar,
is without any effect on the log.
It does not appear in the log.
There is a log, it’s the best log I have ever seen, the log works nice and smooth - but there is nothing in the log that I want to write there with “logger”
This is exactly what this thread is about.

20

You're right... lol.

I meant to use -l 5'

Let's try this again:

logger hello
logread -l 5