Hi, we just completed our upgrade and migration fr...
# talk-hydra
l
Hi, we just completed our upgrade and migration from v1.10.5 to v2.0.3 in production. After the upgrade we have seen a large increase in occurrences of this message when redeeming a refresh token from
/oauth2/token
endpoint: • "Got an empty session in toRequest" Previously there would be ~70K/day but since the upgrade we see 500-700K. What would cause the huge increase?
Also, after upgrading to 2.0.3 we've also seen many of these errors in our Hydra logs:
Copy code
failed to close prepared statement: ERROR: current transaction is aborted, commands ignored until end of transaction block (SQLSTATE 25P02): ERROR: insert or update on table "hydra_oauth2_access" violates foreign key constraint "hydra_oauth2_access_challenge_id_fk" (SQLSTATE 23503)
We saw that some other users had seen same error after the upgrade to 2.0, and provided some SQL to mitigate, but none of our data matched the queries provided, and I think those same queries were added with 2.0.3 anyway.
I think I found the reason for the foreign key constraint violations. There are records in
hydra_oauth2_refresh
that have
active=true
and
challenge_id=null
and have no corresponding records in either
hydra_oauth2_access
or
hydra_oauth2_flow
.
Is there anything that can be done?