I doing a custom, manual installation of ceph. I changed the cluster name from the default one to 'ngceph'.
I changed the installation path to /data/ceph.
A lot of thing correctly resolves the settings. But one command fails:
CLUSTER=/data/ceph/conf/ngceph.conf CLUSTER=ngceph ceph daemonperf client.radosgw.fa43 list
...
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/ceph_daemon.py", line 73, in admin_socket
b'{"prefix": "get_command_descriptions"}')
File "/usr/lib/python3.6/site-packages/ceph_daemon.py", line 49, in do_sockio
sock.connect(path)
FileNotFoundError: [Errno 2] No such file or directory
...
And indeed, after a few check, I found the culprit:
CLUSTER=/data/ceph/conf/ngceph.conf CLUSTER=ngceph strace -f -e trace=file ceph daemonperf client.radosgw.fa43 list
...
[pid 3431] execve("/bin/ceph-conf", ["ceph-conf", "--name", "client.radosgw.fa43", "--show-config-value", "admin_socket"], 0x5651c6e1cb30 /* 31 vars */) = 0
So I tried this command:
CLUSTER=/data/ceph/conf/ngceph.conf CLUSTER=ngceph ceph-conf --name client.radosgw.fa43 --show-config-value admin_socket
/var/run/ceph/ceph-client.radosgw.fa43.asok
But the real path for the socket is:
ls -l /var/run/ceph/ngceph-client.radosgw.fa43.2521.94787303273792.asok
srwxr-xr-x 1 ceph ceph 0 Apr 22 21:47 /var/run/ceph/ngceph-client.radosgw.fa43.2521.94787303273792.asok
It does not use the cluster name, and I wonder what is this 2521.94787303273792 coming from. Would it fails even with a standard cluster name ?
The version I'm using is a rpm build from ceph:
$ rpm -qf /bin/ceph-conf
ceph-common-16.2.1-0.el8.x86_64
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
