Fatal IO error 104 (Connection reset by peer) on X server

最新推荐文章于 2025-07-09 18:58:01 发布
原创 最新推荐文章于 2025-07-09 18:58:01 发布 · 6k 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#server #io

本文档指导如何在安全模式下备份并编辑X11的配置文件xorg.conf。具体步骤包括使用sudo命令进行权限提升，备份原有配置文件，并通过gedit编辑器修改配置文件中的'Screen'部分。

在安全模式下执行：
cd /etc/X11 ／*********X11的X是大写的
sudo cp xorg.conf xcorg.conf_back／*******作备份
sudo gedit xorg.conf／********编辑xorg
找到 ：Section "Screen"这行。
把Identifier 这行改成以下，，，
Identifier "Default Screen"
／********** ～～因为有备份所以放心 *****／



WuOu
关注
K8s（四）：集群初始化报错“Error getting node“ err=“node \“k8s-master\“ not found“
✨ 欢迎来到【Seal ^_^ 的优快云博客】！✨
04-01 3万+
🔴 K8s（四）：集群初始化报错“Error getting node“ err=“node \“k8s-master\“ not found“
vm安装centOS报错：anaconda: Fatal IO error 104
fanzhanki的专栏
07-26 4998
Running anaconda 13.21.176, the CentOS system installer - please wait 11:37:49 Starting graphical installation. anaconda: Fatal IO error 104 (Connection reset by peer) on X server :1.0. install exi
在VMware8.0.4安装centos6.3出现蓝屏，显示“anaconda: Fatal IO error 104 (Connection reset by peer) on X server :...
GJP61005的博客
02-24 579
解决方案：在创建虚拟机时选择“自定义（高级）”，然后点击“下一步”，在弹出的对话框中，在硬件兼容性该项选择 Workstation6.5-7.x。如果创建虚拟机时选择“标准”，默认的硬件兼容性将是Workstation8.0，就会报错。 转载于:https://www.cnblogs.com/JaneZSS/p/5213918.html...
vm安装centOS报错：anaconda: Fatal IO error 104_彭世瑜_新浪博客
彭世瑜的博客
12-06 1180
Running anaconda 13.21.176, the CentOS system installer - please wait 11:37:49 Starting graphical installation. anaconda: Fatal IO error 104 (Connection reset by peer) on X server :1.0. install ex...
虚拟机VMware7.0.0安装CentOS-6.2出现fatal IO error 104 connection reset by peer on xserver:1.0解决
caimo的专栏
03-06 1万+
背景：win7-64位，虚拟机VMware7.0.0，linux版本CentOS-6.2-i386-bin-DVD1.iso      我拿CentOS在VMware7.0.0版本上安装不成功，当跳过Disk检查，启动Xserver进行图形界面安装的时候，就出现了fatal IO error 104 connection reset by peer on xserver:1.0错误。
虚拟机安装centos报anaconda: Fatal IO error 104
修炼之路
10-26 3146
1、新建虚拟机的时候选择，自定义 2、然后硬件兼容性选择，下面的那个，就没问题了
root@cka-master:~# modprobe br_netfilter root@cka-master:~# kubeadm init --config kubead m.yaml [init] Using Kubernetes version: v1.32.0 [preflight] Running pre-flight checks [WARNING SystemVerification]: cgroups v 1 support is in maintenance mode, please migrat e to cgroups v2 [preflight] Pulling images required for setting up a Kubernetes cluster [preflight] This might take a minute or two, de pending on the speed of your internet connectio n [preflight] You can also perform this action be forehand using 'kubeadm config images pull' error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /kube-apiserver:v1.32.0: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/k ube-apiserver:v1.32.0: error pulling image configuration: download failed after attempts=6: read tc p 192.168.30.130:44340->124.160.145.45:80: read: connection reset by peer [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /kube-controller-manager:v1.32.0: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_con tainers/kube-controller-manager:v1.32.0: error pulling image configuration: download failed after a ttempts=6: read tcp 192.168.30.130:33568->124.160.145.45:80: read: connection reset by peer [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /kube-scheduler:v1.32.0: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/k ube-scheduler:v1.32.0: error pulling image configuration: download failed after attempts=6: read tc p 192.168.30.130:35120->124.160.145.45:80: read: connection reset by peer [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /kube-proxy:v1.32.0: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/kube- proxy:v1.32.0: error pulling image configuration: download failed after attempts=6: read tcp 192.16 8.30.130:58008->124.160.145.45:80: read: connection reset by peer [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /coredns:v1.11.3: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/coredns: v1.11.3: error pulling image configuration: download failed after attempts=6: read tcp 192.168.30.1 30:50124->124.160.145.45:80: read: connection reset by peer [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /pause:3.10: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.10: e rror pulling image configuration: download failed after attempts=6: read tcp 192.168.30.130:33184-> 124.160.145.45:80: read: connection reset by peer [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers /etcd:3.5.16-0: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.5.1 6-0: error pulling image configuration: download failed after attempts=6: read tcp 192.168.30.130:5 9094->124.160.145.45:80: read: connection reset by peer [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight -errors=...` To see the stack trace of this error execute with --v=5 or higher root@cka-master:~# kubeadm config images pull found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the 'criSocket' field in the kubeadm configuration file: unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock To see the stack trace of this error execute with --v=5 or higher root@cka-master:~# cat /etc/crictl.yaml runtime-endpoint: "unix:///run/cri-dockerd.sock" image-endpoint: "" timeout: 0 debug: false pull-image-on-create: false disable-pull-on-run: false 帮我分析以上集群部署时出现的问题，该如何解决
最新发布
09-29
1. 在`kubeadm init`阶段，预检时拉取镜像失败，错误信息显示在拉取多个必要镜像时出现“connection reset by peer”错误。 2. 在运行`kubeadm config images pull`时，出现多个CRI端点的错误，要求明确指定`...
golang http服务的graceful问题
weixin_33826609的博客
06-13 1348
背景一个web服务如果能将自身变动和对外服务隔离对服务的稳定性和可用性是友好的，所以出现了graceful的东西，实现随不同，但原理大致相似，我用的一个具体的实现请看github.com/cgCodeLife/…，在测试中发现一个现象，在执行graceful的服务热升级的时候发现golang的client会偶现EOF, read connection reset by peer, connecti...
一次“玄学”SSH故障，我居然挖到了云原生架构的惊天大坑！
qq_40286307的博客
07-09 921
从一次诡异的 SSH 故障出发，深入揭露云原生架构背后的随机性陷阱与应对之道。
安装VMware报错：anaconda: Fatal IO error 104解决方法
zh18810063861的博客
10-13 631
安装VMware报错：anaconda: Fatal IO error 104(Connection reset by peer) on X sever:1.0.解决方法
未解决：DELL dicension 上CentOS5无法启动图形模式
cuiwadui3512的博客
11-03 148
机器设备：dell dimension 2010操作系统：CentOS 5问题：安装成功后无法启动图形模式startx结果为：...fatal server error:no screens foundXIO: fatal IO...
xwindows不能登录问题解决办法
weixin_33724046的博客
02-21 384
很久没登录X界面了，今天登录时却发生如下错误：[root@gw ~]# startxxauth: error while loading shared libraries: libXmuu.so.1: cannot open shared ob                                              ject file: No such file or direc...
Java.io.IOException: Connection reset by peer问题定位
热门推荐
liyinping12的博客
10-26 1万+
相信不少兄弟都碰到过这类问题。很不幸，今天本人负责的一个系统突然大量出现该类错误，本身系统没有做修改。 一般第一眼看到这类错误基本上就可以确定是本系统作为服务端跟客服端的长链断了并进行了重连，但是是跟那条链路呢？由于报错中一点链路信息都没带，就仅仅抛出了一个异常给问题定位带来了不小困难。经过跟同事的讨论最终的定位方式如下： （1）首先我们可以确保该问题是由于长链路重置导致，也就是说肯定有一条本...
vm安装centOS报错：anaconda: Fatal IO error 104
彭世瑜的博客
12-06 1998
Running anaconda 13.21.176, the CentOS system installer - please wait 11:37:49 Starting graphical installation. anaconda: Fatal IO error 104 (Connection reset by peer) on X server :1.0. in...
FATAL ERRoR: connection reset by peer-session Close
04-03
"FATAL ERROR: connection reset by peer-session Close"是一个错误消息，表示与服务器的连接被对方重置，导致会话关闭。这种错误通常发生在网络通信过程中，可能是由于网络问题、服务器故障或者安全设置等原因引起...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值