# Pbm restore steps

**URL:** <https://forums.percona.com/t/pbm-restore-steps/34831>\
**Category:** Percona Backup for MongoDB\
**Created:** [November 7, 2024, 6:19am UTC](https://forums.percona.com/t/pbm-restore-steps/34831 "2024-11-07T06:19:47Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 7, 2024, 6:19am UTC](https://forums.percona.com/t/pbm-restore-steps/34831/1 "2024-11-07T06:19:47Z")

</div>

Hello Team,  
I’ve 2 node replica setup and configure backup using pbm and it will store into the s3 bucket. Scheduled cron job for the backups as very sunday and wendesday base backup and the remaining days are incremental backup.

I’m trying to restore the latest base backup and this is output,

[root@mongodb-test3 ~]# pbm restore --time=“2024-11-05T18:30:02”  
Starting restore 2024-11-07T05:53:34.381347779Z to point-in-time 2024-11-05T18:30:02 from ‘2024-11-04T18:30:02Z’…

when I check the pbm status it is showing as,

# Cluster:

rs1:

- 192.168.40.41:27017 [P]: pbm-agent [v2.6.0] FAILED status:

> ERROR with lost agent, last heartbeat: 1730958885

- 192.168.40.40:27017 [S]: pbm-agent [v2.6.0] FAILED status:

> ERROR with lost agent, last heartbeat: 1730958890

Can anyone help me with this. What are the steps do i need to follow before restoration.

regards,  
JP

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 7, 2024, 11:46am UTC](https://forums.percona.com/t/pbm-restore-steps/34831/2 "2024-11-07T11:46:04Z")

</div>

Hi, it seems PBM ran into some issue. Can you check the pbm-agent logs on each node with  
`journalctl -u pbm-agent ` ?

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 7, 2024, 12:20pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/3 "2024-11-07T12:20:53Z")

</div>

Hello,

Thanks for your reply.

This is the command I’m using for the restore,  
[root@65981f33aae5 ~]# pbm restore --time=“2024-11-05T18:30:02”  
Starting restore 2024-11-07T12:15:58.27830722Z to point-in-time 2024-11-05T18:30:02 from ‘2024-11-04T18:30:02Z’  
…

and I can see the output for “journalctl -u pbm-agent -f”

Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 I got command restore [name: 2024-11-07T12:15:58.27830722Z, snapshot: 202 4-11-04T18:30:02Z point-in-time: \<1730831402,0\>] \<ts: 1730981758\>  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 I got epoch {1730958814 6}  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] to time: 2024-11-05T18:30:02Z  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] oplog slicer disabled  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] backup: 2024-11-04T18:30:02Z  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] recovery started  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] port: 27218  
Nov 07 17:45:58 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:58.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/rs.rs1/node.192.168.40.41:27017.hb” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:45:59 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:59.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/rs.rs1/rs.hb” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:45:59 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:59.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/cluster.hb” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:45:59 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:45:59.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] mongod binary: mongod, version: v6.0.17  
Nov 07 17:46:00 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:00.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] get src 2024-11-03T18:30:02Z  
Nov 07 17:46:00 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:00.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] get src 2024-11-02T18:30:01Z  
Nov 07 17:46:35 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:35.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] moving to state starting  
Nov 07 17:46:35 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:35.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/rs.rs1/node.192.168.40.41:27017.starting” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:46:35 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:35.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] waiting for `starting` status i n rs map[.pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/node.192.168.40.40:27017:{} .pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/node.192.168. 40.41:27017:{}]  
Nov 07 17:46:43 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:43.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/rs.rs1/rs.starting” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:46:43 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:43.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] waiting for shards map[.pbm.res tore/2024-11-07T12:15:58.27830722Z/rs.rs1/rs:{}]  
Nov 07 17:46:49 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:49.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/cluster.starting” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:46:49 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:49.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] waiting for cluster  
Nov 07 17:46:55 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:55.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] converged to state starting  
Nov 07 17:46:55 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:55.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] starting  
Nov 07 17:46:55 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:55.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] moving to state running  
Nov 07 17:46:55 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:55.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/rs.rs1/node.192.168.40.41:27017.running” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:46:56 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:46:56.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] waiting for `running` status in rs map[.pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/node.192.168.40.40:27017:{} .pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/node.192.168.4 0.41:27017:{}]  
Nov 07 17:47:04 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:04.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/rs.rs1/rs.running” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:47:04 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:04.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] waiting for shards map[.pbm.res tore/2024-11-07T12:15:58.27830722Z/rs.rs1/rs:{}]  
Nov 07 17:47:10 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:10.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11 -07T12:15:58.27830722Z/cluster.running” [size hint: 10 (10.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:47:10 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:10.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] waiting for cluster  
Nov 07 17:47:16 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:16.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] converged to state running  
Nov 07 17:47:16 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:16.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] send to stopAgent chan  
Nov 07 17:47:17 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:17.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] stop agents heartbeats  
Nov 07 17:47:17 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:17.000+0530 I [restore/2024-11-07T12:15:58.27830722Z] stopping mongod and flushing ol d data  
Nov 07 17:47:17 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:17.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] shutdown server  
Nov 07 17:47:17 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:17.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:18 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:18.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:19 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:19.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:20 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:20.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:21 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:21.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:22 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:22.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:23 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:23.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary  
Nov 07 17:47:24 mongodb-test3 pbm-agent[59256]: 2024-11-07T17:47:24.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting to became secondary

and in the secondary server I can see the logs as,

[root@mongodb-test4 ~]# journalctl -u pbm-agent -f  
Nov 07 17:47:13 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:13.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] shutdown server  
Nov 07 17:47:29 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:29.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] waiting for the node to shutdown  
Nov 07 17:47:30 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:30.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/node.192.168.40.40:27017.error” [size hint: 115 (115.00B); part size: 10485760 (10.00MB)]  
Nov 07 17:47:30 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:30.000+0530 E [restore/2024-11-07T12:15:58.27830722Z] restore: shutdown: check for lock file /data/db/mongod.lock: stat /data/db/mongod.lock: no such file or directory  
Nov 07 17:47:30 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:30.000+0530 I change stream was closed  
Nov 07 17:47:30 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:30.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] uploading “.pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/log/192.168.40.40:27017.0.log” [size hint: -1 (unknown); part size: 10485760 (10.00MB)]  
Nov 07 17:47:30 mongodb-test4 pbm-agent[24530]: 2024-11-07T17:47:30.000+0530 D [restore/2024-11-07T12:15:58.27830722Z] hearbeats stopped  
Nov 07 17:47:31 mongodb-test4 pbm-agent[24530]: 2024/11/07 17:47:31 Exit:   
Nov 07 17:47:31 mongodb-test4 systemd[1]: pbm-agent.service: Deactivated successfully.  
Nov 07 17:47:31 mongodb-test4 systemd[1]: pbm-agent.service: Consumed 37.606s CPU time.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 7, 2024, 12:37pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/4 "2024-11-07T12:37:27Z")

</div>

Hi, can you check the contents of this file in the S3 bucket?  
“.pbm.restore/2024-11-07T12:15:58.27830722Z/rs.rs1/node.192.168.40.40:27017.error”  
also check any mongo logs on mongodb-test4 as it seems that node had an issue during the recovery process

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 7, 2024, 1:15pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/5 "2024-11-07T13:15:06Z")

</div>

Hi, I can see the following information in the mentioned error log

1730981850:shutdown: check for lock file /data/db/mongod.lock: stat /data/db/mongod.lock: no such file or directory

Where can we check the mongo logs. As checked, i don’t find any in the mongodb-test4 machine

[root@mongodb-test4 ~]# ls -lrt /var/log/mongodb/mongod.log  
-rw-r-----. 1 mongod mongod 0 Aug 14 05:03 /var/log/mongodb/mongod.log

Since the instance is running on the docker container i’m not sure where the log file is exists.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 7, 2024, 1:29pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/6 "2024-11-07T13:29:47Z")

</div>

Seems you hit a bug. I have created [[PBM-1435] - Jira](https://perconadev.atlassian.net/browse/PBM-1435) for the dev team to take a look

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 7, 2024, 1:57pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/7 "2024-11-07T13:57:45Z")

</div>

Thanks a lot

I’ll wait for the updates

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 7, 2024, 3:58pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/8 "2024-11-07T15:58:37Z")

</div>

Hi Ivan,

Meanwhile, could you please give me the document for the PBM backup and restore (PITR). It would be helpful for me while configuring in the production environment.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 7, 2024, 4:19pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/9 "2024-11-07T16:19:22Z")

</div>

Please refer to [Point-in-time recovery - Percona Backup for MongoDB](https://docs.percona.com/percona-backup-mongodb/features/point-in-time-recovery.html)

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 7, 2024, 5:04pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/10 "2024-11-07T17:04:07Z")

</div>

Thank you.

How long does it take for the bug fix, any idea.

---

<div class="post-metadata">

**Author:** ![oleksandr.havryliak](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/oleksandr.havryliak/32/5703_2.png) [@oleksandr.havryliak](https://forums.percona.com/u/oleksandr.havryliak)\
**Post date:** [November 12, 2024, 1:25pm UTC](https://forums.percona.com/t/pbm-restore-steps/34831/11 "2024-11-12T13:25:10Z")

</div>

Hi @Jayaprakash_Duraisam !  
Do I understand correctly that mongodb-test4 - is docker container which is running mongodb and pbm-agent is connecting to this instance from the outside?

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 15, 2024, 11:52am UTC](https://forums.percona.com/t/pbm-restore-steps/34831/12 "2024-11-15T11:52:48Z")

</div>

Hello @oleksandr.havryliak

Sorry for the delayed response!!!

Yes, you’re right. Mongodb is running in the docker container and I’m doing the backups and restore from the outside.

regards,  
Jayaprakash Duraisamy

---

<div class="post-metadata">

**Author:** ![oleksandr.havryliak](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/oleksandr.havryliak/32/5703_2.png) [@oleksandr.havryliak](https://forums.percona.com/u/oleksandr.havryliak)\
**Post date:** [November 18, 2024, 7:02am UTC](https://forums.percona.com/t/pbm-restore-steps/34831/13 "2024-11-18T07:02:44Z")

</div>

Hi!  
Unfortunately this setup is not supported for the physical/incremental backup/restore. To be able to perform physical/incremental restore pbm-agent must have R/W access to mongodb data directory and also must have direct access to the mongod executable.

---

<div class="post-metadata">

**Author:** ![Jayaprakash\_Duraisam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jayaprakash_duraisam/32/18251_2.png) [@Jayaprakash\_Duraisam](https://forums.percona.com/u/Jayaprakash_Duraisam)\
**Post date:** [November 18, 2024, 7:07am UTC](https://forums.percona.com/t/pbm-restore-steps/34831/14 "2024-11-18T07:07:41Z")

</div>

Thanks @oleksandr.havryliak

Could you please help me to achieve this. I mean, how to give R/W access to the mongodb data directory and mongod executable

---

<div class="post-metadata">

**Author:** ![oleksandr.havryliak](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/oleksandr.havryliak/32/5703_2.png) [@oleksandr.havryliak](https://forums.percona.com/u/oleksandr.havryliak)\
**Post date:** [November 18, 2024, 7:17am UTC](https://forums.percona.com/t/pbm-restore-steps/34831/15 "2024-11-18T07:17:16Z")

</div>

If we are talking about containers you can try using [supervisord](https://docs.docker.com/engine/containers/multi-service_container/#use-a-process-manager) to start and run both mongodb and pbm-agent inside the container. You can find the examples here: [mongodb.ini](https://github.com/Percona-QA/psmdb-testing/blob/main/pbm-functional/pytest/conf/supervisord.d/mongod.ini), [pbm-agent.ini](https://github.com/Percona-QA/psmdb-testing/blob/main/pbm-functional/pytest/conf/supervisord.d/pbm-agent.ini)
