Valery Tschopp

Hello @tschoonj I checked, and unfortunately porting it to boto3 is a big refactoring. boto3 is completely different, less straight forward then the old boto... And I'll not find the...

Thanks for reporting this issue, I'll try to have a look at it asap

Unfortunately the subuser management functionalities are still missing. I currently don't have time to implement this myself, but fell free to submit a pull request.

What is the command you are using ? (e.g. `./check_ceph_osd -H ceph-storage-0.example.com -k client.nagios.keyring -i nagios`)

It should be a file permission problem. Here is what I have for the user nagios: ``` $ id uid=6001(nagios) gid=792(nagios) groups=792(nagios),4(adm) $ ls -l /etc/ceph/ceph.conf -rw-r--r-- 1 root root...

So if I understand this NRPE line `/usr/local/nagios/libexec/check_nrpe -H 10.x.y.z -c check_ceph_osd -a 10.x.y.z 0` correctly, it means: run the plugin check_ceph_osd on remote host `10.x.y.z` with the parameters `ARGS1=10.x.y.z`...

Did you try with the parameter `-k KEYRING_FILE` or `--keyring KEYRING_FILE` ?

It is just a permission issue of the keyring file, it should be readable by the user nagios ``` unable to find a keyring on /etc/pve/priv/ceph.client.nagios.keyring: (13) Permission denied ```...

Can you try, as user nagios: ``` /usr/bin/ceph --id nagios --keyring /var/lib/nagios/ceph.client.nagios.keyring osd status ``` it is what the nagios plugin is doing...

Is the user nagios able to read the ceph.conf ? A possible workaround is to define the keyring in a nagios ceph.conf, and use it with the client. `nagios.ceph.conf` (a...