[systemd-devel] startup problems

[Lennart Poettering]

On Tue, 01.06.10 23:57, Steve Herber (herber at thing.com) wrote:

> When I boot using systemd and all the services configured by
> the gentoo ebuild,  the system goes into a failure mode and
> I don't have a good way to capture the systemd[1] log messages
> from the screen.  So this is a request for a set of configuration
> files that bring up the most simple system possible.  Is that
> possible?

"failure mode"? what do you mean by that?

The most simple system you can bring up is if you pass
"systemd.default=emergency.service" on the kernel command line.

And iy ou pass "systemd.log_target=kmsg" on the command line the log
buffer will be written to the kernel log buffer, and is then accessible
with "dmesg".

> Here is an outline of the systemd[1] messages that I think give
> and idea of what is happening with my system.  Feedback on the
> particulars or recommendations in general are welcome.
> Could I be missing a kernel module that systemd does not try to
> load?
> 
> systemd running in init mode
> modprobe autofs4
> modprobe ipv6
> set hostname to <where did the dots go?>

We have been filtering all weird chars from that string. I have now
fixed that.

> Why is there a weird diamond character in front of the files?
> 	funny/etc/systemd/system
> 	funny/usr/local/lib/systemd/system
> 	funny/etc/init.d
> 	funny/etc

Hmm, there should be no weird char, that's a tab, that's all.

> Failed to get dbus connection
> Autofs kernel version 1.0
> Autofs protocol version 5.1
> proc-sys-fs-binfmt_misc.automount changed dead -> waiting
> job proc-sys-fs-binfmt_misc.automount/start finished, success=yes
> 
> job dev-mqueue.automount/start finished, success=yes
> Failed to initialize automounter: no such file or directory
> sys-kernel-debug.automount/start finished, success=no

Well, this is not really a problem so far. We just try to add an
automount point for /sys/kernel/debug, but that fails since your kernel
seems to be built without support for it. But that should be fine. You
may ignore that.

The output you have shown above shows no real problems.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4