LinuxQuestions.org - [SOLVED] Kernel log daemon not starting

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - Kernel log daemon not starting (https://www.linuxquestions.org/questions/linux-from-scratch-13/kernel-log-daemon-not-starting-4175438977/)

Kernel log daemon not starting

Hi

I have encountered a problem on my lfs the kernel log daemon is not starting, It looks like it happened about 9 days ago if i,m reading log correct
The last date was nov 18
The system log daemon is ok

Where should I start looking for problem or how to fix.

ps I have been installing packages working towards gnome
I have also made the partition larger as I ran out of room

Not sure what you do or do not know.

klogd is started, together with syslogd with this file during boot in runlevels 2 3 4 5: /etc/rc.d/init.d/sysklogd

No typo's? Did you add any (correct?) options to klogd?

If that doesn't help: Check your log files and the output of dmseg just after a reboot.

Hi

Only added the -c 3 to the end of start daemon /sbin/klogd but tried removing no difference but that has been there along time.

I did think of re running bootscripts from lfs again.
The next option would be to untar an older copy and work back through it again.
As the 18th was a sunday I would of installed a few packages

As far as i can see nothing showed up in dmseg

Strange.

Are you able to start klogd by hand (as root)?

Code:

# make sure it isn't running

ps -ef | grep klogd

# start klgod

/sbin/klogd &

# is it running

ps -ef | grep klogd

You might add an option (-o or -d comes to mind, check the klogd man page).

One other thing comes to mind: Did you alter any kernel options? I can't point you to s specific one at the moment (no kernel source available).

Just had a quick look at my kernel config and the only reference to the logs is this line:
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4

Could you ( or more likely gnome ) have reset the the log level somewhere? so that the demon is running but not actually spitting anything out?

Does "top" show the demon?

Hi

Druuna
Daemon is not running when booted but can start it by hand as you suggested.

I have also tried some old kernels to boot from still wont start, so i,m sure it,s not a problem in the kernel

Quote:

Originally Posted by spiky0011 (Post 4838901)

Daemon is not running when booted but can start it by hand as you suggested.

I have also tried some old kernels to boot from still wont start, so i,m sure it,s not a problem in the kernel

Looking at the feedback I have to agree.

You said you can start klogd by hand (using /sbin/klogd), can you stop (check both manually) and start klogd and syslogd by using /etc/rc.d/init.d/sysklogd stop and /etc/rc.d/init.d/sysklogd start (also check both manually if success is suggested)?

Ok

output of /etc/rc.d/init/sysklogd stop
Stopping kernel log daemon
stopping system log daemon

Just as a note it reports stopping kernel log daemon when I shutdown

output of /etc/rc.d/init/sysklogd start
Starting system log daemon ok
Starting kernel log daemon fail

Quote:

Originally Posted by spiky0011 (Post 4838947)

output of /etc/rc.d/init/sysklogd start
Starting system log daemon ok
Starting kernel log daemon fail

So, using /sbin/klogd works. Using the init script doesn't start klogd. But syslog is started, which tells you that the init script seems to be working.

The start_daemon function does return exit codes/messages, which are also logged in case of failure : What have you seen in the logs? If nothing is found you could add (temporarily) the following line to /etc/syslog.conf (and restart sysklogd):

Code:

# save all in one file

*.*                      -/var/log/allmessages

The above would print all that is logged to a file.

Ok

created file allmessages then rebooted

Code:

Nov 28 19:56:22 Planet-Spiky syslogd 1.5.0: restart.

Nov 28 19:56:23 Planet-Spiky /usr/sbin/gpm[1443]: *** info [daemon/startup.c(136)]: 

Nov 28 19:56:23 Planet-Spiky /usr/sbin/gpm[1443]: Started gpm successfully. Entered daemon mode.

Nov 28 19:56:24 Planet-Spiky /usr/sbin/gpm[1443]: *** info [mice.c(1988)]: 

Nov 28 19:56:24 Planet-Spiky /usr/sbin/gpm[1443]: imps2: Auto-detected intellimouse PS/2

Nov 28 19:56:24 Planet-Spiky login[1447]: pam_unix(login:session): session opened for user spiky by LOGIN(uid=0)

Nov 28 19:56:24 Planet-Spiky dbus[1421]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)

Nov 28 19:56:25 Planet-Spiky dbus[1421]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)

Nov 28 19:56:25 Planet-Spiky polkitd[1522]: Started polkitd version 0.107

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Loading rules from directory /etc/polkit-1/rules.d

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Loading rules from directory /usr/share/polkit-1/rules.d

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Finished loading, compiling and executing 1 rules

Nov 28 19:56:26 Planet-Spiky dbus[1421]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Acquired the name org.freedesktop.PolicyKit1 on the system bus

Nov 28 19:56:26 Planet-Spiky dbus[1421]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'

Nov 28 19:57:00 Planet-Spiky sudo:    spiky : TTY=tty1 ; PWD=/home/spiky ; USER=root ; COMMAND=/bin/cp -v /var/log/allmessages /home/spiky/Documents/

If I start klogd then this file fills up

Quote:

Originally Posted by spiky0011 (Post 4839003)

Ok

created file allmessages then rebooted

Code:

Nov 28 19:56:22 Planet-Spiky syslogd 1.5.0: restart.

Nov 28 19:56:23 Planet-Spiky /usr/sbin/gpm[1443]: *** info [daemon/startup.c(136)]: 

Nov 28 19:56:23 Planet-Spiky /usr/sbin/gpm[1443]: Started gpm successfully. Entered daemon mode.

Nov 28 19:56:24 Planet-Spiky /usr/sbin/gpm[1443]: *** info [mice.c(1988)]: 

Nov 28 19:56:24 Planet-Spiky /usr/sbin/gpm[1443]: imps2: Auto-detected intellimouse PS/2

Nov 28 19:56:24 Planet-Spiky login[1447]: pam_unix(login:session): session opened for user spiky by LOGIN(uid=0)

Nov 28 19:56:24 Planet-Spiky dbus[1421]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)

Nov 28 19:56:25 Planet-Spiky dbus[1421]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)

Nov 28 19:56:25 Planet-Spiky polkitd[1522]: Started polkitd version 0.107

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Loading rules from directory /etc/polkit-1/rules.d

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Loading rules from directory /usr/share/polkit-1/rules.d

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Finished loading, compiling and executing 1 rules

Nov 28 19:56:26 Planet-Spiky dbus[1421]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'

Nov 28 19:56:26 Planet-Spiky polkitd[1522]: Acquired the name org.freedesktop.PolicyKit1 on the system bus

Nov 28 19:56:26 Planet-Spiky dbus[1421]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'

Nov 28 19:57:00 Planet-Spiky sudo:    spiky : TTY=tty1 ; PWD=/home/spiky ; USER=root ; COMMAND=/bin/cp -v /var/log/allmessages /home/spiky/Documents/

If I start klogd then this file fills up

By executing /sbin/klogd -c 3 & or /etc/rc.d/init.d/sysklogd start?

Maybe too obvious, but have you tried replacing the sysklogd init script by a fresh copy from the book? <= Link to latest stable LFS, do check if this is also valid for the LFS version you are using.

Hi

Well the obvious seems to be the way to go It now loads

I have kept the old sysklogd file I will look through it to see if I can spot what has changed.

I do know that I havn't edited the file at all so if there is a change something changed it.