| Summary: | klogd fail to restart successfully across hardware reboots. | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | koti <koteswararao18> |
| Component: | Other | Assignee: | unassigned |
| Status: | NEW --- | ||
| Severity: | normal | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | 1.35.x | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
Some more details would be good, E.G. how do you start klogd, does it print out any error messages when it fails to start? You talk about a firmware upgrade, but it is unclear to me what the relation is between that and your klogd issue? Hi, thank you for your reply. >>how do you start klogd, does it print out any error messages when it fails to >>start? i didn't see any error message in the log. seems i need to enable loglevel to see klog failure if it emit it or not. meanwhile, as i mentioned earlier, once booting is done, i didn't see "klogd start" message which indicates klogd is started successfully but in the 'ps ' list i noticed klogd process is alive. {{ /# ps | grep klogd 5500 root 3916 S /bin/klogd -n }} i launched /bin/klogd at shell prompt as given below and klogd is launched successfully. {{ /# /bin/klogd -n (In one shell, this command is launched, and it's waiting indefinitely) }} in another shell, i just checked if klogd is started successfully or not? it's started successfully. {{ # cat /var/log/dmesg/kern.log | grep klogd .. May 15 23:49:53 kern.notice kernel: klogd started: BusyBox v1.35.0 (2023-05-12 04:41:16 UTC) /# ps | grep klogd 5500 root 3916 S /bin/klogd -n 26327 root 3916 S /bin/klogd -n 26449 root 3916 S grep klogd /# From process list, observed klogd -n generates new PID 26327. does it mean klogd is not exited properly during shutdown is leading to failure in starting it successfully? }} >>firmware upgrade, but it is unclear to me what the relation is between that >>and your klogd issue Firwmare upgrade means, x86-64 target machine is flashed with image i.e built on local ubuntu machine. Once it's flashed with new image, all services will be started for first time and as part of it, klogd also launched for first time successfully. But during second reboot, klogd seems not exited properly, so launching it again fails after reboot is done? Regards Koti The "klogd start" message presumably comes from an init script or similar, so if you don't see that, please verify/debug the script. You don't mention if this is a completely custom setup with init scripts written by you or if you use something existing like Buildroot to provide the start/stop logic? Maybe the easiest way forward is to not startup anything though scripts but instead run syslogd and klogd manually, possibly through strace to see what is happening. |
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