Changes between Initial Version and Version 1 of Ticket #31515, comment 7
- Timestamp:
- Apr 25, 2020, 8:35:53 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31515, comment 7
initial v1 13 13 2020-04-26 1:21:33 282 [Warning] Aborted connection 282 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets) 14 14 2020-04-26 1:21:33 187 [Warning] Aborted connection 187 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets) 15 2020-04-26 1:21:33 180 [Warning] Aborted connection 180 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets)16 2020-04-26 1:21:33 186 [Warning] Aborted connection 186 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets)17 2020-04-26 1:21:33 281 [Warning] Aborted connection 281 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets)18 2020-04-26 1:21:33 279 [Warning] Aborted connection 279 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets)19 2020-04-26 1:21:33 182 [Warning] Aborted connection 182 to db: 'test' user: 'root' host: '172.17.0.1' (Got an error reading communication packets)20 15 }}} 16 17 Additionally, with `show processlist` I can see that Django is keeping connections open when doing nothing (they all disappear along with those errors in the SQL console when I shut down the asgi server), is this proper behaviour when the CONN_AGE is set to 0? 18 19 [[Image(https://i.imgur.com/LRdVrAL.png)]]