Plug.Cowboy.Drainer shut down abnormally
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
Start with the SASL log and the Plug.Cowboy.Drainer.start_link entry point mentioned in the report. Reproduce the shutdown on the local setup and investigate the suspected memory or file-descriptor limits, comparing them with the environments where it does not occur. Done means identifying the cause or documenting diagnostics that distinguish these failure modes.
Written by the indexing model from the issue text.
Description
Hi!
My app has been shutting down seemingly randomly. This only happens on my local machine (not on other devs, not in production environments) so I suspect it has something to do with my set up.
There are no logs when my app shuts down. It doesn't seem to correlate to any particular behavior. This has been happening for at least a couple weeks with regular daily development happening.
I finally got a clue by enabling SASL logging:
[error] Child Plug.Cowboy.Drainer of Supervisor MyApp.Endpoint shut down abnormally
** (exit) killed
Pid: #PID<0.1011.0>
Start Call: Plug.Cowboy.Drainer.start_link([refs: [MyAppWeb.Endpoint.HTTP]])
Restart: :permanent
Shutdown: 5000
Type: :worker
[notice] Application my_app exited: shutdown
Based on looking at what Plug.Cowboy.Drainer does, this seems like the error could be a red herring? Any ideas how I could get more diagnostic information? I highly suspect this is a memory limit or running out of file descriptors or something else specific to my environment but I can't seem to get any more clues.
I'm using plug_cowboy 2.6.0 with Phoenix 1.7.0-rc.2 on Elixir 1.14.3, OTP 25
- Dominant language
- Elixir
- Stars
- 264
- Forks
- 59
- Avg merge
- 1h 48m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
carverauto/serviceradar#5264 ·
Maintainers usually reply within 1 day
-
Handle short ciphertext in AES-GCM Decrypt instead of panickingPossibly taken @pamod-madubashana claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
semaphoreio/semaphore#1305 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuinnWilton/argus#5 · 1 comment ·
-
help-wanted L: docker L: elm L: github:actions L: helm L: ruby:bundler
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dependabot/dependabot-core#16425 ·
Maintainers usually reply within 2 days
-
Cainophile EXIT handler crashes on its own password redaction and logs the DB password in clear textOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days