我们最近设置了一个 FreeIPA 服务器。我们将其用于中央用户管理、DNS 和 CA。除了一个例外，它一直运行良好。
使用此 FreeIPA 服务器进行身份验证的一些工作站位于数千英里之外。往返时间约为 300 毫秒。我们注意到这些机器上出现了一些不可预测的身份验证失败。一秒钟后，他们将无法对登录尝试进行身份验证，然后他们将在几秒钟后成功进行身份验证。我们认为延迟是罪魁祸首。
有没有办法延长客户端的超时时间？或者，我们一直在考虑在这些工作站所在的位置设置一个 IPA 副本。高延迟链接将如何影响副本与主服务器进行复制的能力？
我正在尝试通过使用 Ansible 生成 /etc/exports 文件来动态配置系统中的多个 NFS 服务器。我希望能够使用 jinja2 模板来做到这一点。这是我根据导出列表无法确定的 jinja2 模板。
我在我的 nfs 角色中定义了以下变量：
site_nfs_servers: ['ansibletarget1', 'ansibletarget2']
exports:
- server: "ansibletarget1"
shares:
- path: "/my/first/share/path"
client: "*"
options: "rw,sync"
- path: "/my/second/share/path"
client: "*"
options: "rw,sync,root_squash"
- server: "ansibletarget2"
shares:
- path: "/another/shared/path/different/server"
client: "*"
options: "ro,sync"
然后我有以下 ansible play 来生成模板：
- name: Generate the exports file.
template:
src: exports.j2
dest: /etc/exports
owner: root
group: root
mode: '0750'
我的模板目前看起来像这样：
{% for export in exports %}
{% if ansible_hostname in export.server %}
{% for share in shares %}
{{ share.path }} {{ share.client }} {{ share.options }}
{% endfor %}
{% endif %}
{% endfor %}
我认为我离正确的模板结构还差得很远。到底是如何遍历这个列表的？
我有两个 Linux 路由器 (RHEL 7) 参与了由 keepalived 软件包版本 2.0.20 提供的冗余 VRRP 配置。这两个路由器曾经运行 RHEL 6 和 keepalived 版本 2.0.16，但我们最近将它们升级到上述版本。
在我们升级之前，我有一个可以在备份路由器上运行的脚本，它会导致路由器接管为主路由器。该脚本将收集当前主路由器的优先级值，然后将其自身的优先级提高 1，然后重新启动 keepalived 服务。这将导致备份路由器接管为主。
该脚本将通过发出以下命令来收集当前主路由器的值：
kill -s $(keepalived --signum=DATA) $(cat /var/run/keepalived.pid)
vrrpPriority='more /tmp/keepalived.data | grep -m1 "Master priority" | awk '{print $4}''
现在我们已经升级了，看起来第一个命令不再做任何事情了。该命令似乎执行没有错误，但我从未在 /tmp/keepalived.data 中获得生成的文件。所以第二个命令失败，因为该文件不存在。
是否有更好或不同的方法来收集当前主路由器的优先级值？
另一个区别是，当我们在 RHEL 6 中运行时，keepalived 作为新贵脚本运行，而今天 keepalived 作为 systemd 服务运行。keepalived 的所有其他方面似乎工作正常。
我们的网络使用 pimd 支持许多多播流。只有当我们在 pimd.conf 文件的 phyint 部分中使用“altnet multicast_source_ip masklen 24”语句时，许多（但不是全部）多播流才会流动。当某些网络设备根据全天的特定事件启动/关闭时，这些多播流会动态添加或删除。在一天中，pimd.conf 文件可能会多次添加或删除这些 altnet 语句。每次发生这种情况时，我们都必须发出“pimd -l”命令才能使更改生效。每次发出此命令时，都会重新加载守护程序并擦除 mroute 表。经过短暂的重新发现后，mroutes 慢慢地回到多播路由表中。
我想知道是否可以添加/删除 altnet 指令而无需编辑 pimd.conf 文件并发出 pimd -l 命令重新加载配置。换句话说，它们可以在运行时添加或删除吗？或者在不影响任何现有多播流/路由的情况下添加？
我正在尝试在树莓派 3 b+ 上配置 openvpn 客户端。树莓派正在运行 CentOS 7 armhfp。
我从 EPEL 存储库中为 armhfp 平台安装了 openvpn。我已将我的配置和关联的密钥和身份验证文件放在 /etc/openvpn
[root@raspberrypi openvpn]# ll
total 24
drwxr-x---. 2 root openvpn 4096 Jan 1 1970 client
-rwxrwxrwx. 1 root root 2186 Jan 25 22:17 mullvad_ca.crt
-rwxrwxrwx. 1 root root 985 Jan 1 1970 mullvad_us.conf
-rwxrwxrwx. 1 root root 19 Jan 25 22:17 mullvad_userpass.txt
drwxr-x---. 2 root openvpn 4096 Nov 18 14:06 server
-rwxrwxrwx. 1 root root 1301 Jan 25 22:17 update-resolv-conf
[root@raspberrypi openvpn]#
我正在尝试使用以下命令启动服务：systemctl start openvpn-client@mullvad_us
当我这样做时，它会以以下状态失败：
[root@raspberrypi openvpn]# systemctl status openvpn-client@mullvad_us -l
● openvpn-client@mullvad_us.service - OpenVPN tunnel for mullvad_us
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2020-01-26 01:17:19 UTC; 3h 10min ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 994 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config %i.conf (code=exited, status=1/FAILURE)
Main PID: 994 (code=exited, status=1/FAILURE)
Jan 26 01:17:19 raspberrypi systemd[1]: Starting OpenVPN tunnel for mullvad_us...
Jan 26 01:17:19 raspberrypi openvpn[994]: Options error: In [CMD-LINE]:1: Error opening configuration file: mullvad_us.conf
Jan 26 01:17:19 raspberrypi openvpn[994]: Use --help for more information.
Jan 26 01:17:19 raspberrypi systemd[1]: openvpn-client@mullvad_us.service: main process exited, code=exited, status=1/FAILURE
Jan 26 01:17:19 raspberrypi systemd[1]: Failed to start OpenVPN tunnel for mullvad_us.
Jan 26 01:17:19 raspberrypi systemd[1]: Unit openvpn-client@mullvad_us.service entered failed state.
Jan 26 01:17:19 raspberrypi systemd[1]: openvpn-client@mullvad_us.service failed.
似乎无法读取我的 mulvad_us.conf 文件。我已授予它完整的 777 权限，并尝试将其所有权更改为 openvpn:openvpn。我还禁用了 selinux，以防万一出现问题。我也将文件移动到 /etc/openvpn/client 也没有成功。
如果我从命令行启动 openvpn 它工作正常。我将运行命令：“nohup openvpn --config /etc/openvpn/mullvad_us.conf &”，隧道会正确构建和形成。
我只是无法让它在启动时自动出现。我打算以无头方式运行它，并且不希望每次打开设备时都必须通过 ssh 进入设备只是为了启动 vpn 隧道。
我在网上看到文章说要在 /etc/default/openvpn 编辑文件，但由于某种原因该文件不存在，我不禁认为这是由于我正在运行的 CentOS 的风格。在这一点上，我很困惑。任何帮助将不胜感激。
我正在尝试在 RHEL 6.9 VM 上安装 FreeRADIUS 服务器。此 VM 在 FIPS 模式下运行。我遇到了此处发现的 Red Hat 错误报告中描述的问题。
根据 2015 年 3 月的错误报告，RADIUS 协议需要 MD5 支持。因此 FIPS 模式不支持 FreeRADIUS（和 RADIUS）。
我希望在自该错误报告以来发生的 3 年中，我可以实施修复或解决方法来解决此问题。不幸的是，根据 DISA STIG 要求，我只能在 FIPS 模式下运行。有人知道让 FreeRADIUS 在以 FIPS 模式运行的机器上工作的方法吗？
我有一台用作路由器的 Linux 机器。它已安装 quagga 并启用了 IP 转发。它与 3925 Cisco 路由器形成 OSPF 邻接关系。
我被要求确保这台 Linux 机器（运行 Redhat 6.8）不会发送任何 ICMP Unreachable 通知。我知道在 Cisco 路由器上，我只需在任何需要它的接口上设置“no icmp unreachable”。但是我怎么能确定它们在 Linux 机器上被禁用了呢？
我还被要求确保没有从路由器发送“ICMP 掩码回复”消息。同样，我知道在 Cisco 路由器上会使用“no ip mask-reply”命令。Redhat 中是否有同等类型的设置？
谢谢你的帮助。
我有一台机器位于无法访问互联网的安全环境中。我有一个 CentOS 的基本负载和一些额外的 RPM。这包括基本的 PERL 安装，没有额外的模块。它也没有安装 GCC，所以我不能手动安装新模块，也不能使用 CPAN 安装它们。因此，我需要一个纯粹的 Perl 解决方案。
我被要求创建一个 Perl 脚本，该脚本将验证机器是否安装了特定的 RPM 列表，并且它们是特定版本或更高版本。
这是我到目前为止所拥有的：
#!/usr/bin/perl
use strict;
use warnings;
# This is the list of RPMs to look for on the machine.
my @RPMs = ("bwm-ng",
"celt051",
"device-mapper-multipath",
"device-mapper-multipath-libs",
"dhcp",
"dhcp-common",
"ebtables",
"freeglut",
"glusterfs-api",
"glusterfs-libs",
"gnutls-utils",
"gpm",
"hmaccalc",
"iftop",
"iperf",
"ipsec-tools",
"iptraf",
"iscsi-initiator-utils",
"libsysfs",
"lm_sensors",
"lm_sensors-libs",
"log4cpp",
"lrzsz",
"lzop",
"mcsctrans",
"minicom",
"nc",
"netcf-libs",
"net-snmp",
"net-snmp-libs",
"net-snmp-utils",
"omping",
"perl-AppConfig",
"perl-Pod-POM",
"perl-Template-Toolkit",
"pimd",
"python-lxml",
"quagga",
"radvd",
"smcroute",
"usbredir",
"yajl");
# These are the RPM versions that they should be equal to or newer than.
my @RPMVersions = ("bwm-ng-0.6-6.el6.2.x86_64",
"celt051-0.5.1.3-0.el6.x86_64",
"device-mapper-multipath-0.4.9-87.el6.x86_64",
"device-mapper-multipath-libs-0.4.9-87.el6.x86_64",
"dhcp-4.1.1-49.P1.el6.centos.x86_64",
"dhcp-common-4.1.1-49.P1.el6.centos.x86_64",
"ebtables-2.0.9-6.el6.x86_64",
"freeglut-2.6.0-1.el6.x86_64",
"glusterfs-api-3.4.0.57rhs-1.el6_5.x86_64",
"glusterfs-libs-3.4.0.57rhs-1.el6_5.x86_64",
"gnutls-utils-2.8.5-18.el6.x86_64",
"gpm-1.20.6-12.el6.x86_64",
"hmaccalc-0.9.12-2.el6.x86_64",
"iftop-1.0-0.7.pre4.el6.x86_64",
"iperf-2.0.5-11.el6.x86_64",
"ipsec-tools-0.8.0-25.3.x86_64",
"iptraf-3.0.1-14.el6.x86_64",
"iscsi-initiator-utils-6.2.0.873-14.el6.x86_64",
"libsysfs-2.1.0-7.el6.x86_64",
"lm_sensors-3.1.1-17.el6.x86_64",
"lm_sensors-libs-3.1.1-17.el6.x86_64",
"log4cpp-1.0-13.el6_5.1.x86_64",
"lrzsz-0.12.20-27.1.el6.x86_64",
"lzop-1.02-0.9.rc1.el6.x86_64",
"mcsctrans-0.3.1-4.el6.x86_64",
"minicom-2.3-6.1.el6.x86_64",
"nc-1.84-24.el6.x86_64",
"netcf-libs-0.2.4-3.el6.x86_64",
"net-snmp-5.5-54.el6.x86_64",
"net-snmp-libs-5.5-54.el6.x86_64",
"net-snmp-utils-5.5-54.el6.x86_64",
"omping-0.0.4-1.el6.x86_64",
"perl-AppConfig-1.66-6.el6.x86_64",
"perl-Pod-POM-0.25-2.el6.x86_64",
"perl-Template-Toolkit-2.22-5.el6.x86_64",
"pimd-2.3.0-1.x86_64",
"python-lxml-2.2.3-1.1.el6.x86_64",
"quagga-0.99.23.1-2014082501.x86_64",
"radvd-1.6-1.el6.x86_64",
"smcroute-2.0.0-0.x86_64",
"usbredir-0.5.1-2.el6.x86_64",
"yajl-1.0.7-3.el6.x86_64");
my $RPMname; #This reprepsents an individual RPM name within the @RPMs array.
foreach $RPMname (@RPMs){ # Loop through the @RPMs array and query the RPM database for each RPM.
my $cmd = "rpm -qa | grep " . $RPMname;
my @cmdResults = `$cmd`;
if (! @cmdResults){
print "\tMissing RPM: " . $RPMname . "\n\n"; # If the RPM isn't installed; inform the user.
} else {
foreach(@cmdResults){
print "\t" . $_ . "\n"; # Print the version of the RPM that's currently installed.
# Compare the RPM version that's installed with the corresponding version that should be installed
# as listed in the @RPMVersions array.
# write some magic here. <------
}
}
}
exit(0);
我发现似乎是一个可能的解决方案，但我似乎无法弄清楚如何调整适合我的场景的代码。
见这里：http ://www.perlmonks.org/bare/?node=240384
由于我上面提到的限制，我不能使用 RPM::VersionSort 或其他几个与 RPM 相关的模块。
任何帮助将不胜感激。
谢谢！
我有一台带有六个网络接口的迷你电脑，运行 CentOS 7.2 和内核 3.10，安装最少。
我想将我的接口命名为 net0-net5。为此，我正在尝试遵循此处提到的建议：http ://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
在上面的文章中，它指出为了重命名我的接口，我需要创建 .link 文件并将它们放在 /etc/systemd/network 中。这是一种新的方式，需要根据 systemd-networkd 重命名其网络接口。
但是，我发现 systemd-networkd 服务将无法启动，并且如果没有运行此服务，我认为我根本无法命名我的接口。
请参阅以下内容：
systemctl --failed -l
UNIT LOAD ACTIVE SUB DESCRIPTION
<E2><97><8F> systemd-networkd.service loaded failed failed Network Service
<E2><97><8F> systemd-networkd.socket loaded failed failed networkd rtnetlink so
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
systemctl status systemd-networkd -l
��● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Tue 2011-05-10 01:45:45 UTC; 32min ago
Docs: man:systemd-networkd.service(8)
Process: 317 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=226/NAMESPACE)
Main PID: 317 (code=exited, status=226/NAMESPACE)
May 10 01:45:45 localhost systemd[1]: Unit systemd-networkd.service entered failed state.
May 10 01:45:45 localhost systemd[1]: systemd-networkd.service failed.
May 10 01:45:45 localhost systemd[1]: systemd-networkd.service has no holdoff time, scheduling restart.
May 10 01:45:45 localhost systemd[1]: start request repeated too quickly for systemd-networkd.service
May 10 01:45:45 localhost systemd[1]: Failed to start Network Service.
May 10 01:45:45 localhost systemd[1]: Unit systemd-networkd.service entered failed state.
May 10 01:45:45 localhost systemd[1]: systemd-networkd.service failed.
May 10 01:45:45 localhost systemd[1]: start request repeated too quickly for systemd-networkd.service
May 10 01:45:45 localhost systemd[1]: Failed to start Network Service.
May 10 01:45:45 localhost systemd[1]: systemd-networkd.service failed.
systemctl status systemd-networkd.socket -l
��● systemd-networkd.socket - networkd rtnetlink socket
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.socket; enabled; vendor preset: disabled)
Active: failed (Result: service-failed-permanent) since Tue 2011-05-10 01:45:45 UTC; 39min ago
Docs: man:systemd-networkd.service(8)
man:rtnetlink(7)
Listen: route 273 (Netlink)
May 10 01:45:45 localhost systemd[1]: Unit systemd-networkd.socket entered failed state.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
我应该提到 NetworkManager 没有安装，DHClient 也没有安装。由于这是一个最小的安装，我想我会展示正在运行的进程：
ps -ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:09 /init
2 ? S 0:00 [kthreadd]
3 ? S 0:00 [ksoftirqd/0]
5 ? S< 0:00 [kworker/0:0H]
7 ? S 0:00 [migration/0]
8 ? S /0]
10 ? S 0:00 [rcuob/1]
11 ? S 0:00 [rcuob/2]
12 ? S 0:00 [rcuob/3]
13 ? S 0:00 [rcu_sched]
14 ? S 0:00 [rcuos/0]
15 ? S 0:00 [rcuos/1]
16 ? S 0:00 [rcuos/2]
17 ? S 0:00 [rcuos/3]
18 ? S 0:00 [watchdog/0]
19 ? S 0:00 [watchdog/1]
20 ? S 0:00 [migration/1]
21 ? S 0:00 [ksoftirqd/1]
23 ? S< 0:00 [kworker/1:0H]
24 ? S< 0:00 [khelper]
25 ? S 0:00 [kdevtmpfs]
26 ? S< 0:00 [netns]
27 ? S< 0:00 [perf]
28 ? S< 0:00 [writeback]
29 ? S< 0:00 [kintegrityd]
30 ? S< 0:00 [bioset]
31 ? S< 0:00 [kblockd]
32 ? S< 0:00 [md]
33 ? S 0:00 [kworker/0:1]
34 ? S 0:00 [kworker/1:1]
38 ? S 0:00 [khungtaskd]
39 ? S 0:00 [kswapd0]
40 ? SN 0:00 [ksmd]
41 ? SN 0:00 [khugepaged]
42 ? S 0:00 [fsnotify_mark]
43 ? S< 0:00 [crypto]
51 ? S< 0:00 [kthrotld]
54 ? S< 0:00 [kmpath_rdacd]
55 ? S 0:00 [kworker/1:2]
56 ? S< 0:00 [kpsmoused]
57 ? S 0:00 [kworker/0:2]
58 ? S< 0:00 [ipv6_addrconf]
77 ? S< 0:00 [deferwq]
89 ? Ss 0:00 /usr/lib/systemd/systemd-journald
96 ? S< 0:00 [rpciod]
109 ? S 0:00 [kauditd]
110 ? Ss 0:00 /usr/sbin/lvmetad -f
131 ? Ss 0:00 /usr/lib/systemd/systemd-udevd
160 ? S< 0:00 [events_power_ef]
164 ? S< 0:00 [ata_sff]
166 ? S 0:17 [kworker/u8:3]
167 ? S 0:00 [scsi_eh_0]
169 ? S< 0:00 [scsi_tmf_0]
172 ? S 0:00 [scsi_eh_1]
173 ? S< 0:00 [scsi_tmf_1]
174 ? S 0:00 [kworker/u8:4]
175 ? S 0:00 [scsi_eh_2]
176 ? S< 0:00 [scsi_tmf_2]
177 ? S 0:00 [scsi_eh_3]
178 ? S< 0:00 [scsi_tmf_3]
181 ? S< 0:00 [kvm-irqfd-clean]
208 ? S< 0:00 [kworker/0:1H]
209 ? S< 0:00 [kworker/1:1H]
213 ? S 0:00 [jbd2/sda1-8]
214 ? S< 0:00 [ext4-rsv-conver]
215 ? S< 0:00 [ext4-unrsv-conv]
235 ? S<sl 0:00 /sbin/auditd -n
260 ? SNs 0:00 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/et
262 ? SNsl 0:00 /usr/libexec/rtkit-daemon
263 ? Ss 0:00 /bin/dbus-daemon --system --address=systemd: --nofork
268 ? Ss 0:00 avahi-daemon: running [linux.local]
269 ? Ssl 0:00 /usr/bin/python -Es /usr/sbin/firewalld --nofork --no
270 ? Ss 0:00 /usr/lib/systemd/systemd-logind
279 ? Ss 0:00 /usr/sbin/gpm -m /dev/input/mice -t exps2
280 ? Ss 0:00 /usr/sbin/irqbalance --foreground
281 ? Ssl 0:00 /usr/sbin/rsyslogd -n
282 ? Ssl 0:00 /usr/sbin/gssproxy -D
284 ? S 0:00 avahi-daemon: chroot helper
500 ? Ss 0:00 /usr/sbin/sshd -D
503 ? Ssl 0:00 /usr/bin/python -Es /usr/sbin/tuned -l -P
510 ? Ssl 0:00 /usr/sbin/libvirtd
512 ? Ss 0:00 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.
519 ? Ss 0:00 /usr/sbin/crond -n
546 tty1 Ss+ 0:00 /sbin/agetty --noclear tty1 linux
547 ? Ss 0:00 login -- mini
976 ? Ssl 0:00 /usr/lib/polkit-1/polkitd --no-debug
1022 ? S 0:00 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/de
1023 ? S 0:00 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/de
1025 ttyS0 Ss 0:00 -bash
1057 ttyS0 S 0:00 su -
1058 ttyS0 S 0:00 -bash
1093 ? Ss 0:00 /usr/sbin/anacron -s
15547 ttyS0 R+ 0:00 ps -ax
我发现有趣的一件事是 /init 被列为 PID 1 但 ps -p 1 -o comm= 表明我正在运行 systemd。还：
[root@localhost tmp]# pstree
systemd-+-agetty
|-alsactl
|-anacron
|-auditd---{auditd}
|-avahi-daemon---avahi-daemon
|-crond
|-dbus-daemon
|-dnsmasq---dnsmasq
|-firewalld---{firewalld}
|-gpm
|-gssproxy---5*[{gssproxy}]
|-irqbalance
|-libvirtd---15*[{libvirtd}]
|-login---bash---su---bash---pstree
|-lvmetad
|-polkitd---5*[{polkitd}]
|-rsyslogd---2*[{rsyslogd}]
|-rtkit-daemon---2*[{rtkit-daemon}]
|-sshd
|-systemd-journal
|-systemd-logind
|-systemd-udevd
|-tuned---4*[{tuned}]
`-xinetd
任何关于我应该如何让 systemd-networkd.service 和 systemd-networkd.socket 成功加载的想法将不胜感激。
我在具有 6 个以太网端口的小型迷你 PC 上安装了最小的 CentOS 7.2。我选择从安装中排除 NetworkManager，因为我更喜欢使用基本网络服务或切换到使用 systemd-networkd。但是，我似乎无法启动网络或 systemd-networkd 服务。
systemctl status network.service -l
��● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed (Result: exit-code) since Tue 2011-05-10 00:01:22 UTC; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 25591 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
May 10 00:01:22 localhost network[25591]: RTNETLINK answers: File exists
May 10 00:01:22 localhost network[25591]: RTNETLINK answers: File exists
May 10 00:01:22 localhost network[25591]: RTNETLINK answers: File exists
May 10 00:01:22 localhost network[25591]: RTNETLINK answers: File exists
May 10 00:01:22 localhost network[25591]: RTNETLINK answers: File exists
May 10 00:01:22 localhost network[25591]: RTNETLINK answers: File exists
May 10 00:01:22 localhost systemd[1]: network.service: control process exited, code=exited status=1
May 10 00:01:22 localhost systemd[1]: Failed to start LSB: Bring up/down networking.
May 10 00:01:22 localhost systemd[1]: Unit network.service entered failed state.
May 10 00:01:22 localhost systemd[1]: network.service failed.
journalctl -xe -u network.service
-- Logs begin at Tue 2011-05-10 00:00:40 UTC, end at Tue 2011-05-10 00:02:35 UTC. --
May 10 00:00:44 localhost systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has begun starting up.
May 10 00:00:44 localhost network[334]: Bringing up loopback interface: [ OK ]
May 10 00:00:45 localhost network[334]: Bringing up interface eth0: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device eth
0 does not seem to be present, delaying initialization.
May 10 00:00:45 localhost network[334]: [FAILED]
May 10 00:00:45 localhost network[334]: Bringing up interface eth1: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device eth
1 does not seem to be present, delaying initialization.
May 10 00:00:45 localhost /etc/sysconfig/network-scripts/ifup-eth[702]: Device eth1 does not seem to be present, delaying initializa
tion.
May 10 00:00:45 localhost network[334]: [FAILED]
May 10 00:00:45 localhost systemd[1]: network.service: control process exited, code=exited status=1
May 10 00:00:45 localhost systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
May 10 00:00:45 localhost systemd[1]: Unit network.service entered failed state.
May 10 00:00:45 localhost systemd[1]: network.service failed.
May 10 00:01:20 localhost systemd[1]: Starting LSB: Bring up/down networking...
这是 dmesg | grep e1000e
[root@localhost ~]# dmesg | grep eth
[ 9.194339] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:01:05:0f:2a:a0
[ 9.202239] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 9.209127] e1000e 0000:00:19.0 eth0: MAC: 7, PHY: 8, PBA No: FFFFFF-0FF
[ 9.320640] e1000e 0000:04:00.0 eth1: registered PHC clock
[ 9.320643] e1000e 0000:04:00.0 eth1: (PCI Express:2.5GT/s:Width x1) 00:30:59:08:18:53
[ 9.320645] e1000e 0000:04:00.0 eth1: Intel(R) PRO/1000 Network Connection
[ 9.320734] e1000e 0000:04:00.0 eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 9.453298] e1000e 0000:05:00.0 eth2: registered PHC clock
[ 9.458777] e1000e 0000:05:00.0 eth2: (PCI Express:2.5GT/s:Width x1) 00:30:59:08:18:54
[ 9.466673] e1000e 0000:05:00.0 eth2: Intel(R) PRO/1000 Network Connection
[ 9.473608] e1000e 0000:05:00.0 eth2: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 9.609123] e1000e 0000:06:00.0 eth3: registered PHC clock
[ 9.609126] e1000e 0000:06:00.0 eth3: (PCI Express:2.5GT/s:Width x1) 00:30:59:08:18:55
[ 9.609128] e1000e 0000:06:00.0 eth3: Intel(R) PRO/1000 Network Connection
[ 9.609203] e1000e 0000:06:00.0 eth3: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 9.704211] e1000e 0000:07:00.0 eth4: registered PHC clock
[ 9.704214] e1000e 0000:07:00.0 eth4: (PCI Express:2.5GT/s:Width x1) 00:30:59:08:18:56
[ 9.704216] e1000e 0000:07:00.0 eth4: Intel(R) PRO/1000 Network Connection
[ 9.704291] e1000e 0000:07:00.0 eth4: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 9.816322] e1000e 0000:08:00.0 eth5: registered PHC clock
[ 9.816324] e1000e 0000:08:00.0 eth5: (PCI Express:2.5GT/s:Width x1) 00:01:05:0f:2a:a1
[ 9.816326] e1000e 0000:08:00.0 eth5: Intel(R) PRO/1000 Network Connection
[ 9.816483] e1000e 0000:08:00.0 eth5: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[root@localhost ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
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: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN
link/gre 0.0.0.0 brd 0.0.0.0
3: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: enp0s25: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:01:05:0f:2a:a0 brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:30:59:08:18:53 brd ff:ff:ff:ff:ff:ff
6: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:30:59:08:18:54 brd ff:ff:ff:ff:ff:ff
7: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:30:59:08:18:55 brd ff:ff:ff:ff:ff:ff
8: enp7s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:30:59:08:18:56 brd ff:ff:ff:ff:ff:ff
9: enp8s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:01:05:0f:2a:a1 brd ff:ff:ff:ff:ff:ff
10: eth_bri: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether ae:75:23:c7:e3:b6 brd ff:ff:ff:ff:ff:ff
inet 129.193.148.1/24 brd 129.193.148.255 scope global eth_bri
valid_lft forever preferred_lft forever
inet6 fe80::ac75:23ff:fec7:e3b6/64 scope link
valid_lft forever preferred_lft forever
journctl -u network.service 似乎暗示没有 eth0，但从 dmesg 显示有 eth0 到 eth5。然而; 当我发出 ip addr 时，您可以看到它们都已重命名为 systemd-udevd 提供的新样式；enp0s25...等。
这里有另一个线程Can't start CentOS 7 "network" service这意味着 dhcpclient 服务可能会妨碍您。该线程的答案建议禁用 dhcpclient 服务。就我而言，我没有运行 dhcpclient。
[root@localhost ~]# ps -ef | grep dhc
root 2506 23576 0 00:23 ttyS0 00:00:00 grep --color=auto dhc
[root@localhost ~]#