Various boot failures following fresh installation / ISO generation

CarlD · 2014-08-28 20:17:24

Hello,

It would seem that fresh Arch installations in the last couple of days are providing quite a few errors / failures during bootup. None of these occurred before then, which also seems to affect ISOs generated over the last couple of days too. Having looked into it, the issues seem to be primarily related the automatic activation of dcpcd, ip6tables, iptables, and the krb5 (Kerberos) services. I determined this after comparing the systemctl outputs of an ISO generated a week ago to one I created today. The difference was that the former used WICD and the latter NetworkManager. However, I do not believe NM somehow activated these.

Also noticed failures related to nscd and WPA supplicant. At face value the nscd issue seems identical to a bug report made in 2005: https://bugs.archlinux.org/task/2697

Relevant journalctl entries for nscd:

Aug 28 18:47:41 evo nscd[235]: 235 cannot create /var/db/nscd/passwd; no persistent database used
Aug 28 18:47:41 evo nscd[235]: 235 cannot create /var/db/nscd/group; no persistent database used
Aug 28 18:47:41 evo nscd[235]: 235 cannot create /var/db/nscd/hosts; no persistent database used
Aug 28 18:47:41 evo nscd[235]: 235 cannot create /var/db/nscd/services; no persistent database used
Aug 28 18:47:41 evo nscd[235]: 235 cannot create /var/db/nscd/netgroup; no persistent database used

Still looking into the WPA supplicant issue. Found some old bug reports for other distros (i.e debian and Ubuntu), but nothing yet for Arch. Relevant journalctl entries for WPA supplicant:

Aug 28 18:49:03 evo systemd[1]: Dependency failed for WPA supplicant daemon (interface- and nl80211 driver-specific version).
Aug 28 18:49:03 evo systemd[1]: Dependency failed for WPA supplicant daemon (interface- and wired driver-specific version).
Aug 28 18:49:03 evo systemd[1]: Dependency failed for WPA supplicant daemon (interface-specific version).

Bit of an odd one I am still puzzled about is the failure of dmraid during ISO bootup. Again, this was not automatically activated before, but is now, resulting in (unsurprising) failure. Installation and ISO generation methods have not changed in the least, so am a tad perplexed! Can anyone offer any insight while I continue to investigate? Well, other than the most obvious suspicion, which is services for installed elements now automatically activate.

Much appreciated,

Carl

serfraviros · 2014-08-29 16:14:21

I have the same problem on a fresh install.

After running systemctl --state = failed I get the following:

UNIT LOAD ACTIVE SUB DESCRIPTION

● ip6tables.service loaded failed failed IPv6 Packet Filtering Framework
● iptables.service loaded failed failed Packet Filtering Framework
● krb5-kadmind.service loaded failed failed Kerberos 5 administration server
● krb5-kdc.service loaded failed failed Kerberos 5 KDC
● mdadm.service loaded failed failed MDADM Event Monitor
● systemd-journal-upload.service loaded failed failed Journal Remote Upload Servic

In my case I could make iptables and ip6tables torn after reading the wiki and do the following:

# touch /etc/iptables/iptables.rules

# systemctl start iptables

# touch /etc/iptables/ip6tables.rules

# systemctl start ip6tables

As for krb5 I could not even solve the problem, the problem is in the configuration file /etc/krb5.conf but when I compare the file with another previous installation on another computer there is no difference between them. I have not found much documentation about this topic.

A side effect is that there is no way that achieves connexion via wifi. If I connect to a wired network no problem, but it is impractical to take a very long cable wherever I carry a laptop.

CarlD · 2014-08-29 16:41:39

To use you network manager, type in the following:

sudo systemctl disable dhpcd.service

You don't actually need to configure iptables or anything like that. The problem is that they were automatically enabled when they shouldn't have been, resulting in conflicts and failures because they haven't been configured. You can just disable them.

I've love to know why this has happened!

serfraviros · 2014-08-29 17:04:00

CarlD wrote:

To use you network manager, type in the following:
sudo systemctl disable dhpcd.service

Man, that is basic and I did not think of that!. Believe me, I am ashamed at the same time grateful to you.

However this had not happened before, only in this intalación.

As for krb5 the problem persists and I have not found a solution.

Like you I want to know why this happens for a few days in fresh installations.

CarlD · 2014-08-29 19:27:59

Here is the problem (found this after my own bug report was closed due to being a duplicate): https://bugs.archlinux.org/task/41711

jeff story · 2014-08-29 23:12:23

Hey Carl,

I see the bug was closed / fixed. Has this resolved all the issues posted above?

Last edited by jeff story (2014-08-29 23:13:27)

CarlD · 2014-08-29 23:15:03

jeff story wrote:

Hey Carl,
I see the bug was closed / fixed. Has this resolved all the issues posted above?

Well let you know as soon as the update finds its way into the repos. Looks like it should.

Arch Linux

#1 2014-08-28 20:17:24

Various boot failures following fresh installation / ISO generation

#2 2014-08-29 16:14:21

Re: Various boot failures following fresh installation / ISO generation

#3 2014-08-29 16:41:39

Re: Various boot failures following fresh installation / ISO generation

#4 2014-08-29 17:04:00

Re: Various boot failures following fresh installation / ISO generation

#5 2014-08-29 19:27:59

Re: Various boot failures following fresh installation / ISO generation

#6 2014-08-29 23:12:23

Re: Various boot failures following fresh installation / ISO generation

#7 2014-08-29 23:15:03

Re: Various boot failures following fresh installation / ISO generation

Board footer