Documentation #45564
closed
cephadm: document workaround for accessing the admin socket by entering running container
Added by Sebastian Wagner almost 4 years ago.
Updated over 3 years ago.
Description
$ ceph daemon mgr.ceph03 config show
admin_socket: exception getting command descriptions: [Errno 2] No such file or directory
$ ceph --admin-daemon /var/run/ceph/mgr.ceph03 config show
No such file or directory
Probably, users have to run
cephadm enter mgr.ceph03
to access the admin socket.
I got it to work like this:
node1:~ # cephadm enter --fsid 1c45b7be-bbad-11ea-9ed1-525400092435 --name osd.0
[ceph: root@node1 /]# ceph daemon osd.0 help
I do have to be on the same node where the osd.0 container is running.
I noticed that "cephadm shell" infers the FSID (I only have one cluster running on this set of machines, so it's not difficult to infer) - maybe "cephadm enter" could do the same?
- Subject changed from cephadm: how to access the admin socket? to cephadm: how to access the admin socket from outside container?
- Subject changed from cephadm: how to access the admin socket from outside container? to cephadm: not possible to access the admin socket from outside container
- Subject changed from cephadm: not possible to access the admin socket from outside container to cephadm: document workaround for accessing the admin socket by entering running container
I just noticed this ticket is in the Documentation tracker. I opened a new ticket #48019 to track the actual bug (it should not be necessary to enter a container to access the admin socket, should it?)
- Related to Bug #48019: cephadm: `ceph daemon <daemon-name> ...` is broken added
I'd close this as duplicate now
- Status changed from New to Duplicate
Also available in: Atom
PDF