Self hosting retool on AWS EKS | Retool version: 2.111.3

Hello,

I have deployed retool using the retool-onpremise github documentation.
It was running fine until i decided to increase the resources, so I changed the values and redeployed.

the postgres app is giving issues.
Here are the logs for the respective pods

API pod (container.yaml) retool version: 2.111.3

kubectl logs api-547b4bb5d5-vsbqw -n retool

Output:

wait-for-it.sh: waiting for postgres:5432 without a timeout
wait-for-it.sh: postgres:5432 is available after 0 seconds
not untarring the bundle
{"message":"[process service types] MAIN_BACKEND, DB_CONNECTOR, DB_SSH_CONNECTOR","level":"info","timestamp":"2023-08-16T23:16:37.332Z"}
There are 360 pending database migrations, checking for up-to-date schema in 1 second(s)...

Postgres version 11.13

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start


WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
waiting for server to start....2023-08-16 23:15:46.227 UTC [49] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-16 23:15:46.241 UTC [50] LOG:  database system was shut down at 2023-08-16 23:15:46 UTC
2023-08-16 23:15:46.246 UTC [49] LOG:  database system is ready to accept connections
 done
server started
CREATE DATABASE


/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

2023-08-16 23:15:46.605 UTC [49] LOG:  received fast shutdown request
waiting for server to shut down....2023-08-16 23:15:46.607 UTC [49] LOG:  aborting any active transactions
2023-08-16 23:15:46.608 UTC [49] LOG:  background worker "logical replication launcher" (PID 56) exited with exit code 1
2023-08-16 23:15:46.608 UTC [51] LOG:  shutting down
2023-08-16 23:15:46.622 UTC [49] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2023-08-16 23:15:46.714 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-08-16 23:15:46.714 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-08-16 23:15:46.717 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-16 23:15:46.729 UTC [77] LOG:  database system was shut down at 2023-08-16 23:15:46 UTC
2023-08-16 23:15:46.734 UTC [1] LOG:  database system is ready to accept connections
2023-08-16 23:16:36.728 UTC [84] LOG:  incomplete startup packet
2023-08-16 23:21:43.831 UTC [694] LOG:  incomplete startup packet
2023-08-16 23:27:02.298 UTC [1306] LOG:  incomplete startup packet

Jobs-runner retool version: 2.111.3

kubectl logs jobs-runner-79dd96c7b7-72wzm -n retool
wait-for-it.sh: waiting for postgres:5432 without a timeout

Hey! Just wanted to update this thread with the resolution from the email thread with Support. Increasing the resources for both the API and Jobs-runner pods resolved this issue.

1 Like