在同一个网络内，建立了两个同名的群集

Jun 24 11:56:08 cu-pve05 kyc_zabbix_ceph[2419970]: ]}

Jun 24 11:56:08 cu-pve05 corosync[3954]: error   [TOTEM ] Digest does not match

Jun 24 11:56:08 cu-pve05 corosync[3954]: alert   [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:08 cu-pve05 corosync[3954]: alert   [TOTEM ] Invalid packet data

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Digest does not match

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Invalid packet data

Jun 24 11:56:08 cu-pve05 kyc_zabbix_ceph[2419970]: Response from "192.168.7.114:10051": "processed: 3; failed: 48; total: 51; seconds spent: 0.001189"

Jun 24 11:56:08 cu-pve05 kyc_zabbix_ceph[2419970]: sent: 51; skipped: 0; total: 51

Jun 24 11:56:08 cu-pve05 corosync[3954]: error   [TOTEM ] Digest does not match

Jun 24 11:56:08 cu-pve05 corosync[3954]: alert   [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:08 cu-pve05 corosync[3954]: alert   [TOTEM ] Invalid packet data

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Digest does not match

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Invalid packet data

Jun 24 11:56:08 cu-pve05 corosync[3954]: error   [TOTEM ] Digest does not match

Jun 24 11:56:08 cu-pve05 corosync[3954]: alert   [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:08 cu-pve05 corosync[3954]: alert   [TOTEM ] Invalid packet data

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Digest does not match

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:08 cu-pve05 corosync[3954]:  [TOTEM ] Invalid packet data

Jun 24 11:56:09 cu-pve05 corosync[3954]: error   [TOTEM ] Digest does not match

Jun 24 11:56:09 cu-pve05 corosync[3954]: alert   [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:09 cu-pve05 corosync[3954]: alert   [TOTEM ] Invalid packet data

Jun 24 11:56:09 cu-pve05 corosync[3954]:  [TOTEM ] Digest does not match

Jun 24 11:56:09 cu-pve05 corosync[3954]:  [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:09 cu-pve05 corosync[3954]:  [TOTEM ] Invalid packet data

Jun 24 11:56:09 cu-pve05 corosync[3954]: error   [TOTEM ] Digest does not match

Jun 24 11:56:09 cu-pve05 corosync[3954]: alert   [TOTEM ] Received message has invalid digest... ignoring.

Jun 24 11:56:09 cu-pve05 corosync[3954]: alert   [TOTEM ] Invalid packet data

删掉其中一个后，又报下面的错，在节点视图下的syslog下看到的

Jul 11 18:48:01 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on write

Jul 11 18:48:04 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:48:07 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on read

Jul 11 18:48:35 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on read

Jul 11 18:48:39 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on read

Jul 11 18:48:42 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:48:45 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:48:51 cu-pve03 pvedaemon[4111390]: worker exit

Jul 11 18:48:51 cu-pve03 pvedaemon[4692]: worker 4111390 finished

Jul 11 18:48:51 cu-pve03 pvedaemon[4692]: starting 1 worker(s)

Jul 11 18:48:51 cu-pve03 pvedaemon[4692]: worker 4148787 started

Jul 11 18:49:00 cu-pve03 systemd[1]: Starting Proxmox VE replication runner...

Jul 11 18:49:00 cu-pve03 systemd[1]: Started Proxmox VE replication runner.

Jul 11 18:49:06 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on read

Jul 11 18:49:10 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:49:13 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on read

Jul 11 18:49:16 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:49:23 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:49:30 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket closed (con state CONNECTING)

Jul 11 18:49:36 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on write

Jul 11 18:49:39 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket closed (con state CONNECTING)

Jul 11 18:49:42 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on read

Jul 11 18:49:50 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on write

Jul 11 18:50:00 cu-pve03 systemd[1]: Starting Proxmox VE replication runner...

Jul 11 18:50:00 cu-pve03 systemd[1]: Started Proxmox VE replication runner.

Jul 11 18:50:00 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on read

Jul 11 18:50:07 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on write

Jul 11 18:50:14 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:50:26 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:50:31 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on write

Jul 11 18:50:34 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:50:37 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on write

Jul 11 18:50:40 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on write

Jul 11 18:50:55 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:51:00 cu-pve03 systemd[1]: Starting Proxmox VE replication runner...

Jul 11 18:51:00 cu-pve03 systemd[1]: Started Proxmox VE replication runner.

Jul 11 18:51:02 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket closed (con state CONNECTING)

Jul 11 18:51:09 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on read

Jul 11 18:51:16 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket closed (con state CONNECTING)

Jul 11 18:51:19 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on read

Jul 11 18:51:33 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:51:43 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on read

Jul 11 18:51:48 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on read

Jul 11 18:51:51 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on write

Jul 11 18:52:00 cu-pve03 systemd[1]: Starting Proxmox VE replication runner...

Jul 11 18:52:00 cu-pve03 systemd[1]: Started Proxmox VE replication runner.

Jul 11 18:52:03 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:52:14 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on write

Jul 11 18:52:26 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on write

Jul 11 18:52:34 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:52:37 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on write

Jul 11 18:52:40 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:52:43 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:52:50 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:53:00 cu-pve03 systemd[1]: Starting Proxmox VE replication runner...

Jul 11 18:53:00 cu-pve03 systemd[1]: Started Proxmox VE replication runner.

Jul 11 18:53:01 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:53:05 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on write

Jul 11 18:53:08 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on write

Jul 11 18:53:11 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on write

Jul 11 18:53:14 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket closed (con state CONNECTING)

Jul 11 18:53:28 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket closed (con state CONNECTING)

Jul 11 18:53:51 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on read

Jul 11 18:53:55 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket error on read

Jul 11 18:53:58 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:54:00 cu-pve03 systemd[1]: Starting Proxmox VE replication runner...

Jul 11 18:54:00 cu-pve03 systemd[1]: Started Proxmox VE replication runner.

Jul 11 18:54:01 cu-pve03 kernel: libceph: mon0 192.168.7.4:6789 socket closed (con state CONNECTING)

Jul 11 18:54:06 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket error on read

Jul 11 18:54:09 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:54:17 cu-pve03 kernel: libceph: mon2 192.168.7.6:6789 socket closed (con state CONNECTING)

Jul 11 18:54:18 cu-pve03 kernel: libceph: mds0 192.168.7.5:6800 socket closed (con state CONNECTING)

Jul 11 18:54:32 cu-pve03 pveproxy[4118327]: worker exit

Jul 11 18:54:32 cu-pve03 pveproxy[7729]: worker 4118327 finished

Jul 11 18:54:32 cu-pve03 pveproxy[7729]: starting 1 worker(s)

Jul 11 18:54:32 cu-pve03 pveproxy[7729]: worker 4150738 started

Jul 11 18:54:37 cu-pve03 kernel: libceph: mon1 192.168.7.5:6789 socket error on read
问题点：

1、te环境backup 40MB/s

2、数据库虚拟机备份，考虑挂载点的问题，/ceph/fileserver/...

3、复制kycfs上的文件。
vzdump 202 --compress lzo  --storage kycfs --mode snapshot --node cu-pve05 --remove 0

vzdump 151 --mode stop --remove 0 --storage kycfs --compress lzo --node cu-pve02 --bwlimit 200000

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

INFO: starting new backup job: vzdump 151 --mode stop --remove 0 --storage kycfs --compress lzo --node cu-pve02

INFO: Starting Backup of VM 151 (qemu)

INFO: Backup started at 2019-07-10 16:26:44

INFO: status = stopped

INFO: update VM 151: -lock backup

INFO: backup mode: stop

INFO: ionice priority: 7

INFO: VM Name: cu-dbs-151

INFO: include disk 'scsi0' 'kycrbd:vm-151-disk-0' 100G

INFO: include disk 'scsi1' 'kycrbd:vm-151-disk-1' 300G

INFO: snapshots found (not included into backup)

INFO: creating archive '/mnt/pve/kycfs/dump/vzdump-qemu-151-2019_07_10-16_26_44.vma.lzo'

INFO: starting kvm to execute backup task

INFO: started backup task 'a29c0ebc-52ee-4823-a5e6-56e7443c2cae'

INFO: status: 0% (499122176/429496729600), sparse 0% (423092224), duration 3, read/write 166/25 MB/s

INFO: status: 1% (4353687552/429496729600), sparse 0% (4277657600), duration 22, read/write 202/0 MB/s

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

INFO: starting new backup job: vzdump 192 --compress lzo --bwlimit --storage kycfs --mode snapshot --node cu-pve06 --remove 0

INFO: Starting Backup of VM 192 (qemu)

INFO: Backup started at 2019-07-10 16:28:53

INFO: status = stopped

INFO: update VM 192: -lock backup

INFO: backup mode: stop

INFO: ionice priority: 7

INFO: VM Name: cu-tpl-192

INFO: include disk 'ide0' 'kycrbd:vm-192-disk-0' 100G

INFO: creating archive '/mnt/pve/kycfs/dump/vzdump-qemu-192-2019_07_10-16_28_53.vma.lzo'

INFO: starting kvm to execute backup task

INFO: started backup task '58adf55a-971c-49aa-b42d-595f8e3a0cf3'

INFO: status: 0% (197656576/107374182400), sparse 0% (114630656), duration 3, read/write 65/27 MB/s

INFO: status: 1% (1090519040/107374182400), sparse 0% (556826624), duration 15, read/write 74/37 MB/s

INFO: status: 2% (2181038080/107374182400), sparse 0% (563113984), duration 42, read/write 40/40 MB/s

INFO: status: 3% (3257532416/107374182400), sparse 0% (581787648), duration 69, read/write 39/39 MB/s

pve_ceph问题汇总的更多相关文章

  1. 常用 Gulp 插件汇总 —— 基于 Gulp 的前端集成解决方案（三）

    前两篇文章讨论了 Gulp 的安装部署及基本概念,借助于 Gulp 强大的 插件生态 可以完成很多常见的和不常见的任务.本文主要汇总常用的 Gulp 插件及其基本使用,需要读者对 Gulp 有一个基本 ...

  2. 异常处理汇总 ~ 修正果带着你的Net飞奔吧！

    经验库开源地址:https://github.com/dunitian/LoTDotNet 异常处理汇总-服 务 器 http://www.cnblogs.com/dunitian/p/4522983 ...

  3. UWP开发必备：常用数据列表控件汇总比较

    今天是想通过实例将UWP开发常用的数据列表做汇总比较,作为以后项目开发参考.UWP开发必备知识点总结请参照[UWP开发必备以及常用知识点总结]. 本次主要讨论以下控件: GridView:用于显示数据 ...

  4. Oracle手边常用70则脚本知识汇总

    Oracle手边常用70则脚本知识汇总 作者:白宁超 时间:2016年3月4日13:58:36 摘要: 日常使用oracle数据库过程中,常用脚本命令莫不是用户和密码.表空间.多表联合.执行语句等常规 ...

  5. Oracle 数据库知识汇总篇

    Oracle 数据库知识汇总篇(更新中..) 1.安装部署篇 2.管理维护篇 3.数据迁移篇 4.故障处理篇 5.性能调优篇 6.SQL PL/SQL篇 7.考试认证篇 8.原理体系篇 9.架构设计篇 ...

  6. Vertica 数据库知识汇总篇

    Vertica 数据库知识汇总篇(更新中..) 1.Vertica 集群软件部署,各节点硬件性能测试 2.Vertica 创建数据库,创建业务用户测试 3.Vertica 数据库参数调整,资源池分配 ...

  7. 读书笔记汇总 - SQL必知必会（第4版）

    本系列记录并分享学习SQL的过程,主要内容为SQL的基础概念及练习过程. 书目信息 中文名:<SQL必知必会(第4版)> 英文名:<Sams Teach Yourself SQL i ...

  8. 关于DDD的学习资料汇总

    DDD(Domain-Driven Design)领域驱动设计,第一次看到DDD是在学习ABP时,在其中的介绍中看到的.what,DDD是个什么鬼,我不是小白,是大白,没听过.于是乎,度娘查查查,找到 ...

  9. Oracle 列数据聚合方法汇总

    网上流传众多列数据聚合方法,现将各方法整理汇总,以做备忘. wm_concat 该方法来自wmsys下的wm_concat函数,属于Oracle内部函数,返回值类型varchar2,最大字符数4000 ...

随机推荐

  1. Flutter——FloatingActionButton组件（浮动按钮组件）

    FloatingActionButton 简称 FAB ,可以实现浮动按钮,也可以实现类似闲鱼 app 的地步凸起导航.     属性名称 属性值 child 子视图,一般为 Icon,不推荐使用文字 ...

  2. OpenStack中虚拟机获取不到IP地址的解决方法

    OpenStack源码交流群: 538850354 系统环境: centos6.5 + icehouse多节点部署 问题描述: 使用测试镜像cirros,虚拟机实例可以正常启动,但是不能从IP池中获取 ...

  3. RT-Thread--内存管理

    内存管理的功能特点 RT-Thread 操作系统在内存管理上,根据上层应用及系统资源的不同,有针对性地提供了不同的内存分配管理算法.总体上可分为两类:内存堆管理与内存池管理,而内存堆管理又根据具体内存 ...

  4. P4393 [BOI2007]Sequence 序列问题[贪心]

    题目描述 对于一个给定的序列a1, -, an,我们对它进行一个操作reduce(i),该操作将数列中的元素ai和ai+1用一个元素max(ai,ai+1)替代,这样得到一个比原来序列短的新序列.这一 ...

  5. C#经纬度加减运算(度°分′秒″格式)

    经度是分和秒是按60进位,如果要做运算第一步就是转换成浮点数,之后就是计算和还原. using System.Text.RegularExpressions; public static double ...

  6. maven-setting.xml文件详解

    <?xml version="1.0" encoding="UTF-8"?> <settings xmlns="http://mav ...

  7. java大文件上传解决方案

    最近遇见一个需要上传百兆大文件的需求,调研了七牛和腾讯云的切片分段上传功能,因此在此整理前端大文件上传相关功能的实现. 在某些业务中,大文件上传是一个比较重要的交互场景,如上传入库比较大的Excel表 ...

  8. C# 使用递归获取所有下属、所有子部门……

    本例中获取的是所有的晚辈!首先定义家庭成员类: public class FamilyMember { /// <summary> /// 身份 /// </summary> ...

  9. P4092 [HEOI2016/TJOI2016]树

    题目描述 在2016年,佳媛姐姐刚刚学习了树,非常开心.现在他想解决这样一个问题:给定一颗有根树(根为1),有以下两种操作: 标记操作:对某个结点打上标记(在最开始,只有结点1有标记,其他结点均无标记 ...

  10. NetworkX系列教程(10)-算法之三:关键路径问题

    小书匠Graph图论 重头戏部分来了,写到这里我感觉得仔细认真点了,可能在NetworkX中,实现某些算法就一句话的事,但是这个算法是做什么的,用在什么地方,原理是怎么样的,不清除,所以,我决定先把图 ...