Re: systemd boot errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Tue, Aug 28, 2012 at 2:41 PM, Arno Gaboury <arnaud.gaboury@xxxxxxxxx> wrote:
>
> Dear list,
>
> I am testing systemd.
> I have the following errors at boot:
>
> 1-failed to start packet filtering framework
> iptables is installed on my system

There probably was an error restoring the iptables rules. Check
"systemctl status iptables"

> 2-boot hangs on at: reached target graphical interface
> i do not use any login manager. runlevel 3 + startx

"systemctl enable multi-user.target" will switch the default target to
multi-user.target

>
> 3-systemd can't write to journal.
> I have a message at boot:
> /var/log/journal/d564e939c66712bce792b0710000017f/fss   file does not
> exist. I have in fact
> /var/log/journal/d564e939c66712bce792b0710000017f/system.journal.

You get this error because you're running systemd v189 and have
forward-secure log sealing enabled (which is the default), but no
sealing keys exist.

Either disable sealing in "/etc/systemd/journald.conf" or generate
sealing keys using "journalctl --setup-keys".


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux