Add proper error message when PBM agents aren't available
General
Escalation
General
Escalation
Description
This had been running for a few days just fine. Ran from cron every 4 hours.
I tried restarting the agent on mongo1.db.example.net and then the backup started working. Although the other agents show failed in the status now.
Environment
Smart Checklist
Activity
andrew.pogrebnoi October 28, 2021 at 3:48 PM
Yes, you're right, the error message should be more user-friendly. Let's keep the ticket.
William Taylor October 25, 2021 at 3:56 PM
I would argue that there is a bug here to be fixed.
Running pbm backup and having the error message "no progress from leader, backup metadata not found" isn't really helpful in my opionion.
Would be nice if the error message was more friendly and told the user something helpful to fix the issue.
Even pbm status showed all the agents correctly but apparently they weren't communicating because I had to restart to get things working correctly.
Thoughts?
andrew.pogrebnoi October 25, 2021 at 11:15 AM
So now everything works fine? I'll close the ticket?
William Taylor October 21, 2021 at 3:43 PM
Yes sorry I restarted the other agents once I noticed the other ones were showing failed.
andrew.pogrebnoi October 21, 2021 at 8:00 AM
Hi ,
Have you tried to restart the other agents as well? pbm-agent NOT FOUND looks like agents can't report its status as they aren't connected to mongo. Can you take a look at what's in agents logs (not `pbm logs` but in processes' stderr)?
This had been running for a few days just fine. Ran from cron every 4 hours.
I tried restarting the agent on mongo1.db.example.net and then the backup started working. Although the other agents show failed in the status now.