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

bugzilla at busybox.net bugzilla at busybox.net
Tue May 16 07:13:30 UTC 2023


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

--- Comment #2 from koti <koteswararao18 at gmail.com> ---
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

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


More information about the busybox-cvs mailing list