Bug#916689: systemd: login at console hangs after "Last login..." displayed, ssh hangs as well

[Michael Biebl]

On Tue, 18 Dec 2018 12:20:06 +0100 Michael Biebl <biebl at debian.org> wrote:
> Am 18.12.2018 um 12:09 schrieb Raphael Manfredi:
> > Quoting Michael Biebl:
> > : What happens if you boot into emergency mode (add emergency to the
> > : kernel command line)?
> > : This will start a very minimal system without any networking or started
> > : services. Can you successfully login?
> > : 
> > : What happens if you boot into rescue mode (add rescue to the kernel
> > : command line)?
> > : This will boot into a minimal system with a few services like
> > : networking.service enabled.
> > : 
> > : What's the output of "ip a" in this case?
> > 
> > In emergency mode, no network, as expected:
> > 
> > 	$ cat /root/ip.a-emergency
> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> >        valid_lft forever preferred_lft forever
> >     inet6 ::1/128 scope host 
> >        valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> >     link/ether 74:d0:2b:9d:5e:e4 brd ff:ff:ff:ff:ff:ff
> > 
> > In resue mode, NO NETWORK!
> > 
> > 	$ cat /root/ip.a-rescue
> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> >        valid_lft forever preferred_lft forever
> >     inet6 ::1/128 scope host 
> >        valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> >     link/ether 74:d0:2b:9d:5e:e4 brd ff:ff:ff:ff:ff:ff
> > 
> > I understand this is not the expected situation, but how is systemd
> > configuring my network?  Who handles the /etc/network/interfaces file?
> 
> systemd is not configuring your network, ifupdown is in your case.
> You use a type auto interface, so networking.service should be
> responsible for that.
> systemctl status networking.service should give you the state of this
> service.

Hi Guus,

since this issue involves ifupdown, maybe you have an idea what's going
wrong.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190108/d05b5377/attachment.sig>