Central 2026.1.0 - waiting for a local database connection at startup

Support
1

1. What is the issue? Please be detailed.

there are some new lines in start-odk.sh that causes the startup script to wait for a local database to be available. Since we are using a different hosted database the connection will never succeed.

2. What steps can we take to reproduce this issue?

Upgraded to 2026.1.0; saw the issue arise, downgraded to 2025.4.4 issue was resolved

the lines in start-odk.sh that are causing this:

echo "waiting for PostgreSQL to become connectable to..."
while ! (psql --no-password --quiet --command "" > /dev/null 2>&1 || (echo "sleeping 1 second waiting for a database connection"; false)); do sleep 1; done

3. What have you tried to fix the issue?

4. Upload any forms or screenshots you can share publicly below.

2

Hi! It should succeed with a connection to an elsewhere-hosted database, too. In fact, that’s how our staging server is set up.
What’s relevant here are the values of the libpq environment variables.

Did you see the action item in the release notes for when you’re using DB_SSL?

Anyway, let’s have a look at your setup.
First, the config from your .env :

grep -E '^(DB_|PG)' .env

Then, with 2026.1.0, could you please run:
docker compose exec -it service env | grep '^PG'

Maybe you can see what’s wrong already yourself based on that. If not, please post the output, but of course you can replace characters of the DB host/password/username with x (keep empty values though, those are relevant, i.e. don’t replace PGHOST= with PGHOST=x, etc.).

2 Likes