一个执着于技术的公众号

今天遇到一个神奇的现象，我对CentOS 8系统做初始化之后再重启系统，发现系统不能通过NetworkManager获取DHCP IP了

查了系统日志发现是：

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.2608] device (ens33): state change: ip-config -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191847.2614] device (ens33): Activation: failed for connection 'ens33'

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.2615] device (ens33): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.2718] device (ens33): Activation: starting connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad)

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.2718] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.2721] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.3385] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.3387] dhcp4 (ens33): activation: beginning transaction (timeout in 45 seconds)

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191847.3387] device (ens33): failure to start DHCP: failed to set DHCP hostname: Invalid argument

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.3387] device (ens33): state change: ip-config -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191847.3392] device (ens33): Activation: failed for connection 'ens33'

Apr 30 04:24:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191847.3393] device (ens33): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9089] device (ens33): Activation: starting connection 'ens33' (e75e0548-afe3-4900-8233-74ba08573297)

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9090] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9092] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'external')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9093] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9094] device (ens33): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9144] device (ens33): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9146] device (ens33): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')

Apr 30 04:24:22 DS-VM-Node172_17_0_1.cluster.com NetworkManager[949]: <info>  [1588191862.9153] device (ens33): Activation: successful, device activated.

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.7576] device (ens33): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'external')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.7745] device (ens33): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'external')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.7850] device (ens33): Activation: starting connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad)

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.7851] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.7855] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8564] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8566] dhcp4 (ens33): activation: beginning transaction (timeout in 45 seconds)

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191883.8567] device (ens33): failure to start DHCP: failed to set DHCP hostname: Invalid argument

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8567] device (ens33): state change: ip-config -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191883.8574] device (ens33): Activation: failed for connection 'ens33'

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8575] device (ens33): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8673] device (ens33): Activation: starting connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad)

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8674] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.8677] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.9231] device (ens33): state change: config -> deactivating (reason 'new-activation', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.9238] device (ens33): disconnecting for new activation request.

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.9252] device (ens33): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.9352] device (ens33): Activation: starting connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad)

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.9359] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:43 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191883.9362] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0351] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0353] dhcp4 (ens33): activation: beginning transaction (timeout in 45 seconds)

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191884.0354] device (ens33): failure to start DHCP: failed to set DHCP hostname: Invalid argument

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0354] device (ens33): state change: ip-config -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191884.0360] device (ens33): Activation: failed for connection 'ens33'

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0362] device (ens33): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0448] device (ens33): Activation: starting connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad)

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0449] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.0452] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1319] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1321] dhcp4 (ens33): activation: beginning transaction (timeout in 45 seconds)

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191884.1321] device (ens33): failure to start DHCP: failed to set DHCP hostname: Invalid argument

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1321] device (ens33): state change: ip-config -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191884.1327] device (ens33): Activation: failed for connection 'ens33'

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1328] device (ens33): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1383] device (ens33): Activation: starting connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad)

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1383] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1386] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1975] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1978] dhcp4 (ens33): activation: beginning transaction (timeout in 45 seconds)

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191884.1978] device (ens33): failure to start DHCP: failed to set DHCP hostname: Invalid argument

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1978] device (ens33): state change: ip-config -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <warn>  [1588191884.1985] device (ens33): Activation: failed for connection 'ens33'

Apr 30 04:24:44 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191884.1986] device (ens33): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7422] device (ens33): Activation: starting connection 'ens33' (882e1861-5548-4152-8eb1-04a186290097)

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7422] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7424] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'external')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7440] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7442] device (ens33): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7660] device (ens33): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7661] device (ens33): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')

Apr 30 04:25:07 DS-VM-Node172_16_193_132.cluster.com NetworkManager[949]: <info>  [1588191907.7669] device (ens33): Activation: successful, device activated.

通过谷歌搜索发现这是一个NetworkManager的BUG

BUG描述链接：

https://bugzilla.redhat.com/show_bug.cgi?id=1744427

既然知道了是BUG，也就知道了问题原因；在CentOS 8还没有对应更新NetworkManager软件包的情况下，我们只能把系统的hostname修改为localhost，来避开这个BUG

for i in static pretty transient; do hostnamectl set-hostname localhost --$i; done

修改完成后就可以重启自动获取DHCP IP了

原文链接：https://www.dwhd.org/20200430_044321.html

往期精彩

◆  必看 | Linux系列学习书籍免费送！

◆  利用expect批量修改Linux服务器密码

◆  Linux运维工程师面试问答录

◆  LVM逻辑卷学习

◆  Linux网络重点知识总结性梳理

◆  抓包工具tcpdump用法说明

◆  一文带你速懂虚拟化KVM和XEN

◆  实战 | Hadoo大数据集群搭建

◆  运维工程师心法：6大技能让你告别背锅

◆  亿级web系统负载均衡几种实现方式

好文和朋友一起看~

CentOS 8 重启不能DHCP获取IP的解决方法的更多相关文章

  1. VMware桥接模式无法自动化获取IP的解决方法

    虚拟机桥接无法自动获取IP的解决方法 在虚拟机VM里面装了centos系统,网卡选用桥接方式. 刚开始的时候还能自动获取到IP地址,突然有一天IP消失了,再怎么重启都无法获取IP地址.因为之前是可以获 ...

  2. netsh wlan set hostednetwork 之后如何删除掉 配置 及终端无法获取IP的解决方法

    来源 微软 技术支持网站 仅仅禁用hostednetwork 是不行的,配置其实还在,彻底删除 配置可以按照如下操作进行: net stop wlansvcGet-ItemProperty " ...

  3. VM虚拟机装centos无法自动获取IP的解决方法

    在虚拟机中使用ip addr 查看网卡 可以看到这个ens33,可能每台机器的名称不一样 然后找到/etc/sysconfig/network-scripts/ifcfg-eth33 编辑此文件 vi ...

  4. PXE DHCP获取IP与传统DHCP获取IP地址的区别

    正常的DHCP获取IP的流程(Discover-Offer-Request-Ack): (Discovery)主机端在LAN中发布MAC地址为FF:FF:FF:FF:FF:FF的广播来寻找DHCP服务 ...

  5. DHCP获取IP地址过程中捕获的报文—三级网络总结（二）

    上一篇文章主要说了一下知识点中的IP地址的考点,这一篇我打算说说DHCP获取IP地址过程中捕获的报文的这个考点,都是自己的理解,有错误欢迎指正. DHCP是应用层协议,UDP是传输层协议,IP是网络层 ...

  6. js获取IP地址多种方法实例教程

    js获取IP地址方法总结   js代码获取IP地址的方法,如何在js中取得客户端的IP地址.原文地址:js获取IP地址的三种方法 http://www.jbxue.com/article/11338. ...

  7. PHP获取IP地址的方法,防止伪造IP地址注入攻击

    PHP获取IP地址的方法 /** * 获取客户端IP地址 * <br />来源:ThinkPHP * <br />"X-FORWARDED-FOR" 是代理 ...

  8. Centos下忘记mysql的root密码的解决方法

    Centos下忘记mysql的root密码的解决方法 一:(停掉正在运行的mysql) [root@NetDakVPS ~]# service mysql stop 二:使用 “--skip-gran ...

  9. 本机的虚拟机执行ifconfig,显示不出ip的解决方法

    源于:https://blog.csdn.net/fuweihua123/article/details/78423715?locationNum=4&fps=1 本机的虚拟机执行ifconf ...

随机推荐

  1. Xml 映射文件中，除了常见的 select|insert|updae|delete 标签之外，还有哪些标签？

    <resultMap>.<parameterMap>.<sql>.<include>. <selectKey>,加上动态 sql 的 9 个 ...

  2. Element-UI资源原型库

    Element-UI v2.0.0版本 Axure和Sketch库: 链接:https://pan.baidu.com/s/1LdsEh8BKQBjcWBKV5yQilQ 提取码:1xqn

  3. Redis 的持久化机制是什么？各自的优缺点？

    Redis 提供两种持久化机制 RDB 和 AOF 机制: 1.RDBRedis DataBase)持久化方式: 是指用数据集快照的方式半持久化模式) 记录 redis 数据库的所有键值对,在某个时间 ...

  4. Flask 简单使用,这一篇就够了!

    #Flask 安装依赖包及作用 - jinja2 模板语言 (flask依赖包) - markupsafe 防止css攻击 (flask依赖包) - werkzeug --wkz 类似于django中 ...

  5. BMZCTF 2020祥云杯到点了

    2020祥云杯到点了 下载附件得到三个word文档,我们打开第一个文档然后将隐藏文字显示出来 得到提示 我们查看属性应该就是日期了我们先把他记录下来 然后打开第二个文档 输入刚刚的密码 在第二个wor ...

  6. python学习笔记（四）——面向对象编程

    python 支持面向过程编程和面向对象编程. 传统面向过程编程,也叫函数式编程,通过我们的需求设计成一个一个的函数来完成,对一些小规模程序来说面向过程确实简单方便不少.而随着互联网的发展,对于一些大 ...

  7. C语言思维导图—自己整理的

  8. python中PIL库的使用

    API参考 打开dos窗口,安装库: pip install pillow 很明显,图片有点大,咱们缩略一下: from PIL import Image im = Image.open(" ...

  9. 安装ESLint

    安装ESLint ESLint是静态代码检查工具,配合TypeScript使用可以帮助检查TypeScript的语法和代码风格. 添加ESLint到当前工程,yarn add -D eslint. 使 ...

  10. 学习HTML5 history API

    html5 在 history 对象上添加几个新的方法.事件.属性,用以增强开发者对于浏览器历史记录的控制.大体上说,新的API可以帮助我们在无刷新的情况下改变浏览器的url,新增或者替换之前的历史记 ...