I've just updated my nodes to 5.2 (from 5.1) and I'm getting this odd error::
Jul 04 19:16:02 xen2 kernel: libceph: mon2 10.0.80.12:6789 socket closed (con state CONNECTING)
Jul 04 19:16:06 xen2 kernel: libceph: mon0 10.0.80.10:6789 socket error on write
Jul 04 19:16:09 xen2 kernel: libceph: mon2 10.0.80.12:6789 socket error on write
Jul 04 19:16:15 xen2 kernel: libceph: mon1 10.0.80.11:6789 socket error on read
Jul 04 19:16:18 xen2 kernel: libceph: mon0 10.0.80.10:6789 socket closed (con state CONNECTING)
Jul 04 19:16:21 xen2 kernel: libceph: mon0 10.0.80.10:6789 socket error on read
Because of this 'ct_disks','data_store' and 'vm_disks' have questions marks next to them and I can start any of the containers or VMs. I assume because it can't access the ceph nodes, the data storages aren't there which the VMs/containers run on.
Any ideas how to resolve this issue (or further troubleshoot it)? I'm on a rather tight deadline to get this back up and running.
Cheers for any help provided
Jul 04 19:16:02 xen2 kernel: libceph: mon2 10.0.80.12:6789 socket closed (con state CONNECTING)
Jul 04 19:16:06 xen2 kernel: libceph: mon0 10.0.80.10:6789 socket error on write
Jul 04 19:16:09 xen2 kernel: libceph: mon2 10.0.80.12:6789 socket error on write
Jul 04 19:16:15 xen2 kernel: libceph: mon1 10.0.80.11:6789 socket error on read
Jul 04 19:16:18 xen2 kernel: libceph: mon0 10.0.80.10:6789 socket closed (con state CONNECTING)
Jul 04 19:16:21 xen2 kernel: libceph: mon0 10.0.80.10:6789 socket error on read
Because of this 'ct_disks','data_store' and 'vm_disks' have questions marks next to them and I can start any of the containers or VMs. I assume because it can't access the ceph nodes, the data storages aren't there which the VMs/containers run on.
Any ideas how to resolve this issue (or further troubleshoot it)? I'm on a rather tight deadline to get this back up and running.
Cheers for any help provided