[SOLVED] LFS6.8 startup problem on kernel log daemon

vmsda · 04-01-2011, 03:44 PM

I finished the Book and had a go at starting LFS. Everything seemed ok until the following messages

Code:

INIT: Entering runlevel : 3
Starting system log daemon...     [OK]
Starting kernel log daemon...

... and got stuck there.

Suggestions welcome.

druuna · 04-02-2011, 03:26 AM

Hi,

It looks like the system log daemon (syslogd) is started correctly, but the kernel log daemon (klogd) did not.

Did you check the /etc/rc.d/init.d/sysklogd file, which starts both the system and kernel log daemon, for possible errors?

Hope this helps.

vmsda · 04-02-2011, 03:43 AM

Quote:

Originally Posted by druuna

... Did you check the /etc/rc.d/init.d/sysklogd file ...

Thank you again for your prompt hint, druuna. I did not check because I am forced to power off/on. What I did do was to start in recovery mode, and the system starts all right. So I shall do that again, and then try to activate the log daemons manually and try to see what comes out of that. I shall keep you posted on the results.

UPDATE:
I tried but failed to activate the daemons manually. Next best thing, I tried to do a normal boot again, and when the system stopped, I powered off/on, restarted Ubuntu, mounted the lfs partition and inspected var/log/wtmp and var/run/utmp for possible erros, but files were empty.

This looks bad.

druuna · 04-02-2011, 12:01 PM

Hi,

Why did you look at /var/log/wtmp and /var/run/utmp? You need to look at the /etc/rc.d/init.d/sysklogd file.

You can try the following to determine if klogd is the actual culprit: move the sysklogd startup file (I assume you booted into ubuntu and mounted LFS at some place):

Code:

cd <mountpoint>/etc/rc.d/rc3.d/
mv S10sysklogd _S10sysklogd

Reboot into LFS and see if the boot process continues. If it does, then something is indeed wrong with the /etc/rc.d/init.d/sysklogd file and you can do the following steps:

After editing /etc/rc.d/init.d/sysklogd you can check if it starts correctly by doing:

Code:

cd /etc/rc.d/init.d
./sysklogd start

If it hangs you can kill it (ctrl-c) and try again from the edit step.

If the problem is fixed, restore the file you moved earlier:

Code:

cd /etc/rc.d/rc3.d
mv _S10sysklogd S10sysklogd

Hope this helps.

BTW: Don't edit a previous post when updating, just post a follow up message, that way I get notified (I do check my previous posts, but not all the time).

vmsda · 04-03-2011, 10:09 AM

Quote:

Originally Posted by druuna

Why did you look at /var/log/wtmp and /var/run/utmp? You need to look at the /etc/rc.d/init.d/sysklogd file.

Hello, druuna:

I looked at the sysklogd file, which is a script, and it did not display any messages. So, from looking at other questions and answers in this forum I was led to have a look at those logs which, by the way, were empty.

So I took a more radical approach. Since I had followed your proverbial wisdom and had saved the "sources" and "tools" contents as per the end of chapter 5 in the Book, I decided to rebuild the system from there. And now I am happy to say that at the end of the saga the system did boot properly - except that the eth0 net interface did not come up because I tried to use dhcp (I do not have a static setup) and, strangely, when I log in as root and change the directory, the prompt never shows me the working directory, althought it obviously takes it into account for subsequent commands. But anyway, these are small glitches in an overall pleasant experience.

Thank you again.

druuna · 04-03-2011, 11:06 AM

Hi,

Nice to read you got it working!

About the dhcp problem: Probably a configuration issue. Check the files in /etc/sysconfig/network-devices/ to start with.

About the root prompt: LFS does only do minimal configuring. Have a look at BLFS, especially chapter 3. The setting of the prompt (among a lot of other things) is done in The Bash Shell Startup Files

BTW: You're welcome

vmsda · 04-03-2011, 11:28 AM

Before I close this thread, I should like to make a couple of points:

1. To thank everyone who took the trouble to answer my queries. In this respect, I must in all fairness single out druuna, who not only contributed most to the conclusion of my labours, but also answered sometimes within minutes of my posting.

2. Since my lack of knowledge and other resource types precludes me from contributing in a more meaningful way, I was left with the option of a standard cash donation, which I have done with pleasure.

Onward to BLFS, then.

druuna · 04-03-2011, 12:29 PM

Hi,

Great to read you appreciate the help you get here at LQ

The donation is a great gesture, Jeremy (the owner of LQ) will be pleased, I'm sure!

trombley2009 · 07-29-2014, 11:45 AM

I had the same issue on my LFS system.
My system is based on LFS 7.5.
One thing can also try is to check the permissions of the /sbin/klogd binary.
On my system, it was set to -r-x------.
Do a chmod 755 /sbin/klogd and see if that helps. It worked on my system.
Hope this helps.
Mike.

trombley2009 · 07-29-2014, 12:03 PM

Quote:

Originally Posted by trombley2009

I had the same issue on my LFS system.
My system is based on LFS 7.5.
One thing can also try is to check the permissions of the /sbin/klogd binary.
On my system, it was set to -r-x------.
Do a chmod 755 /sbin/klogd and see if that helps. It worked on my system.
Hope this helps.
Mike.

after rebooting I still have the same issue.
I thought I fixed it.