[systemd-devel] Staring Apply kernel Variables failed.
lennart at poettering.net
Tue Feb 8 01:29:27 PST 2011
On Tue, 08.02.11 16:49, Chanwoo Choi (cwchoi00 at gmail.com) wrote:
> Dear members,
> [ 4.310630] systemd: Succesfully opened /dev/kmsg for logging.
> [ 4.315351] systemd: systemd 16 running in system mode. (-PAM -LIBWRAP
> -AUDIT -SELINUX +SYSVINIT -LIBCRYPTSETUP; ubuntu)
> Welcome to Linux!
> [ 4.340060] systemd: Your kernel apparently lacks built-in ipv6
> support. Might be a good idea to compile it in. We'll now try to work aroun
> d this by calling '/sbin/modprobe ipv6'...
> [ 4.356012] systemd: About to execute: /sbin/modprobe -qab -- ipv6
> [ 4.363128] systemd: Forked /sbin/modprobe as 1396
> [ 4.460776] systemd: /sbin/modprobe failed with error code 1.
This happens because ipv6 is blacklisted in your setup or not compiled
into the kernel.
> [ 4.469855] systemd: Set hostname to <chan>.
> [ 4.500345] systemd: Looking for unit files in:
> [ 4.503736] systemd: /usr/local/build/etc/systemd/system
> [ 4.509371] systemd: /usr/local/build/lib/systemd/system
> [ 4.517727] systemd: Looking for SysV init scripts in:
> [ 4.521716] systemd: /etc/init.d
> [ 4.525288] systemd: Looking for SysV rcN.d links in:
> [ 4.530565] systemd: /etc
> [ 4.535202] systemd: Using cgroup controller name=systemd. File system
> hierarchy is at /sys/fs/cgroup/systemd/system.
> [ 4.546258] systemd: Installed release agent.
> [ 4.583644] systemd: Created root group.
> [ 4.586575] systemd: Using notification socket
> [ 4.597105] systemd: Successfully created private D-Bus server.
> [ 4.601942] systemd: Using kernel console ttySAC2
> [ 4.797077] systemd: Failed to load configuration for udev.service: No
> such file or directory
Hmm, if you build udev with systemd support you should get the right
service file for udev installed.
> [ 5.020403] systemd: Installed new job systemd-sysctl.service/start as
> [ 5.134805] systemd: Installed new job sysctl.service/start as 46
Hmm, so for some reason you have both sysctl and systemd-sysctl
installed. Most likely you installed a new systemd version over an
existing one. sysctl.service existed only in older versions and was
recently replaced by a systemd internal implementation by the name of
systemd-sysctl.service. Fixing this probably just means removing
sysctl.service (or much better: removing all old cruft from old
installations and installing systemd anew). Normally a package manager
should do that for you.
> [ 5.532744] systemd: Failed to initialize automounter: No such file or
Most likely your kernel is lacking autofs4 support of some kind.
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel