[Bug 15561] New: klogd fail to restart successfully across hardware reboots.

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=15561

            Bug ID: 15561
           Summary: klogd fail to restart successfully across hardware
                    reboots.
           Product: Busybox
           Version: 1.35.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: koteswararao18 at gmail.com
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Hi,

i am redirecting kernel log (dmesg) to /var/log/dmesg/kern.log by defining
below rule in /etc/syslog.conf in linux.  
{{
kern.*         /var/log/dmesg/kern.log
}}
I am using Busybox-1.35 version specific syslogd and klogd to redirect dmesg
log to above kern.log file. In Linux x86-64 machine, once device is upgraded
with firmware and after rebooting, observed dmesg log is copied to kern.log
successfully as klogd and syslogd daemons are launched sucessfully during boot
phase.
{{
May 15 09:11:37  kern.notice kernel: klogd started: BusyBox v1.35.0 (2023-01-18
02:16:44 UTC)
...
May 15 09:34:41  syslog.info syslogd started: BusyBox v1.35.0
}}
But if i reboot machine intentionally and then, i noticed klogd is not launched
at all , so dmesg log is not copied to kern.log file. Where as syslogd is
launched successfully across reboots and klogd is not at all launched even
after many attempts. 5.4 is the kernel version running on linux machine.
Surprising why klogd is not launched at all from second reboot onwards. any
input for further debugging on the issue?

Regards
Koti

-- 
You are receiving this mail because:
You are on the CC list for the bug.