Open ewuski opened 4 months ago
Hi there @ewuski!
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
Closing as resolved
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.8.3, 13.2.1
Bug summary
Since we migrated to Umbraco 10 (in November 2023) we've been experiencing database timeouts, sometimes severe leading to fatal exceptions and site crashes.
We recently upgraded to Umbraco 13.2.1 and the issue is still happening.
Specifics
The issue (or similar issues) happens very often when accessing the back office, usually every day.
It also sometimes happened just after we deployed changes to remote servers. It occurs extremely occasionally locally.
The symptom is that the back office becomes un-browsable, eg.:
The content tree on the left does not show anything/ is empty
nothing loads - neither the top nav, left-hand side tree nor the central edit area, only the background is visible - this happens less commonly or the central and top areas load after a long delay
areas most affected are Content, Media, Users, Members, Translation, and custom section. The Settings section sometimes does not load the tree but often it loads well despite the Content or Media area having the tree empty.
The errors thrown are of this kind or similar:
Yesterday a fatal exception happened during the deployment of our changes to production and test sites. The deployment caused the site to restart which resulted in db timeouts that made the entire site crash. The source of the error logged is an issue with loading cache data but also indicates db as the source of the issue:
The issue then affects the front-end API actions like saving or publishing content, which produces more errors:
Steps to reproduce
We do not know what triggers the issue. It just happens when we log in to the back office without doing anything else, just because we are not able to do anything else because most of the content in the back office does not load.
Here are our config settings:
We tried to increase the db timeout but it didn't help anything.
Our server is a dedicated server:
Memory 8 GB SSD Disk 2 x 480 GB SSD Operating System Windows Server 2022
Expected result / actual result
The back office should load fine and do not produce db timeouts.