[arch-general] systemd boot errors
Jan Steffens
jan.steffens at gmail.com
Tue Aug 28 09:00:56 EDT 2012
On Tue, Aug 28, 2012 at 2:41 PM, Arno Gaboury <arnaud.gaboury at gmail.com> 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".
More information about the arch-general
mailing list