Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[tv.debian at googlemail.com]

On Wed, 10 Dec 2014 12:23:15 +0200 Andrei POPESCU 
<andreimpopescu at gmail.com> wrote:
 > Control: tag -1 moreinfo
 >
 > On Lu, 01 dec 14, 18:15:22, tv.debian at googlemail.com wrote:
 > >
 > > I did so, when switching to VT 9 the screen is spamed with the systemd
 > > message about "starting LSB". I typed blindly " journalctl -alb" and
 > > noticed that a shell session was indeed active behind the spam wall !
 >
 > Could you also attach the output to this bug?
 >
 > > I can see that the driver "e1000" for the network card is loaded early
 > > without problem.
 > >
 > > I have very few errors, I get:
 > >
 > > "failed to find module 'lp'" and same for 'ppdev' , which in turn 
generates
 > > several fail warnings later on for "systemd load kernel modules".
 >
 > You probably have some modules in /etc/modules or /etc/modprobe.d/ that
 > fail to load.
 >
 > > "Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh"
 > >
 > > There is no /usr/lib/systemd/scripts directory on my system (system 
is mdadm
 > > raid + LUKS). "apt-file search" didn't tell me what package is 
supposed to
 > > provide this "mdadm_env.sh" script, and "find" didn't show it on my 
system
 > > either.
 >
 > This might be bogus, but a little more details about your setup wouldn't
 > hurt.
 >
 > > "ERROR : Duplicate address 192.168.1.2 assigned in the network 
where eth1 is
 > > connected to"
 > >
 > > The last one puzzles me as at the time I booted I was the only 
machine on
 > > the network, and address is assigned from the DHCP server (openwrt) 
through
 > > MAC address reservation.
 > > grepping through /etc for string "192.168.1.2" show one occurrence in
 > > /etc/hosts, one in /etc/samba/lmhosts, and one in backuppc 
configuration.
 > >
 > > arp shows no address or MAC conflict on the network, and my router 
doesn't
 > > either.
 > >
 > > Finally I did "pgrep network" and killed the corresponding PID to 
get the
 > > boot process to resume. It did successfully and the system is fully
 > > functional, including networking, raid and all, which makes me 
think some of
 > > the failure reports may be bogus ?
 >
 > Please attach also your /etc/network/interfaces.
 >
 > Kind regards,
 > Andrei
 > --
 > http://wiki.debian.org/FAQsFromDebianUser
 > Offtopic discussions among Debian users and developers:
 > http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
 > http://nuvreauspam.ro/gpg-transition.txt

Hi, thank you for your attention but since I am not the original 
submitter of this bug and was under the impression that it was "solved" 
(a workaround has been found) I didn't want to add more noise. I will 
open a new bug if I switch back to systemd and still experience the issue.

My "interfaces" file is attached to my first message, together with dhcp 
conf.
I am looking into the modules error, I do have quite a few ones in 
modules.conf, historical heritage and probably unnecessary now, but not 
the ones mentioned in the logs.
I will generate and attach a new boot log when I get a chance to run 
this system with systemd again, maybe this week-end.
This system is LUKS over RAID1 (mdadm), no lvm. /boot, /root and /home 
separate, plus other data and backup arrays that get mounted with a 
combination of pam_mount, key-file and decrypt_derived . /root is 
encrypted too, I get to install plymouth whenever I want to test systemd 
to be able to see the various password prompts. This plymouth thing 
should be a "suggest" for systemd with a comment about Luks encrypted 
partitions, that's another story.

Regarding /usr/lib/systemd/scripts, I don't find it with "apt-file 
search", I don't know what package is supposed to create it. Do you have 
this directory on your (Testing/Sid) systems, I don't have it on any !

Thank you again, you can disregard this reply if this is considered 
irrelevant to the bug, I will open a new one when I can test this again.

Cheers.