You will either need access to a ceph.conf, or else have some way to pass in on the CLI: * monitor IP addresses * a client ID * a client key (or keyring file) Your ceph.conf doesn't strictly need to be the same one used for other things on the cluster, so you could assemble it yourself. Same goes for the client keyring. But one way or another you need to gather up that data and provide it when you invoke the ceph tool. -Greg On Fri, Mar 15, 2019 at 1:04 PM Victor Hooi <victorhooi@xxxxxxxxx> wrote: > > Hi, > > I'm attempting to setup Telegraf on a Proxmox machine to send Ceph information into InfluxDB. > > I had a few issues around permissions (https://github.com/influxdata/telegraf/issues/5590), but we seem to be nearly sorted out. > > However, one issue still remains around ceph status. > > Specifically, it seems to require being able to read /etc/ceph/ceph.conf. For example, if I run sudo under the telegraf user context: > > root@syd1:/etc/ceph# sudo -u telegraf ceph status > 2019-03-16 07:01:37.262708 7f7031e1e700 -1 Errors while parsing config file! > 2019-03-16 07:01:37.262712 7f7031e1e700 -1 parse_file: cannot open /etc/ceph/ceph.conf: (13) Permission denied > Error initializing cluster client: PermissionDeniedError('error calling conf_read_file',) > > > However, on Proxmox, ceph.conf is a symlink to a file on their pmxcfs file system - which doesn't let you set custom permissions. > > Is there another way around this, to get ceph status to run under a non-root user? > > Thanks, > Victor > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |