After installation and configuration, the pods and PMM section on cr.yaml looks as follows:
On the PMM Server, listing the nodes get only Shards and ConfigServers listed:
Analyzing any of the mongoS logs, we can see the following:
After pmm-admin add mongodb,we see:
and
Comparing the permissions of mongod against mongoS, we have:
mongoS
mongod
It seems there is a group permission divergence that blocks the mongoS being monitored by PMM.
Environment
None
AFFECTED CS IDs
CS0038728
Attachments
2
Activity
Show:
Pavel Tankov September 28, 2023 at 6:43 PM
Edited
It's fixed. There is no more cannot load file in path and cat: /etc/mongodb-ssl/tls.key: Permission denied cat: /etc/mongodb-ssl/tls.crt: Permission denied messages in the log.
Slava Sarzhan August 30, 2023 at 1:17 PM
the issue was fixed, and fix will be available in next psmdb operator release.
How to reproduce:
Deploy PSMDB operator v1.14.0.
Default installation as per the official documentation.
Install PMM using helm.
Default installation per the official documentation.
After installation and configuration, the pods and PMM section on cr.yaml looks as follows:
On the PMM Server, listing the nodes get only Shards and ConfigServers listed:
Analyzing any of the mongoS logs, we can see the following:
After pmm-admin add mongodb,we see:
and
Comparing the permissions of mongod against mongoS, we have:
mongoS
mongod
It seems there is a group permission divergence that blocks the mongoS being monitored by PMM.