aljaz/cyphernode
1
0
Fork 0
mirror of https://github.com/aljazceru/cyphernode.git synced 2026-01-24 23:04:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

Retrying up to 5 times if DB migration fails...

Browse Source
This commit is contained in:
kexkey
2022-01-17 16:53:33 -05:00
parent 2554a1b57a
commit d5f159e668
1 changed files with 28 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
proxy_docker/app/script/startproxy.sh
View File

@@ -23,15 +23,33 @@ createCurlConfig() {
}
# If the file .dbfailed exists, it means we previously failed to process DB migrations.
# Sometimes, depending on timing, a migration fails but it doesn't mean it's corrupted.
# It may be a container that was not accessible for a short period of time, for example.
# So we'll try up to MAX_ATTEMPTS times before concluding in failure.
# For this to work, we'll put the number of attemps in the .dbfailed file.
MAX_ATTEMPTS=5
nb_attempts=1
if [ -e ${DB_PATH}/.dbfailed ]; then
n=$(cat ${DB_PATH}/.dbfailed)
nb_attempts=$((n+1))
fi
if [ "${nb_attempts}" -gt "${MAX_ATTEMPTS}" ]; then
touch /container_monitor/proxy_dbfailed
trace "[startproxy] A previous database creation/migration failed. Stopping."
trace "[startproxy] A file called .dbfailed has been created. Fix the migration errors, remove .dbfailed and retry."
trace "[startproxy] Too many database creation/migration failed attempts. Failed attempts = ${nb_attempts}."
trace "[startproxy] A file called .dbfailed has been created in your proxy datapath. Fix the migration errors, remove .dbfailed and retry."
trace "[startproxy] Check your log files, especially postgres."
trace "[startproxy] Exiting."
sleep 30
exit 1
else
rm -f /container_monitor/proxy_dbfailed
if [ "${nb_attempts}" -gt "1" ]; then
trace "[startproxy] Current database creation/migration attempt = ${nb_attempts}. Retrying..."
fi
fi
trace "[startproxy] Waiting for PostgreSQL to be ready..."
@@ -57,17 +75,21 @@ else
fi
if [ "${returncode}" -ne "0" ]; then
touch ${DB_PATH}/.dbfailed
touch /container_monitor/proxy_dbfailed
trace "[startproxy] Database creation/migration failed. Stopping."
echo -n "${nb_attempts}" > ${DB_PATH}/.dbfailed
trace "[startproxy] Database creation/migration failed. We will retry ${MAX_ATTEMPTS} times."
trace "[startproxy] A file called .dbfailed has been created in your proxy datapath. Fix the migration errors, remove .dbfailed and retry."
trace "[startproxy] Check your log files, especially postgres."
trace "[startproxy] Exiting."
sleep 30
exit ${returncode}
fi
# /container_monitor/proxy_ready will be created by Docker's health check
rm -f /container_monitor/proxy_ready
rm -f /container_monitor/proxy_dbfailed
rm -f ${DB_PATH}/.dbfailed
chmod 0600 $DB_FILE
createCurlConfig ${WATCHER_BTC_NODE_RPC_CFG} ${WATCHER_BTC_NODE_RPC_USER}