[ceph-users] Re: Cluster became unresponsive: e5 handle_auth_request failed to assign global_id

. Not sure if it is the reason or the consequence of this problem. вт, 28 июл. 2020 г. в 11:37, Anthony D'Atri : > Are your mon DBs on SSDs? > > > On Jul 27, 2020, at 7:28 AM, Илья Борисович Волошин < > i.volos...@simplesolution.pro> wrote: > > > > Here

[ceph-users] Re: Cluster became unresponsive: e5 handle_auth_request failed to assign global_id

(something like netstat -4ln or the current > equivalent thereof) > > Is the old (new) Firewall maybe still running ? > > > On 27.07.20 16:00, Илья Борисович Волошин wrote: > > Hello, > > > > I've created an Octopus 15.2.4 cluster with 3 monitors and 3 OSDs

[ceph-users] Cluster became unresponsive: e5 handle_auth_request failed to assign global_id

Hello, I've created an Octopus 15.2.4 cluster with 3 monitors and 3 OSDs (6 hosts in total, all ESXi VMs). It lived through a couple of reboots without problem, then I've reconfigured the main host a bit: set iptables-legacy as current option in update-alternatives (this is a Debian10 system),