Segmentation fault with Version 2.35.3 and Fargate

[MarianG]

We deployed the version 2.35.3 of DefectDojo on AWS ECS with Fargate (1.4) and the worker and beat container were running fine. However, we had issues with the django container that run into segmentation faults. This resulted in the ECS Task restarting over and over again. In the logs we received the message !!! uWSGI process 14479 got Segmentation Fault !!! Steps to reproduce Steps to reproduce the behavior:

1. Go to AWS ECS create a cluster
2. Build the containers with version 2.35.3
3. deploy the containers on Fargate
4. See error

Expected behavior Task are executed with containers and Dojo application is starting

Deployment method (select with an X)

• [ ] Docker Compose
• [ ] Kubernetes
• [ ] GoDojo
• [x] Container build + AWS Fargate

Environment information

• Operating System: [e.g. Ubuntu 18.04]
• DefectDojo version (see footer) or commit message: 2.35.3

Logs Use docker-compose logs (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).

Additional context (optional) It seems that on some environments the wsgi process has trouble with memory management, e.g. https://github.com/pytorch/pytorch/issues/42125

[mtesauro]

@MarianG

Unfortunately, AWS Fargate isn't a supported install option so there's not much the project can say about the issue you reported as we don't have tests that cover that situation nor any real familiarity with AWS Fargate.

From the README.md:

You may be able to get assistance by asking this on the OWASP Slack in the #defectdojo channel - details on joining Slack are at https://github.com/DefectDojo/django-DefectDojo?tab=readme-ov-file#community-getting-involved-and-updates