3 months ago
Stopping Container
[2025-09-20 14:20:30 +0000] [1] [INFO] Handling signal: term
[2025-09-20 14:20:30,281] INFO - [BOOT] SIGTERM received — shutting down gracefully
[2025-09-20 14:20:30,281] INFO - [SCHED] shutting down…
[2025-09-20 14:20:30,281] INFO - Scheduler has been shut down
[2025-09-20 14:20:30 +0000] [4] [INFO] Worker exiting (pid: 4)
[2025-09-20 14:20:30,283] INFO - [DB] pool closed
[2025-09-20 14:20:30 +0000] [1] [INFO] Shutting down: Master
This has been happening for the last 3-4 days and therefore my system (pipeline hast been stopped
4 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 SIGTERM ISSUE: Code is fine but unable to access public url of my node server
🧵 Container SIGTERM after 60-65 seconds despite healthy keepalive and health checks
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 3 months ago
3 months ago
None of the suggestive above helps me resolving the Sigterm I’ve received that keeps killing my system whilst shutting down after receiving said Sigterm
3 months ago
This looks like it's running out of memory. Can you check the metrics and see if that's the case?
3 months ago
See this comment https://station.railway.com/questions/django-gunicorn-container-stops-immedi-7b1e85a4#gdc3 as you apparently have the same issue as the creator of the threat on the link