rook issues

ceph-volumeattacher: failed rbd single_major check, assuming it‘s unsupported: failed to check for rbd module single_major param: Failed to complete ‘check kmod param‘: exit status 1. modinfo: ERROR:

could not get modinfo from ‘rbd‘: Exec format error

modinfo rbd
filename:       /lib/modules/3.10.0-693.21.1.el7.x86_64/kernel/drivers/block/rbd.ko.xz

解决:

给容器里安装xz 解压命令,因为新版内核中库文件是 xz 压缩包

或者将宿主机的rbd.ko.xz 解压,将解压后的rbd.ko 软连接到 rbd.ko.xz, 这样容器就不用解压了
------------------------------------------------------------

2018-04-21 04:03:27.450807 I | cephosd: skipping device sdb that is in use (not by rook). fs: , ownPartitions: false

2018-04-21 04:03:27.483015 I | cephosd: configuring osd devices: {"Entries":{}}

解决:

使用无分区的裸磁盘

------------------------------------------------------------

MountVolume.SetUp failed for volume "pvc-f002e1fe-469c-11e8-9dca-90b8d0599f2f" : mount command failed, status: Failure, reason: Rook: Error getting RPC client: error connecting to socket /usr/libexec/kubernetes/kubelet-plugins/volume/exec/rook.io~rook/.rook.sock: dial unix /usr/libexec/kubernetes/kubelet-plugins/volume/exec/rook.io~rook/.rook.sock: connect: no such file or directory

解决:

rook-operator.yml

env:- name: FLEXVOLUME_DIR_PATH  value: "/var/lib/kubelet/volumeplugins"

kubelet 启动加上

--volume-plugin-dir=/var/lib/kubelet/volumeplugins

------------------------------------------------------------------------------------------

pod event:

MountVolume.SetUp failed for volume "pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f" : mount command failed, status: Failure, reason: Rook: Mount volume failed: failed to attach volume replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f: failed to map image replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f cluster rook. failed to map image replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f: Failed to complete ‘rbd‘: signal: interrupt. . output: pod has unbound PersistentVolumeClaims (repeated 7 times)

rook-agent  logs:

2018-04-23 03:11:28.618916 I | exec: Running command: rbd map replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f --id admin --cluster=rook --keyring=/tmp/rook.keyring362403923 -m 10.254.233.241:6790 --conf=/dev/null

2018-04-23 03:12:28.620071 I | exec: Timeout waiting for process rbd to return. Sending interrupt signal to the process
2018-04-23 03:12:28.624230 E | flexdriver: Attach volume replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f failed: failed to attach volume replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f: failed to map image replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f cluster rook. failed to map image replicapool/pvc-99dabdb1-46a4-11e8-9dca-90b8d0599f2f: Failed to complete ‘rbd‘: signal: interrupt. . output:

进入容器手动执行

rbd: sysfs write failed

解决:

原文地址:https://www.cnblogs.com/mhc-fly/p/8921169.html

时间: 2024-07-29 14:25:11

rook issues的相关文章

kubernetes上部署rook-ceph存储系统

[TOC] 1. 简单说说为什么用rook rook这里就不作详细介绍了,具体可以到官网查看. 说说为什么要在kubernetes上使用rook部署ceph集群.众所周知,当前kubernetes为当前最佳云原生容器平台,随着pod在kubernetes节点内被释放,其容器数据也会被清除,即没有持久化存储数据能力.而ceph作为最好的开源存储之一,也是结合kubernetes最好的存储之一.利用kubernetes的调度功能,rook的自我扩展和自我修复能力,相互紧密配合. 2. rook-ce

issues about Facebook Login

在学习The complete iOS 9 Developer Course - Build 18 Apps 中的Letture134-Facebook Login,需要整合(integrate)Parse+Facebook在iOS(Xcode)中,也就是用Facebook的账户登录制作的APP(copy Tinder),然后在Parse中记录账户的相关信息,而不用手动建立.登陆成功之后在后台返回账户的名称等public_profile. 此Lecture算是至今最难的一节,因为1.Parse的

Top Things to Consider When Troubleshooting Complex Application Issues

http://blogs.msdn.com/b/debuggingtoolbox/archive/2011/10/03/top-things-to-consider-when-troubleshooting-complex-application-issues.aspx 1- For reactive incidents: “Bring the engineer onsite because it is going to be easier to isolate the problem.” Th

Save Money on Your Issues

Save Money on Your Issues Randy Loomis, PMP Andover, Connecticut, U.S. oUR CoMPAny WAS USIng TRAInIng SoFTWARE that was five upgrades behind. We reached the point where it was so out of date that the vendor would no longer support it. Our project con

App Submission Issues

查看原文: http://leancodingnow.com/app-submission-issues/ I bet many iOS developers are busy submitting apps to the App Store lately after fixing issues on iOS 9. This blog post just listed the issues I came across lately when submitting apps to App Stor

Investigating issues with Unmanaged Memory. First steps. (转载)

原文:http://kate-butenko.blogspot.tw/2012/07/investigating-issues-with-unmanaged.html I want to write this blogpost really fast, until I forget everything, despite I have absolutely no time and need to work on other cases :( Let's count this as part of

zabbix 在主页增加"last 20 issues"

在zabbix的主页有一项last 20 issues,显示的是当前有问题的trigger,方面我们查看现在系统的问题,但是在报警很多的时候超过20个就知道显示当前的20个,很多trigger就看不到了,为了让这个显示的更多可以修改zabbix web的源码,让这个显示的更多. 例如修改成last 100 issues: vim include/defines.inc.php define('DEFAULT_LATEST_ISSUES_CNT', 20);    //修改20为100 刷新查看就

Failover clustrinng configration common issues

Windows fail-over clustering is very useful for servers fail over, when configuring this function some common issues we might encounter, I shared the solutions as follows: 1) Cluster quorum setting cannot be successful. Most likely, it is due to acce

PLSQL_性能优化工具系列_Best Practices: Proactive Data Collection for Performance Issues

占位符 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=2082062510193540&id=1366133.1&_afrWindowMode=0&_adf.ctrl-state=rru77dj7v_139 NOTE:1417774.1 - FAQ: SQL Health Check (SQLHC) Frequently Asked QuestionsNOTE:224270.1 - TRCANLZR