-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable the admin socket and log file for librbd client #204
Conversation
Need to sync it on related charm openstack project Related-Bug: LP#1786874
looks like cinder-volume use too much rados client. which will generate too much ceph client log file. |
maybe I'm wrong, I might have misunderstood about the $pid, maybe the $pid is refer to cinder-volume process, not the thread. I will need to do some experiment. |
Ive tried enabling this in my local env on a cinder node. I then created 100 (rbd) volumes and there were 0 logfiles in /var/log/ceph which suggests that librbd does not support client logging. As a side test i ran an rbd cli command and it created /var/log/ceph/client.admin.550767.log. |
Two problems
|
Enable 'log to syslog' and 'err to stderr' for ceph clients. Currently the default configuration disables "log to syslog" for ceph primarily targeting the ceph OSD units which log to files in /var/log/ceph instead. However this value is also used by ceph clients and as a result even with an error a ceph client such as libvirt/qemu will not log errors *anywhere* making issues such as failure to connect to a ceph cluster or invalid keyrings difficult to diagnose. Hence we always enable 'log to syslog' for ceph clients. We could alternatively enable log to a file, however, there are apparmor and permissions issues that mean access to /var/log/ceph is not guaranteed and in some cases multiple PIDs may write to this file creating many different files so syslog seems like the best choice. (Reference: juju#204) Also enable 'err to stderr' which it makes it more likely the error is surfaced in other important locations such as /var/log/libvirt/qemu/instance-*.log and on the command line. Partial-Bug: #1786874
Enable 'log to syslog' and 'err to stderr' for ceph clients. Currently the default configuration disables "log to syslog" for ceph primarily targeting the ceph OSD units which log to files in /var/log/ceph instead. However this value is also used by ceph clients and as a result even with an error a ceph client such as libvirt/qemu will not log errors *anywhere* making issues such as failure to connect to a ceph cluster or invalid keyrings difficult to diagnose. Hence we always enable 'log to syslog' for ceph clients. We could alternatively enable log to a file, however, there are apparmor and permissions issues that mean access to /var/log/ceph is not guaranteed and in some cases multiple PIDs may write to this file creating many different files so syslog seems like the best choice. (Reference: juju#204) Also enable 'err to stderr' which it makes it more likely the error is surfaced in other important locations such as /var/log/libvirt/qemu/instance-*.log and on the command line. Partial-Bug: #1786874
Need to sync it on related charm openstack project