mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-11 00:04:08 -05:00
OpenWebUI 0.5.16 container crashes with "[engine] caught signal [SIGTERM]" when running as AWS Fargate ECS task #4138
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#4138
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jaipaddy on GitHub (Feb 25, 2025).
Bug Report
Installation Method
Docker
Environment
Open WebUI Version: 0.5.16
Ollama (if applicable):
Operating System: AWS Fargate ECS Task
Browser (if applicable): Chrome 133
Confirmation:
Expected Behavior:
I expect to be able to chat using the Function that makes a call to OpenAI Assistants API
Actual Behavior:
The ECS container crashes upon asking a question with this error - "[engine] caught signal [SIGTERM]" and it restarts and all users lose their session.
Description
Bug Summary:
Got OpenWebUI working locally as a docker container which talks to an OpenAI assistant via a Function - https://openwebui.com/f/mantonherre/assistant_openai.
While replicating this for wider use in our internal prod environment as AWS Fargate ECS Tasks/container, noticed that the container crashes often when this specific assistant that calls the Function is enabled and a question is sent in the chat. The debug logs have no useful information. All I see is "[engine] caught signal [SIGTERM]" in the container logs from ECS
Reproduction Details
Steps to Reproduce:
Create a Function from the link posted above. The model using this Function should be auto enabled. On the chat prompt, select this model and ask a question. The response will never return and if your refresh the browser, it will keep spinning. The Cloudwatch event logs for ECS will show that the container died and restarted. [engine] caught signal [SIGTERM] is the only line indicating the shutdown.
The healthchecks are supposed to run every 30s and 5 times.
Logs and Screenshots
[engine] caught signal [SIGTERM]
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!