gash thanks Mantas. I am so stupid do not realise that it was on DHCP the first
interface. many thanks !!!
- Okay, It's corrected. It seems much better!!!
# systemd-analyze blame
4.918s dev-mapper-sysvg\x2droot.device
4.152s keyboard-setup.service
3.016s apt-daily.service
2.354s snapd.service
1.829s lxd-containers.service
1.825s lvm2-monitor.service
1.628s kdump-tools.service
1.300s systemd-networkd-wait-online.service
My situation is that: our host was bootstrapped via preseed with a bash
script_post_install to create the `/etc/network/interfaces` file.
Now, It would be possible to generate the "/etc/netplan/01-netcfg.yaml" using
"/etc/network/interfaces" as a principale file of confs.
I know at the beggining we used "netplan ifupdown-migrate"? but this command
seems not exist any more to the latest Bionic. 😞
Many Thanks!
-r
________________________________
De : Mantas MikulÄ—nas <graw...@gmail.com>
Envoyé : lundi, 16 juillet 2018 07:37
Cc : Systemd
Objet : Re: [systemd-devel] systemd-networkd-wait-online.service take too much
time
On Mon, Jul 16, 2018 at 1:13 AM Renato _
<tutelacooldo...@hotmail.com<mailto:tutelacooldo...@hotmail.com>> wrote:
hello, am working to get my Bionic image working perfectly on my BareMetal.
which is working perfectly fine on Xenial. But on Bionic I am facing to
boot-latency issue with systemd. I googled it and I do not find interesting
thing.
Can someone assist me to get a better troubleshoot?
Many Thanks!
-r
# cat /etc/issue
Ubuntu 18.04 LTS \n \l
# systemd-analyze blame
2min 43ms systemd-networkd-wait-online.service
30.970s apt-daily.service
4.900s dev-mapper-sysvg\x2droot.device
4.629s keyboard-setup.service
1.760s systemd-journal-flush.service
1.300s lvm2-monitor.service
1.144s kdump-tools.service
# cat /etc/network/interfaces
auto enp130s0f0
iface enp130s0f0 inet manual
bond-master bond0
auto enp130s0f1
iface enp130s0f1 inet manual
bond-master bond0
auto bond0
iface bond0 inet static
# Sleep required for XXV710-DA2 (25G) CSI-5441
# N/A
gateway 10.88.112.1
address 10.88.112.44
netmask 255.255.254.0
bond_mode 802.3ad
bond_xmit_hash_policy layer3+4
bond_miimon 100
bond_lacp_rate fast
slaves enp130s0f0 enp130s0f1
dns-search myworld.net<http://myworld.net>
dns-nameservers 8.8.8.8 8.8.4.4
# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp130s0f0:
dhcp4: yes
Your systemd-networkd (netplan) configuration tries to run DHCP on
enp130s0f0... but your ifupdown (network/interfaces) configuration puts the
same enp130s0f0 under a bond interface. Why do you have both? It makes no sense
to run IP directly on a bonded interface.
--
Mantas MikulÄ—nas
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
