wrong socket path with ceph daemonperf
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
Le 22 avr. 2021 à 22:13, Fabrice Bacchella <fabrice.bacchella@orange.fr> a écrit :
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
The command is wrong, but trying the good command doesn't change the result: CEPH_CONF=/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@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Ceph project is drop cluster changing name may years ago. Is more client feature, for example for OpenStack API's --cluster=${name} is a /etc/ceph/${name}.conf or other custom software for multi cluster access from one point. So it's unmaintained feature. k
On 22 Apr 2021, at 23:13, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
I doing a custom, manual installation of ceph. I changed the cluster name from the default one to 'ngceph'.
Le 23 avr. 2021 à 23:37, Konstantin Shalygin <k0ste@k0ste.ru> a écrit :
Ceph project is drop cluster changing name may years ago. Is more client feature, for example for OpenStack API's --cluster=${name} is a /etc/ceph/${name}.conf or other custom software for multi cluster access from one point.
So it's unmaintained feature.
OK it's explain here https://docs.ceph.com/en/pacific/rados/configuration/common/#running-multipl...: But at https://docs.ceph.com/en/pacific/install/manual-deployment/: Cluster Name: Ceph clusters have a cluster name, which is a simple string without spaces. The default cluster name is ceph, but you may specify a different cluster name. Overriding the default cluster name is especially useful when you are working with multiple clusters and you need to clearly understand which cluster your are working with. For example, when you run multiple clusters in a multisite configuration <https://docs.ceph.com/en/pacific/radosgw/multisite/#multisite>, the cluster name (e.g., us-west, us-east) identifies the cluster for the current CLI session. Note: To identify the cluster name on the command line interface, specify the Ceph configuration file with the cluster name (e.g., ceph.conf, us-west.conf, us-east.conf, etc.). Also see CLI usage (ceph --cluster {cluster-name}). And many other places. So that paragraph is a documentation bug.
k
On 22 Apr 2021, at 23:13, Fabrice Bacchella <fabrice.bacchella@orange.fr <mailto:fabrice.bacchella@orange.fr>> wrote:
I doing a custom, manual installation of ceph. I changed the cluster name from the default one to 'ngceph'.
I was thinking about reporting the bug at https://pad.ceph.com/p/Report_Documentation_Bugs <https://pad.ceph.com/p/Report_Documentation_Bugs>. But what is thing thing ? What am I expected to do with that ? Just add a comment at the end ? But is this document read, used ? That's not a bugtrack but a shared document.
Le 24 avr. 2021 à 08:50, Fabrice Bacchella <fabrice.bacchella@orange.fr> a écrit :
Le 23 avr. 2021 à 23:37, Konstantin Shalygin <k0ste@k0ste.ru> a écrit :
Ceph project is drop cluster changing name may years ago. Is more client feature, for example for OpenStack API's --cluster=${name} is a /etc/ceph/${name}.conf or other custom software for multi cluster access from one point.
So it's unmaintained feature.
OK it's explain here https://docs.ceph.com/en/pacific/rados/configuration/common/#running-multipl...:
But at https://docs.ceph.com/en/pacific/install/manual-deployment/: Cluster Name: Ceph clusters have a cluster name, which is a simple string without spaces. The default cluster name is ceph, but you may specify a different cluster name. Overriding the default cluster name is especially useful when you are working with multiple clusters and you need to clearly understand which cluster your are working with.
For example, when you run multiple clusters in a multisite configuration <https://docs.ceph.com/en/pacific/radosgw/multisite/#multisite>, the cluster name (e.g., us-west, us-east) identifies the cluster for the current CLI session. Note: To identify the cluster name on the command line interface, specify the Ceph configuration file with the cluster name (e.g., ceph.conf, us-west.conf, us-east.conf, etc.). Also see CLI usage (ceph --cluster {cluster-name}).
And many other places. So that paragraph is a documentation bug.
k
On 22 Apr 2021, at 23:13, Fabrice Bacchella <fabrice.bacchella@orange.fr <mailto:fabrice.bacchella@orange.fr>> wrote:
I doing a custom, manual installation of ceph. I changed the cluster name from the default one to 'ngceph'.
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (2)
-
Fabrice Bacchella
-
Konstantin Shalygin