The smart proxy overview page has a tab Pulp which shows the disk usage. This indeed does look at the space used on /var/lib/mongodb. AFAIK this is only for humans to consume and as long as you have a real monitoring system that checks its disk space, I wouldn’t worry about it.
If you want to silence this, you can set the path via the installer --foreman-proxy-plugin-pulp-mongodb-dir and it’ll check that directory instead.
Thanks for your reply
I don’t understand why the warning is triggered then, “–foreman-proxy-plugin-pulp-mongodb-dir” point to /var/lib/mongodb in my installation. Why is it saying that the file is unreadable ?
@ekohl Sorry for resurrecting this solved thread, but a customer of ours is experiencing this issue, while our internal test deployments point at /var/lib/pulp instead of /var/lib/mongodb and so do not have the issue. As far as I can tell we are not actively using the --foreman-proxy-plugin-pulp-mongodb-dir parameter. Do you know if the default value might have changed between foreman-installer versions?
What is the rational of checking /var/lib/mongodb vs. /var/lib/pulp? Is there a way to change the path post installation other than rerunning the foreman-installer with the parameter you posted?
Our customer reports they “fix” this issue by changing the permissions of /var/lib/mongodb (which does not strike me as a good solution to begin with) and then complain that foreman-installer keeps changing the permissions back.
Is the setfacl command by @loitho a better solution? (I don’t know if SELinux is used on the relevant system).