You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presumably this worked at one time but after updating to the latest deps esp. compute platform, a compose does not come up. Logs tell a story that postgres is brought down before the async platform can connect to it. Fix this up so it can serve as a proper example of a simple, working async service.
docker-compose-queue-db-1 | CREATE DATABASE
docker-compose-queue-db-1 |
docker-compose-queue-db-1 |
docker-compose-queue-db-1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
docker-compose-queue-db-1 |
docker-compose-queue-db-1 | waiting for server to shut down...2023-03-24 05:05:04.654 UTC [36] LOG: received fast shutdown request
docker-compose-queue-db-1 | .2023-03-24 05:05:04.662 UTC [36] LOG: aborting any active transactions
docker-compose-queue-db-1 | 2023-03-24 05:05:04.663 UTC [36] LOG: background worker "logical replication launcher" (PID 43) exited with exit code 1
docker-compose-queue-db-1 | 2023-03-24 05:05:04.663 UTC [38] LOG: shutting down
docker-compose-queue-db-1 | 2023-03-24 05:05:04.743 UTC [36] LOG: database system is shut down
docker-compose-queue-db-1 | done
docker-compose-queue-db-1 | server stopped
docker-compose-queue-db-1 |
docker-compose-queue-db-1 | PostgreSQL init process complete; ready for start up.
docker-compose-queue-db-1 |
The text was updated successfully, but these errors were encountered:
Presumably this worked at one time but after updating to the latest deps esp. compute platform, a compose does not come up. Logs tell a story that postgres is brought down before the async platform can connect to it. Fix this up so it can serve as a proper example of a simple, working async service.
The text was updated successfully, but these errors were encountered: