[arch-general] systemd boot errors
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 2-boot hangs on at: reached target graphical interface i do not use any login manager. runlevel 3 + startx 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. Thank you for any help.
On Tue, Aug 28, 2012 at 9:41 AM, Arno Gaboury
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
2-boot hangs on at: reached target graphical interface i do not use any login manager. runlevel 3 + startx
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.
Have you read Arch wiki about systemd? It explains 2 and 3 and will help you debug 1. -- A: Because it obfuscates the reading. Q: Why is top posting so bad? For more information, please read: http://idallen.com/topposting.html ------------------------------------------- Denis A. Altoe Falqueto Linux user #524555 -------------------------------------------
On Tue, Aug 28, 2012 at 2:41 PM, Arno Gaboury
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".
participants (3)
-
Arno Gaboury
-
Denis A. Altoé Falqueto
-
Jan Steffens