k8s使用glusterfs存储报错type 'features/utime'
k8s使用glusterfs存储报错type 'features/utime' is not valid or not found on this machine
pods报错如下
Events:Type Reason Age From Message---- ------ ---- ---- -------Normal Scheduled 5m48s default-scheduler Successfully assigned default/auth-web-1-77f4f7cbcc-snp8c to 192.168.1.216Warning FailedMount 5m47s kubelet, 192.168.1.216 MountVolume.SetUp failed for volume "auth-web-home" : mount failed: mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t glusterfs -o log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/auth-web-home/auth-web-1-77f4f7cbcc-snp8c-glusterfs.log,backup-volfile-servers=192.168.1.175:192.168.1.178:192.168.1.179,log-level=ERROR 192.168.1.175:k8s-glusterfs /var/lib/kubelet/pods/cb033ec1-6a62-11e9-b923-e0d55e1cf4c9/volumes/kubernetes.io~glusterfs/auth-web-home
Output: Mount failed. Please check the log file for more details.the following error information was pulled from the glusterfs log to help diagnose this issue:
[2019-04-29 09:40:16.070806] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:16.071117] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x5654d1b3138e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x5654d1b2bdc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f7989cda68b] ) 0-graph: invalid argument: graph [Invalid argument]Warning FailedMount 5m47s kubelet, 192.168.1.216 MountVolume.SetUp failed for volume "auth-web-home" : mount failed: mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t glusterfs -o log-level=ERROR,log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/auth-web-home/auth-web-1-77f4f7cbcc-snp8c-glusterfs.log,backup-volfile-servers=192.168.1.175:192.168.1.178:192.168.1.179 192.168.1.175:k8s-glusterfs /var/lib/kubelet/pods/cb033ec1-6a62-11e9-b923-e0d55e1cf4c9/volumes/kubernetes.io~glusterfs/auth-web-home
Output: Mount failed. Please check the log file for more details.
根据报错信息,我们可以看出来挂载的时候他是指定的日志文件的,我们去对应的日志查看报错
[2019-04-29 09:40:16.070575] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:16.070647] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:16.070806] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:16.071117] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x5654d1b3138e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x5654d1b2bdc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f7989cda68b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:16.712383] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:16.712464] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:16.712658] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:16.713034] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55c7459fe38e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55c7459f8dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f1a3cded68b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:17.868659] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:17.868718] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:17.868882] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:17.869215] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x5625d510738e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x5625d5101dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f578831768b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:20.068908] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:20.068976] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:20.069168] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:20.069562] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55da540e838e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55da540e2dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f1a9d62068b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:24.271395] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:24.271482] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:24.271669] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:24.272034] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x56378367338e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x56378366ddc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f676cb0468b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:32.670859] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:32.670935] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:32.671118] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:32.671504] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55d7af7e738e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55d7af7e1dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f33da2a568b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:48.870810] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:40:48.870865] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:48.871021] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:48.871325] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55b23825838e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55b238252dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7fcc6bb9668b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:41:21.069815] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
[2019-04-29 09:41:21.069878] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:41:21.070033] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:41:21.070404] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55c07e7d838e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55c07e7d2dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7fe065eee68b] ) 0-graph: invalid argument: graph [Invalid argument]
发现他一直在提示这一句 Volume 'k8s-glusterfs-utime', line 61: type 'features/utime' is not valid or not found on this machine
造成这个原因有如下几种可能:
1,glusterfs-server和glusterfs-client安装的版本不对应(解决办法,升级版本使版本一致)
2,glusterfs-server和glusterfs-clinet时间不同步,(做ntp时间服务器,或者关闭校验使用命令 gluster volume set $VolumeName ctime off)
转载于:https://blog.51cto.com/13447608/2386823
k8s使用glusterfs存储报错type 'features/utime'相关推荐
- GlusterFS 安装报错汇总
GlusterFS 安装报错汇总 1. Mounting glusterfs on /mnt/gluster0 failed. [root@instance-bt783gwn ~]# mount -t ...
- Eclipse正确配置Tomcat之后仍然报错Type Target runtime Apache Tomcat v8.0 is not defined解决方式
Eclipse正确配置Tomcat之后仍然报错Type Target runtime Apache Tomcat v8.0 is not defined解决方式 虽然项目能正常运行,但是看着这个红叉叉 ...
- kubernetes ingress路由配置http body大小限制,访问k8s服务的时候报错:413 Request Entity Too Large
访问k8s服务的时候报错:413 Request Entity Too Large kube-system命名空间下名为nginx-configuration的configmap,将proxy-bod ...
- 解决报错Type interface ___ is not known to the MapperRegistry.
解决报错Type interface ___ is not known to the MapperRegistry. 最近几天因为这个问题一直出错 今天终于在查看日志文件中找到原因 是因为在mybat ...
- K8S离线安装kubeadm报错:conntrack is needed by kubelet
K8S离线安装kubeadm报错:conntrack is needed by kubelet 报错信息: rpm -ivh kubeadm-1.18.20-0.x86_64.rpm kubectl- ...
- 从零开始在ubuntu上安装和使用k8s集群及报错解决
文章目录 安装docker 安装kubernetes 配置k8s集群 配置虚拟机网络 配置Master节点的k8s网络 拉取k8s需要的镜像 启动 kubeadm 和 kubelet 配置 node节 ...
- 部署k8s集群及报错完美解决方案
目录 部署环境 一.master操作 二.node01操作 三.Kubernetes部署容器化应用 四.其他报错解决 部署环境 Linux版本 CPU MEM CentOS7 双核 4G/node m ...
- 【错误记录】Kotlin 编译报错 ( Type mismatch: inferred type is String? but String was expected )
文章目录 一.报错信息 二.解决方案 一.报错信息 Google Play 上架要求 Android 的编译版本 和 目标版本都要高于 30 才可以上传 ; 将 Android 的编译版本 和 目标版 ...
- k8s入坑之报错(9)k8s node节点加入到集群时卡住 “[preflight] Running pre-flight checks”...
参考文档k8s node节点加入到集群时卡住 "[preflight] Running pre-flight checks"报错: k8s node节点加入到集群时卡住 " ...
最新文章
- MySQL学习笔记06【多表查询、子查询、多表查询练习】
- Delphi 从PaintBox拷贝一部分内容到TBitmap
- 【2019牛客暑期多校训练营(第六场)- D】Move(随机化二分)
- C++primer第九章 顺序容器 9.3 顺序容器操作
- 解决Vmware中安装Ubuntu Server 14.04 分辨率无法全屏问题
- php时间函数引入,PHP日期和时间函数的使用示例详解
- PostgreSQL的常见参数和技巧
- 工信部:“5G+工业互联网”在建项目全国已超2000余个
- 如何应对被地下的Oracle口令加密算法(2)
- SpringSecurity半成品笔记
- Django项目中使用Redis
- 【语音识别】基于matlab GUI声纹识别(带面板)【含Matlab源码 537期】
- vbs定时自动发送qq消息
- 程序员个人修养和职业规划
- 文菌装NAS E5:超详细!手把手教您安装黑群晖918+6.2保姆级教程
- 汽车维修企业管理【14】
- python执行其它py_如何在一个py程序里执行另一个py程序?
- mysql查询平均工资最低的部门_查询出部门名称、部门的员工数、部门的平均工资、部门的最低收入雇员姓名和最高收入雇员的姓名...
- plotly绘制3D图技巧
- 巴西法律和税收报告以及其他法律要求》》》本质上是一种税务监控手段;