Percona Backup for MongoDB 1.6 ( Status Cluster )

by stopping the pbm-agent with the unit systemd, the agent status remains ok.

[root@localhost:~]# systemctl stop pbm-agent

● pbm-agent.service - pbm-agent
Loaded: loaded (/usr/lib/systemd/system/pbm-agent.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Thu 2022-02-03 16:19:53 CET; 36s ago
Process: 115005 ExecStart=/usr/bin/pbm-agent (code=killed, signal=TERM)
Main PID: 115005 (code=killed, signal=TERM)

[root@localhost:~] pbm status -s cluster
Cluster:

rs0:

  • rs0/localhost:27017: pbm-agent v1.6.1 OK <--------
  • rs0/localhost:27018: pbm-agent v1.6.1 OK
  • rs0/localhost:27019: pbm-agent v1.6.1 OK

I noticed that the pbmAgents collections are not updated after stopping the agent.
Mongo Version : Percona Server for MongoDB server version: v4.4.10-11

I have 3 instances of mongodb (replica set) PSS

is there solution with problem ?

1 Like

Hi @Manganiello ,

Thanks for the reporting. It’s a bug. pbm status should consider agents’ heartbeats. We’ve created a ticket a will try to fix it in the upcoming release.

1 Like