Recent content by IzakEygelaar

  1. I

    Ceph - 'bad crc/signature' and 'socket closed'

    Hi David, I know this thread is old, but are you still experiencing this behaviour on your cluster, as we are seeing very similar behaviour on our setup. KVM's are running latest kernels and ceph cluster is running ceph Jewel on Centos 7.
  2. I

    "libceph: socket closed" on Proxmox heads connecting to ceph storage

    OK cool thanks, let me see what we can do as the KVM heads are under another team's control.
  3. I

    "libceph: socket closed" on Proxmox heads connecting to ceph storage

    kvm0v0 (Stretch) ~ # cat /etc/apt/sources.list.d/proxmox.list # This file is managed by Puppet. DO NOT EDIT. # proxmox deb http://download.proxmox.com/debian/pve/ stretch pve-no-subscription
  4. I

    "libceph: socket closed" on Proxmox heads connecting to ceph storage

    So all of these VM's are "long lived" / production VM's and running for the majority of the time. The Ceph storage runs on Centos 7 and makes use of the provided packages by Ceph. We have also increased the verbosity level (level 5) on the following subsystems: * osd * rbd * filestore From...
  5. I

    "libceph: socket closed" on Proxmox heads connecting to ceph storage

    Hi All, We have a situation where we are currently experiencing a massive amount of "socket closed " messages for Ceph OSD's on our KVM Proxmox heads. Current KVM Proxmox infrastructure: DELL R710 Dual CPU's Dual 10Gbps bonded copper connection to the CEPH storage (Current ceph version =>...
See more
Top Bottom