-
-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"An unexpected error occurred" - Every few hits #1285
Comments
Could you check the logs around the time this error happens? For the docker image, los are in the standard output. |
I have actually managed to reproduce it. I have a suspicion of what could be causing this. Just to make sure it's the same. Can you check in the logs if you find "MySQL server has gone away"? |
Yes, sorry.. there's a lot on the log but I notice the line: Next Doctrine\DBAL\Exception\ConnectionLost: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in /etc/shlink/vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php:106 And the log ends with: Refresh, link works. |
I have found the root cause for this. It's something I already "fixed" several versions ago, but it turns out I only applied a partial fix, mitigating the issue so that it recovers after failing once, instead of preventing the fail completely. The weird thing is that it has been there since a lot of time ago. It's weird that nobody noticed before. |
I have just released v2.10.1 The docker image will be available once this job finishes: https://github.com/shlinkio/shlink/runs/4595524058?check_suite_focus=true |
How Shlink is set-up
Summary
Previous versions appeared to be ok. Started noticing this recently after updates.
Current behavior
Possibly 50% or more of short link hits yield an error "An unexpected error occurred" - on refresh, the link does resolve.
Link creation by way of shlink-web encounters no issues creating short links.
Expected behavior
I expect all links to redirect and no errors.
How to reproduce
Not sure as this doesn't appear to be configuration-related.
Perhaps there are some things I could look for?
The text was updated successfully, but these errors were encountered: