[SOLVED] Ceph mgr daemon crash - NoOrchestrator exception

chrispage1

Active Member
Sep 1, 2021
91
50
38
33
Hi,

I've suddenly started getting crashes on the active Ceph manager node. It looks to be that the reason is caused by NoOrchestrator. We upgraded to Quincy at the weekend, but have never had any orchestrator modules.

Code:
root@pve01:# ceph crash info 2023-04-06T10:32:12.451213Z_f4961d03-7676-4700-8ca1-76da29e37bfc
{
    "backtrace": [
        "  File \"/usr/share/ceph/mgr/nfs/module.py\", line 154, in cluster_ls\n    return available_clusters(self)",
        "  File \"/usr/share/ceph/mgr/nfs/utils.py\", line 38, in available_clusters\n    completion = mgr.describe_service(service_type='nfs')",
        "  File \"/usr/share/ceph/mgr/orchestrator/_interface.py\", line 1479, in inner\n    completion = self._oremote(method_name, args, kwargs)",
        "  File \"/usr/share/ceph/mgr/orchestrator/_interface.py\", line 1546, in _oremote\n    raise NoOrchestrator()",
        "orchestrator._interface.NoOrchestrator: No orchestrator configured (try `ceph orch set backend`)"
    ],
    "ceph_version": "17.2.5",
    "crash_id": "2023-04-06T10:32:12.451213Z_f4961d03-7676-4700-8ca1-76da29e37bfc",
    "entity_name": "mgr.pve03",
    "mgr_module": "nfs",
    "mgr_module_caller": "ActivePyModule::dispatch_remote cluster_ls",
    "mgr_python_exception": "NoOrchestrator",
    "os_id": "11",
    "os_name": "Debian GNU/Linux 11 (bullseye)",
    "os_version": "11 (bullseye)",
    "os_version_id": "11",
    "process_name": "ceph-mgr",
    "stack_sig": "dad5ab00e8109633a6f99a44e3e3c67aa44aad3613d396e491b3ebd3ae1e9dad",
    "timestamp": "2023-04-06T10:32:12.451213Z",
    "utsname_hostname": "pve03",
    "utsname_machine": "x86_64",
    "utsname_release": "5.15.102-1-pve",
    "utsname_sysname": "Linux",
    "utsname_version": "#1 SMP PVE 5.15.102-1 (2023-03-14T13:48Z)"
}

Any idea why this would be happening / how I can stop it from throwing up errors? Strangely this has only occurred twice today, I have never seen the issue before.

Thanks,
Chirs.
 
Did you configure the NFS manager module in any way?
 
I didn't think so but it seems that the NFS module is on:

1680792403623.png

I don't believe it's needed though. Will disabling this resolve the issue?
 
Last edited:
If you don't use it, then yes disabling it should be fine.
Disabling it should get rid of those errors.
 
  • Like
Reactions: chrispage1