Hi Eugen, thanks for the idea but i didn’t have anything mounted that i could unmount > On 6. Sep 2021, at 09:15, Eugen Block <eblock@xxxxxx> wrote: > > Hi, > > I just got the same message in my lab environment (octopus) which I had redeployed. The client's keyring had changed after redeployment and I think I had a stale mount. After 'umount' and 'mount' with the proper keyring it worked as expected. > > > Zitat von Hendrik Peyerl <hpeyerl@xxxxxxxxxxxx>: > >> Hello All, >> >> i recently tried to reactivate a CEPH Cluster that I setup last year. I applied patches regularly and did some tests afterwards which always worked. >> >> Now I did run my usual tests again before getting it ready to use in production but I am not able to mount my cephfs shares anymore, I always run into the following error: >> >> mount error: no mds server is up or the cluster is laggy >> >> The ceph health is OK, I can reach all MDS Servers and all other servers aswell, the S3 Gateways is also still working. I did not find any errors within the logs that would help me debug this further. >> >> As i want to learn how to debug those issues in the future I’d rather try to repair the cluster instead of just recreating it since I dont have any pressure to get it running again quickly. >> >> Could you guys give me any hints on where to look further? >> >> CEPH Version: 14.2.22 >> OS: CentOS7 >> >> Thanks in Advance, >> >> Hendrik >> _______________________________________________ >> ceph-users mailing list -- ceph-users@xxxxxxx >> To unsubscribe send an email to ceph-users-leave@xxxxxxx > > > > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |