Closed kinkenakin closed 3 months ago
Which exact version of Duende IdentityServer are you using? Can you please send me a stacktrace so I can see where exactly it went wrong? Also, looking at the exception, this might have to do with the database simply not being available for some reason. Is there a way for you to check if that's the case?
Right now we are using: Duende IdentityServer 7.0.0-preview.3.
The upgrade to 7.0.4 is yet to be released in Production. The funny thing is other database is working properly on the same server but when I restart the machine it fixed it (but we don't want to do this every time we faced this kind of issue as its a live environment). So my underlying concern is we might encounter this again and just asked whether you can provide some similar issues encountered by your other customers.
We don't have other reports coming in about this so I think this was a one-time database issue. Please upgrade to the latest release version of IdentityServer as soon as possible though as previews are not stable releases.
Assuming my last comment was sufficient to close this. If not please let us know.
Which version of Duende.AccessTokenManagement are you using? 7
Which version of .NET are you using? NET 8
Describe the bug Happened around 7:20ish AM AEST. First time encountered after almost 4 months of upgrading from IDENTITY SERVER 6 to subscribing to Duende.IdentityServer7. I just fear we might encounter this again that we are not sure what caused w/o upgrading anything from the last 3 weeks then suddenly the Ocelot Api Gateway cannot connect to SQL Identity Server DB.
Error captured
An exception occurred in the database while saving changes for context type '"Duende.IdentityServer.EntityFramework.DbContexts.PersistedGrantDbContext"'." ""Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.SqlCommand.<>c.b__209_0(Task`1 result) at