Hi Zach, I just checked the Cherroot repo and there's no newer version (latest is 8.5.2), but that version should be both in 16.2.5 and 16.2.6 (python3-cheroot-8.5.2-1.el8.noarch), so I don't get why this started happening with .6. Are you running vanilla Ceph containers ( quay.ceph.io/ceph-ci/ceph) or a custom build? At this point, it'd be useful to follow up on a Ceph tracker issue, so could you please open one <https://tracker.ceph.com/projects/dashboard/issues/new>? Thanks. Kind Regards, Ernesto On Fri, Nov 26, 2021 at 10:55 PM Zach Heise (SSCC) <heise@xxxxxxxxxxxx> wrote: > Good afternoon Kai, I think I missed this email originally when you sent > it. > > I think that, due to how reliably this issue happens, that this seems to > be unlikely to be an issue with the mgr daemon going down. > > Ernesto - at this point, are there any other debug logs I can provide > that would give more detail? This isn't a mission critical thing for me > since I can restart the dashboard module so easily, and I'll feel hugely > better if it's the same problem that the Cherrypy webserver had a few > months ago. > > Should I go ahead and open up a new ceph bug at tracker.ceph.com if one > does not exist? > > Zach > > > On 2021-11-18 6:39 PM, Kai Börnert wrote: > > Hi, > > > > do you use more nodes than deployed mgrs and cephadm? > > > > If so it might be, that the node you are connecting to no longer has a > > instance of the mgr running, and you only getting some leftovers in > > the browser cache? > > > > At least this was happening in my test cluster, but I was always able > > to find a node with the mgr running by just trying trough them. > > > > Greetings, > > > > Kai > > > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |