Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Provide a way to distinguish SST failure cases in garbd
General
Escalation
General
Escalation
Description
Right now garbd almost always exit with 1 and we can't understand if SST succeeded or not.
We need a way to distinguish these three cases: 1. Donor exits without sending all the SST data 2. Garbd kills SST script 3. SST script fails
Environment
None
Attachments
1
14 May 2025, 12:59 PM
Activity
Eleonora Zinchenko
May 14, 2025 at 12:59 PM
Hi,
garbd finishes with Command did not run`:
2025-05-14 09:42:09.042 INFO: Garbd returns 0
+ GARBD_EXIT_CODE=0
+ case ${GARBD_EXIT_CODE} in
+ log INFO 'Backup was finished successfully'
Command did not run: /usr/bin/run_backup.sh2025-05-14 09:42:09 [INFO] Backup was finished successfully
+ exit 0
As discussed, this is due to:
garbd waits for sst_script to finish twice.
1st time: SST script ended gracefully
2nd time: Command did not run: <- this comes from process->wait() and says that exit code was already collected, nothing to wait for.
Full log attached.Loading file...
Kamil Holubicki
May 7, 2025 at 6:52 AM
Improved version binary passed to @ege.gunes . Waiting for feedback.
Right now garbd almost always exit with 1 and we can't understand if SST succeeded or not.
We need a way to distinguish these three cases:
1. Donor exits without sending all the SST data
2. Garbd kills SST script
3. SST script fails