PMM error: software “mongodb” is not installed: incompatible service

MongoDB Percona Backup for MongoDB
, ,
1

Hello,

We are running Percona for Mongo for the first time. Everything is running using your Docker images.

We have installed Percona Server for Mongo version 8.0.
We have a replicaset with just one Mongo node (for testing).
We have installed Percona Backup for Mongo (PBM) 2.8.0.
We can successfully make both logical and physical backups using PBM and restore.
We have installed the PMM client and server.
We can visit the PMM server and add the service for MongoDB.
However, we cannot see our existing backups or make new ones. We have added the backups folder from PBM to the PMM server and client, hoping that we could add it to the PMM server as a backup directory, but no backups are listed in the web UI, and when we try to run a new backup, we see this error:

software “mongodb” is not installed: incompatible service.

In terms of logs, our PMM server has /srv/pmm-agent.log with entries like:

time=“2025-01-29T15:38:51.584+00:00” level=info msg=“ts=2025-01-29T15:38:51.584Z caller=server.go:75 level=info msg="Established new database connection" fingerprint=127.0.0.1:5432” agentID=/agent_id/9fbf593b-da12-4fd9-a496-71411d3c5778 component=agent-process type=postgres_exporter

I don’t really understand how the PMM server should be integrated. I think the PMM server connects to both the PMM client and also the Mongo server via connection string. Does the PMM Server want to directly integrate with the Wired Tiger files for physical backups, or does it rely on the PBM?

Can you advise how we should resolve the error we are experiencing?

Thanks,

Jared

2

Hi, unfortunately PMM does not support backup management when the Mongo is running in containers at this time.

3

Thank you for your prompt reply.

I think that the following documentation page should be updated so that where it says that MongoDB of a particular minimum version is required, it should also mention that it must be on the same server as the PMM client and not in a container (or whatever the exact requirement is).

Is this due to change in PMM version 3?

4

PMM2 and PMM3 have the same limitation unfortunately. We will make it more clear in the doc page.