systemd说"networking.service失败了“，但是网络已经开通了。
systemd说"networking.service失败了“，但是网络已经开通了。
提问于 2021-05-04 16:48:21
通常，我使用openrc运行Gentoo，但是我正在安装Debian 10服务器，并且在理解系统时遇到了一些问题。服务器通过自定义的dracut initrd启动，后者创建了一个绑定的网络接口，然后从iscsi根目录引导。那部分都很好用。在引导时有三个接口，分别是: 192.168.1.0/24、10.0.0.0/24和172.16.0.0/24。
我的(小)问题是系统提供了以下信息：
# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● networking.service loaded failed failed Raise network interfaces我认为这在很大程度上是因为其中一个网络在init的时候很活跃。在Gentoo中，我可以将接口标记为不提供网络服务。systemd是否有类似的概念，或者是否有我错过的设置？同样，所有接口实际上都已经启动并正常工作(2个桥，1个键)--我已经在绑定和桥中剪短了本地接口和NICS。
# ip addr list
[...]
7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP group default qlen 1000
link/ether 24:6e:96:5e:a3:9c brd ff:ff:ff:ff:ff:ff
inet 172.16.0.14/24 brd 172.16.0.255 scope global dynamic bond0
valid_lft 249300sec preferred_lft 249300sec
inet6 fe80::266e:96ff:fe5e:a39c/64 scope link
valid_lft forever preferred_lft forever
[...]
9: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:10:18:64:0f:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.1.14/24 brd 192.168.1.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::210:18ff:fe64:f3c/64 scope link
valid_lft forever preferred_lft forever
10: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:10:18:64:0f:3e brd ff:ff:ff:ff:ff:ff
inet 10.0.0.14/24 brd 10.0.0.255 scope global vmbr1
valid_lft forever preferred_lft forever
inet6 fe80::210:18ff:fe64:f3e/64 scope link
valid_lft forever preferred_lft forever
# ping -I vmbr0 -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 192.168.1.14 vmbr0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=68.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=114 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=61.6 ms提前谢谢你的任何想法。
编辑所要求的其他信息
# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-05-04 08:47:07 CDT; 4h 13min ago
Docs: man:interfaces(5)
Main PID: 1586 (code=exited, status=1/FAILURE)
May 04 08:47:04 proxmox systemd[1]: Starting Raise network interfaces...
May 04 08:47:04 proxmox ifup[1586]: Waiting for a max of 0 seconds for # no delay before a port becomes available to bec
May 04 08:47:05 proxmox ifup[1586]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
May 04 08:47:06 proxmox ifup[1586]: Waiting for a max of 0 seconds for # no delay before a port becomes available to bec
May 04 08:47:07 proxmox ifup[1586]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
May 04 08:47:07 proxmox ifup[1586]: RTNETLINK answers: File exists
May 04 08:47:07 proxmox ifup[1586]: ifup: failed to bring up vmbr1
May 04 08:47:07 proxmox systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
May 04 08:47:07 proxmox systemd[1]: networking.service: Failed with result 'exit-code'.
May 04 08:47:07 proxmox systemd[1]: Failed to start Raise network interfaces.和
# journalctl -u networking.service
-- Logs begin at Tue 2021-05-04 08:46:28 CDT, end at Tue 2021-05-04 12:17:01 CDT. --
May 04 08:47:04 proxmox systemd[1]: Starting Raise network interfaces...
May 04 08:47:04 proxmox ifup[1586]: Waiting for a max of 0 seconds for # no delay before a port becomes available to bec
May 04 08:47:05 proxmox ifup[1586]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
May 04 08:47:06 proxmox ifup[1586]: Waiting for a max of 0 seconds for # no delay before a port becomes available to bec
May 04 08:47:07 proxmox ifup[1586]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
May 04 08:47:07 proxmox ifup[1586]: RTNETLINK answers: File exists
May 04 08:47:07 proxmox ifup[1586]: ifup: failed to bring up vmbr1
May 04 08:47:07 proxmox systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
May 04 08:47:07 proxmox systemd[1]: networking.service: Failed with result 'exit-code'.
May 04 08:47:07 proxmox systemd[1]: Failed to start Raise network interfaces.回答 1
Unix & Linux用户
发布于 2021-05-06 13:39:13
解决了！
我在/etc/网络/接口中定义了两个网关。一旦我删除了除一个之外的所有错误，错误就会被纠正。
# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.页面原文内容由Unix & Linux提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://unix.stackexchange.com/questions/648096
复制相关文章
相似问题
腾讯云开发者
