| Author |
Message |
Luis_P
|
|
Post subject: Issue at boot [Solved]
 Posted: 04.11.2016, 19:30
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
From some days ago, I have a minor, but annoying, problem at boot. This message appears:
Code:
IPv6: ADDRconf (METDEV_UP): eth0: link is not ready
A start job is running for Raise network interfaces (.... /5 min 12s)
and the system stops its boot until 5 min. 12 sec. have passed. And I have not other solution than wait.
Does anyone know a fix?
Thanks in advance, |
Last edited by Luis_P on 06.11.2016, 12:33; edited 1 time in total
|
| |
|
|
|
 |
|
slh
|
|
|
Post subject: RE: Issue at boot
Posted: 04.11.2016, 21:08
|
|
Joined: 2010-08-25
Posts: 962
Status: Offline
|
|
| The first message is normal, even in a IPv6 network it takes a bit for the IPv6 addresses to propagate, the second one isn't... Please provide your configuration (/etc/network/interfaces, /etc/systemd/network/*) and make sure that you don't have conflicting dæmons trying to configure the same interface under their own umbrella (ifupdown, systemd-networkd, network-manager, connman, ...). |
|
|
| |
|
|
|
|
|
Luis_P
|
|
|
Post subject:
Posted: 05.11.2016, 15:07
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
|
Code:
# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet dhcp
dns-nameservers 87.216.1.65 87.216.6.6
auto eth0
iface eth0 inet dhcp
dns-nameservers 87.216.1.65 87.216.6.6
# ls /etc/systemd/network
#
i.e., /etc/systemd/network is empty.
Concerning dæmons trying to configure the same interface, I've found this:
Code:
# cat /lib/systemd/system/networking.service
[Unit]
Description=Raise network interfaces
Documentation=man:interfaces(5)
DefaultDependencies=no
Wants=network.target
After=local-fs.target network-pre.target apparmor.service systemd-sysctl.service systemd-modules-load.service
Before=network.target shutdown.target network-online.target
Conflicts=shutdown.target
[Install]
WantedBy=multi-user.target
WantedBy=network-online.target
[Service]
Type=oneshot
EnvironmentFile=-/etc/default/networking
ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle'
ExecStart=/sbin/ifup -a --read-environment
ExecStop=/sbin/ifdown -a --read-environment
RemainAfterExit=true
TimeoutStartSec=5min
#
apart from this, I've been not able to find any relevant. Please, give me more concrete test if needed.
Thanks for your support. |
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject:
Posted: 05.11.2016, 19:14
|
|
Joined: 2010-08-25
Posts: 962
Status: Offline
|
|
| Two interfaces configured for DHCP (unless augmented with quite a lot of special orchestration regarding default routes, routing metrics, etc.) is pretty much always an error, with quite dire consequences. Comment out one of them and probably change "auto" to "allow-hotplug" for the remaining one. |
|
|
| |
|
|
|
|
|
Luis_P
|
|
|
Post subject:
Posted: 06.11.2016, 12:35
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
Changes made and solved! 
Thank you very much! |
|
|
| |
|
|
|
|
|
|
