-
ABP Framework version: v0.9.23
-
UI Type: Angular
-
Database System: EF Core (SQL Server)
-
Tiered (for MVC) or Auth Server Separated (for Angular): yes
-
Exception message and full stack trace: Cannot start Docker Compose application. Reason: compose [start] exit status 1. Container redis Starting Container sql-server Starting Container redis Started Container sql-server Started Container sql-server Waiting Container redis Waiting Container sql-server Waiting Container sql-server Waiting Container redis Waiting Container redis Healthy Container redis Healthy Container sql-server Error Container sql-server Error Container sql-server Error dependency failed to start: container sql-server is unhealthy
Always On: The availability replica manager is going offline because SQL Server is shutting down. This is an informational message only. No user action is required.
2025-03-11 05:35:00.45 spid9s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2025-03-11 05:35:01.00 spid27s Service Broker manager has shut down.
2025-03-11 05:35:01.01 spid9s .NET Framework runtime has been stopped.
2025-03-11 05:35:01.15 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
-
Steps to reproduce the issue:
Follow the ABP documentation on docker containerization.
1 Answer(s)
-
0
The most likely issue is that scaling the ABP application instances increases the load on the SQL Server container beyond its capacity, causing it to become unhealthy. You should primarily investigate the resource limits configured for the SQL Server Docker container (CPU, memory, disk I/O) and SQL Server's internal configuration, particularly the maximum number of connections and memory settings, to ensure they are adequate for the increased load. Additionally, checking SQL Server error logs within the container for specific error messages related to resource exhaustion or connection failures is crucial for pinpointing the exact bottleneck.
