我们正尝试向OVH服务器添加其他IP,并且在更改Yaml后每当应用命令“ netplan apply”时,服务器就会完全脱机。网络已关闭。这种情况会持续约10-15分钟,然后再自行恢复。
当我运行命令以检查systemd-networked的状态时,我得到以下信息:
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2018-12-02 05:10:18 UTC; 26min ago
Docs: man:systemd-networkd.service(8)
Main PID: 40782 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 8601)
CGroup: /system.slice/systemd-networkd.service
└─40782 /lib/systemd/systemd-networkd
Dec 02 05:10:18 servername systemd-networkd[40782]: eno1: Gained IPv6LL
Dec 02 05:10:18 servername systemd-networkd[40782]: Enumeration completed
Dec 02 05:10:18 servername systemd[1]: Started Network Service.
Dec 02 05:10:18 servername systemd-networkd[40782]: eno2: Could not find udev device: No such device
Dec 02 05:10:18 servername systemd-networkd[40782]: eno2: Failed
Dec 02 05:10:18 servername systemd-networkd[40782]: Could not add new link, ignoring: No such device
Dec 02 05:10:18 servername systemd-networkd[40782]: lo: Link is not managed by us
Dec 02 05:10:18 servername systemd-networkd[40782]: eno1: DHCPv4 address [ip address]/24 via <my server ip address>
Dec 02 05:10:18 ns536095 systemd-networkd[40782]: eno1: Configured
Dec 02 05:10:18 ns536095 systemd-networkd[40782]: eth0: Interface name change detected, eth0 has been renamed to eno2.
似乎它正在尝试搜索eno2,但它不存在,这导致网络超时并完全掉线。我们所有的IP都设置在eno1上。尽管服务器确实具有该网卡,但eno2没有任何内容。
我该如何解决这个问题?试图找出最长的时间。确认yaml文件格式正确,如下所示。
network:
version: 2
ethernets:
eno1:
dhcp4: true
addresses: [<Main IP>, <additional ip>]
任何帮助将不胜感激。
答案 0 :(得分:0)
我也遇到类似的问题,但是10到15分钟后,界面不会自动返回。 我有桥接接口的问题...
bridges:
br0:
addresses:
- 10.0.1.1/16
- 172.16.0.1/21
interfaces:
- enp2s0f0
- enp2s0f1
- enp2s0f2
- enp2s0f3
答案 1 :(得分:0)
我们发现了类似的问题,并发现将连接指定为“关键”可以解决此问题:
ethernets:
eno1:
dhcp4: false
addresses: [<Main IP>, <additional ip>]
critical: true
遗憾的是,“关键”标志的文档目前相当稀少,因此很难判断将连接指定为“关键”是否有任何缺点,尤其是对于非 DHCP 端口。