linux虚拟机出现See 'systemctl status network.service' and 'journalctl -xn' for details.的原因

博主之前也是突然遇到linux没有eth0网卡，重新cp了写了配置但是也没有用，反而有一个莫名其妙的报错

See ‘systemctl status network.service‘ and ‘journalctl -xn‘ for details.

而且再去读eth0会提示file not found

然后尝试重新添加删除网卡没法重新发现

突然想到会不会是驱动的原因，想到了这个地方

这个是vmware的一个智能设置，他会根据你的ISO自动给你推荐分类的vmware tools，但是博主的ISO是x64的，他自动选择的却是默认32的

新建虚拟机在该选项选择centos x64即可，系统安装后成功发现网卡

linux虚拟机出现See 'systemctl status network.service' and 'journalctl -xn' for details.的原因

时间： 2024-10-13 23:29:04

linux虚拟机出现See 'systemctl status network.service' and 'journalctl -xn' for details.的原因的相关文章

Linux 重启网卡失败 Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.

linux下重启网卡使用命令 : service network restart 时报错: [[email protected] hadoop]# service network restart Starting network (via systemctl): Job for network.service failed because the control process exited with error code. See "systemctl status network.servi

Apache重启失败，提示：Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.

今天更新完程序,重启apache的时候,第一遍正常重启,1分钟之后第二次重启的时候报错了. 执行service httpd restart之后: 报错: Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details. 此时查看apache状态已经处于stop. 执行 ps -ef | grep httpd 命令查看端口占用的时候,已经没有httpd进程,ap

Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details

thinkphp 在Apache上配置启用伪静态,重启Apache1 restart 竟然失败了,报错 Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details 嗯,看状态执行命令 systemctl status http

docker 报错： Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

centos 启动docker服务报错: Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. 1,create daemon.json in /etc/docker/ 2, put this in it: { &q

nginx启动报错：Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' fo

一.背景这个错误在重启nginx或者启动nginx的时候,经常会出现.我之前也一直认为出现这个错误是因为有程序占用了nginx的进程.但是知其然不知其所以然.每次报错都有点懵逼,所以这边一步步排查错误,做个记录. 二.排错过程 1.按照提示 //按照提示,执行此命令,查看错误原因 systemctl status nginx.service 由报错信息可知,nginx绑定80端口失败.详细错误请输入 -l 继续查看 2.继续跟踪错误 //查看错误的详情 systemctl status ngi

CentOS启动docker1.13失败(Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.)

一.启动失败 1.启动docker [[email protected] ~]# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe " for details. 上面表示输入 systemctl

Job for php-fpm.service failed because the control process exited with error code. See "systemctl status php-fpm.service" and "journalctl -xe" for details.

[[email protected] ~]# systemctl start php-fpm Job for php-fpm.service failed because the control process exited with error code. See "systemctl status php-fpm.service" and "journalctl -xe" for details. [[email protected] ~]# systemc

See "systemctl status postfix.service" and "journalctl -xe" for details.

启动postfix的时候报错: [[email protected] tmp]# systemctl enable postfix && systemctl start postfix Job for postfix.service failed because the control process exited with error code. See "systemctl status postfix.service" and "journalctl -

docker启动时报错Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

这里报错主要是因为docker启动时需要默认开启selinux,但是可能由于安装某些应用,我们关闭了selinux,所以此时我们需要设置/etc/sysconfig/docker 将下图标黄位置改为false,即设置docker启动时默认不需要开启selinux # /etc/sysconfig/docker # Modify these options if you want to change the way the docker daemon runs OPTIONS='--selinux