In a customer case, on couple of shards this apparently fails and PBM reports connection refused:
As far as I could see, output of this temporary mongod instance is not stored anywhere. It would be very helpful to have that output, to figure out why it failed.
Perhaps it could be stored to a file either in dbPath or on the shared storage? Or output to stdout so it goes wherever PBM agent log goes.
Environment
None
AFFECTED CS IDs
CS0028551
Smart Checklist
Activity
andrew.pogrebnoi August 31, 2022 at 11:52 AM
Output (logs) of temporary mongods are now stored in `pbm.restore.log` files inside datadir.
These files are cleaned-up after the successful finish of a restore. And stays there should the restore fail.
When restoring a physical backup, PBM starts a temporary mongod process for some housekeeping tasks, in the prepareData function: https://github.com/percona/percona-backup-mongodb/blob/main/pbm/restore/physical.go#L459
In a customer case, on couple of shards this apparently fails and PBM reports connection refused:
As far as I could see, output of this temporary mongod instance is not stored anywhere. It would be very helpful to have that output, to figure out why it failed.
Perhaps it could be stored to a file either in dbPath or on the shared storage? Or output to stdout so it goes wherever PBM agent log goes.