Yurii
What could be the problem ?
[error] Postgrex.Protocol (pid<0.3054.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
Thanks! 
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
joaoevangelista
I would guess someone or something with higher priority send a signal to terminate the postgres server, is it running local or on some cloud ?
stefanchrobot
If this is a Postgres instance in the cloud, this might be an automatic Postgres upgrade.
Yurii
This happens locally and in the cloud.
Yurii
This happens locally and in the cloud
csadewa
Could you connect to your local/cloud postgres instance via pgAdmin? Is it throwing error like that?
If it’s still throwing error like that when you use pgAdmin, then most likely there were problem on the database it self (this is out of my expertise though).
If it’s not throwing error when you use pgAdmin, then most likely your application is doing something which cause the database to shutdown when it’s starting up (i presume?), try looking around your start up code which connect to DB and try to isolate the cause.
csadewa
Googling around for Postgrex FATAL 57P01, it seems like an issue that happen when there were somekind of error (like connection pool exceeded, memory usage over limit), and thus postgres supervisor terminate postgres process.
There were old issue in Oban library which record this Oban seems to be bringing down my application · Issue #72 · oban-bg/oban · GitHub . But the issue has since fixed.
Yurii
This happens even when there is no query in the database
joaoevangelista
OP says it happens in cloud and locally, so installation might not be the problem, maybe the connection configuration, since the application is common between envs?
@Yurii could you paste your Repo configuration? parameters, pool size etc?
Yurii
config :my_app, MyApp.Repo,
adapter: Ecto.Adapters.Postgres,
database: System.get_env(“MYAPP_DB_NAME”),
username: System.get_env(“MYAPP_DB_USERNAME”),
password: System.get_env(“MYAPP_DB_PASSWORD”),
hostname: System.get_env(“MYAPP_DB_HOST”),
types: MyApp.PostgresTypes,
pool: Ecto.Adapters.SQL.Sandbox,
size: 20
joaoevangelista
Are you using this pool in development? Are these configs in the
dev.exsor intest.exs? If you are using these atdev.exsremove the pool configuration and try again, this pool is for test only.